Individual skill
museum-art
Source authentic, high-res PUBLIC-DOMAIN artwork from museum open-access APIs (Met, Cleveland, SMK, Rijksmuseum, NGA, Art Institute of Chicago, Getty, Smithsonian) instead of AI-generated or generic-stock imagery. The default move whenever a visual needs an aesthetic, credible image (blog heroes, decks, social cards, essay/spec figures). Verified keyless recipes + licensing rules inside.
skills/museum-art/SKILL.md
Source commit 144c7a3a959cc99538b7dfee9c22c4b065a0e156
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,406
- Repository last updated
- Oct 23, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- cursor Repository topic
- garry-tan Repository topic
- gbrain Repository topic
- gstack Repository topic
- knowledge-management Repository topic
- obsidian Repository topic
- productivity Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,474 bytesSKILL.mdcore · 10,474 bytesSKILL.mdcore · 10,474 bytesSKILL.mdcore · 10,474 bytesreferences/_synthesis.mddoc · 9,389 bytesreferences/artic.mddoc · 6,317 bytesreferences/cleveland.mddoc · 5,681 bytesreferences/getty.mddoc · 10,173 bytesreferences/met.mddoc · 6,397 bytesreferences/nga.mddoc · 8,255 bytesreferences/rijksmuseum.mddoc · 7,889 bytesreferences/smithsonian.mddoc · 7,594 bytesreferences/smk.mddoc · 7,677 bytes
Read excerpt
# museum-art: Public-Domain Artwork for Visuals
> Standing rule (adopted 2026-07-24, from Eric Li's post on museum open-access): **whenever a visual needs a real image with aesthetic weight, source public-domain museum artwork first** - over AI-generated imagery and over generic stock. Curated, historically significant art reads as credible and sophisticated; AI-gen reads as slop. This stacks with, and reinforces, the `no-ai-slop` skill and your house image style. It does NOT replace the generative `editorial-illustrations` skill (that owns claim-driven diagrams/figures) or your house chart style - use museum art for photographic/hero/decorative/mood imagery, generative figures for data and concept diagrams.
## When to reach for this
- Blog post hero images, section breaks, mood imagery (the blog-publish image step).
- Deck/slide backgrounds and section dividers, social cards, essay figures, spec cover art.
- Any time the instinct is "generate an image" for something decorative or evocative. Stop and pull a real painting instead.
- NOT for: product screenshots, UI mockups, data charts, logos, or claim-driven explanatory diagrams (those are editorial-illustrations / real captures).
## Decision: which source
1. **Met -> Cleveland -> SMK first.** All keyless, one JSON hop, CC0/PD, broad collections. Fastest path to a hi-res image.
2. **Need Dutch/Flemish masters or decorative arts?** Rijksmuseum (keyless, 3 hops).
3. **Need European antiquities/photography and keyword isn't essential?** Getty (keyless, SPARQL).