artbull-evidence-and-sources
Use when assembling and handling the non-visual evidence for an Art Bulletin article — objects, archives, primary documents, provenance, and technical findings — and citing them rigorously. Art-historical claims must rest on verifiable sources, not assertion. Guides evidence handling; it does not fabricate documents or attributions.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill artbull-evidence-and-sources --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Evidence & Sources (artbull-evidence-and-sources) Beyond the object itself, an Art Bulletin argument rests on **documentary and material evidence**: archives, inventories, contracts, letters, sale records, provenance chains, and technical/conservation findings. This skill governs how you gather, weigh, and cite that evidence so an expert reviewer trusts it. The looking lives in `artbull-visual-a
What does the artbull-evidence-and-sources skill do?
Use when assembling and handling the non-visual evidence for an Art Bulletin article — objects, archives, primary documents, provenance, and technical findings — and citing them rigorously. Art-historical claims must rest on verifiable sources, not assertion. Guides evidence handling; it does not fabricate documents or attributions.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill artbull-evidence-and-sources --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.