Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Artbull Images And Permissions

ASecurity

Use to plan and execute the illustration, copyright-permission, and reproduction-quality workflow for an Art Bulletin article — the distinctive, slow, author-funded task of art-historical publishing. The author secures and pays for rights and supplies high-resolution images. Manages the image workflow; it does not grant rights or waive fees.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill artbull-images-and-permissions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Artbull Images And Permissions?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Artbull Images And Permissions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-artbull-images-and-permissions/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-artbull-images-and-permissions)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: artbull-images-and-permissions
description: Use to plan and execute the illustration, copyright-permission, and reproduction-quality workflow for an Art Bulletin article — the distinctive, slow, author-funded task of art-historical publishing. The author secures and pays for rights and supplies high-resolution images. Manages the image workflow; it does not grant rights or waive fees.
---

# Images & Permissions (artbull-images-and-permissions)

This is the skill that most distinguishes art-history publishing. The Art Bulletin requires
**illustrations**, and it is the **author's responsibility to obtain and pay for reproduction
permissions and photography**. Clearance is **slow and expensive**, so start it the moment the key
images are known — in parallel with the writing, not after. At submission, images go in **one Word
file (max 20 images, ≤ 10 MB)**; **high-resolution files are supplied promptly on acceptance**.

## When to trigger

- As soon as you know which works the argument depends on (start clearance now)
- Building the illustration list, captions, and credit lines
- Deciding fair use vs. paid permission for each figure
- Preparing high-resolution files after acceptance
- A budget or deadline threatens whether a key image can be reproduced

## The permissions workflow

1. **List the figures the argument requires.** Distinguish *essential* (the argument fails without
   them) from *supporting*; keep within the ~20-illustration limit and let the argument drive the list.
2. **Identify the rights holder for the actual reproduction.** A public-domain *work* can still have a
   copyrighted *photograph*: clear rights with the **copyright holder** (artist/estate, museum, or
   rights agency such as Art Resource, Bridgeman, Scala, ARS) — not with the book the scan came from.
3. **Decide fair use vs. permission per figure.** It is the author's responsibility to determine fair
   use; the **CAA Code of Best Practices in Fair Use for the Visual Arts** is the field reference.
   When in doubt, seek permission.
4. **Secure the right license scope.** Get **world rights, print + electronic, all editions** where
   possible; mismatched scope (e.g., print-only) causes problems at production and for the online and
   open-access versions.
5. **Source publication-quality files.** Prefer open-access museum downloads and IIIF where the
   rights allow; otherwise commission or license a press-quality file (commonly **300 dpi at print
   size**, TIFF for photographs, vector for plans/diagrams — confirm specs at acceptance).
6. **Write captions and credit lines correctly.** Artist, *italicized title*, date, medium,
   dimensions (inches then centimeters), collection and location, and the **required credit/copyright
   line** in parentheses — using the exact wording the rights holder mandates.
7. **Keep a permissions log.** Per figure: rights holder, contact, fee, license scope, date granted,
   credit-line wording, and file source. This is your evidence at production.

## Budget & timeline reality

- Fees range from free (open access / public domain) to hundreds of dollars per image; living artists'
  estates can be restrictive and slow. **Budget money and months.**
- If a key image cannot be cleared or afforded, the argument may need to lean on a different,
  clearable work — decide this **early**, not at proof stage.

## Anti-patterns

- Leaving permissions until acceptance — the classic, paper-delaying mistake
- Clearing rights from the source book rather than the actual copyright holder
- Assuming a public-domain object means the photograph is rights-free
- Licensing the wrong scope (print-only) and breaking the online / open-access edition
- Low-resolution or manipulated files that misrepresent the object
- Captions missing the mandated credit line wording

## Output format

```
【Figure list】essential vs supporting (count ≤ 20)
【Per figure】rights holder · fair use or permission · license scope · fee · file source
【Captions/credit lines】full + mandated wording? [Y/N]
【High-res plan】formats/resolution staged for acceptance? [Y/N]
【Permissions log】started and complete? [Y/N]
【Risk】any decisive image unclearable/unaffordable? fallback?
【Next】artbull-structure-and-exposition
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — image sources, rights agencies, fair-use code, resolution/format guidance
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — author-responsibility-for-permissions and illustration-file policy

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →