Use when building the central art-historical argument of an Art Bulletin article — the thesis, its stakes, and the chain from visual and documentary evidence to interpretation. The Art Bulletin rewards a fresh, well-warranted claim, not description. Shapes the argument; it does not generate evidence or do the looking.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill artbull-argument-development --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Artbull Argument Development?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-artbull-argument-development)More formats (shields.io, HTML) on the badges page.
---
name: artbull-argument-development
description: Use when building the central art-historical argument of an Art Bulletin article — the thesis, its stakes, and the chain from visual and documentary evidence to interpretation. The Art Bulletin rewards a fresh, well-warranted claim, not description. Shapes the argument; it does not generate evidence or do the looking.
---
# Argument Development (artbull-argument-development)
The heart of an Art Bulletin article is a **thesis** about works of art that is fresh, consequential,
and demonstrated. This skill turns positioning (`artbull-scholarly-positioning`) and looking
(`artbull-visual-analysis`) into a sustained argument. The closely related visual and evidentiary
work lives in its own skills; here you build the **claim and its warrant**.
## When to trigger
- Crystallizing the thesis and what is at stake in it
- The draft "describes beautifully" but reviewers cannot find the argument
- Linking formal observations and documents into an interpretation
- Defining the scope conditions and counter-readings you must answer
## Building the argument
1. **State the thesis as a claim, not a topic.** "This altarpiece reframes X" — something that could
be wrong, that a reader could dispute. A topic ("the altarpiece's iconography") is not a thesis.
2. **Make the stakes explicit.** Why does the claim matter for how the field understands this art,
this period, or this method? Tie back to the gap you named in positioning.
3. **Warrant every interpretive leap.** Each move from *what we see* / *what the document says* to
*what it means* needs a reason. Name the inference; do not smuggle it in with adjectives.
4. **Integrate the visual and the documentary.** The strongest Art Bulletin arguments interlock close
looking (`artbull-visual-analysis`) with archival/provenance evidence (`artbull-evidence-and-sources`).
5. **Anticipate the counter-reading.** Art-historical claims are contestable; state the most serious
rival interpretation and show why yours accounts for the evidence better.
6. **Set scope conditions.** Be candid about what the argument does and does not establish; modest,
defensible claims beat sweeping ones reviewers can puncture.
## Anti-patterns
- Description dressed as argument — vivid prose with no contestable claim
- Connoisseurial assertion ("clearly by the master's hand") with no warranted reasoning
- Over-claiming beyond what the objects and documents can bear
- Ignoring the obvious rival interpretation a reviewer will raise
- An argument that does not actually need the images it reproduces
## Output format
```
【Thesis】one contestable sentence
【Stakes】why it matters to the field
【Evidence chain】visual + documentary → interpretation (warrants named)
【Rival reading】strongest counter + why yours wins
【Scope】what it does / does not establish
【Next】artbull-visual-analysis
```
## Supplementary resources
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — archives, provenance, and technical-art-history sources
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — scope and contribution expectations
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!