CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is maximally lean and the delegation instructions themselves are unambiguous, but the skill provides essentially no standalone value: every piece of task guidance (API recipes, licensing rules, museum specifics) is externalized to files outside this bundle, none of which ship alongside it. A reader of this SKILL.md alone cannot perform the skill's task.

Suggestions

Inline the core of the playbook (or at least a quick-start recipe for one museum API plus the licensing rule) into SKILL.md so the body is actionable on its own, moving the full per-museum recipes into a references/ file that actually ships with the bundle.

Verify the referenced paths — .claude/skills/museum-art/SKILL.md, .agents/rules/cog.md, and .agents/agents/<name>.md are not present in this bundle; either ship them under references/ or make the paths resolvable.

Add a one-line overview of what the playbook covers (e.g., which museums and what steps) so the SKILL.md acts as an overview with one-level-deep references instead of a bare pointer.

DimensionReasoningScore

Conciseness

The body is four sentences with zero padding, no explanation of concepts Claude already knows, and no redundancy — 'Read .claude/skills/museum-art/SKILL.md and execute it exactly as written — that file is the authoritative playbook. Then follow .agents/rules/cog.md.' Every token earns its place, matching anchor 5.

5 / 5

Actionability

The written instructions are concrete — exact file paths to read and an explicit substitution rule ('invoke .agents/agents/<name>.md via invoke_subagent instead') — so it is above anchor 2's 'high-level hints'. But the skill's actual guidance (sourcing recipes, API usage, licensing rules) is entirely absent from the body, living only in an external file that is not part of this bundle, which fits anchor 3: 'some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

A clear two-step sequence — read and execute the playbook, then follow .agents/rules/cog.md — with an unambiguous conditional substitution rule for agent delegation. No validation checkpoints are present, but none are evidently needed for these non-destructive pointer steps, so this matches anchor 4's 'clear sequence with most checkpoints present; minor validation gaps' rather than 5's explicit validation/feedback loops.

4 / 5

Progressive Disclosure

The references are clearly signaled (explicit paths and roles: 'authoritative playbook', rules file, agent substitution), but the body contains no overview content of its own — it is pure indirection to .claude/skills/museum-art/SKILL.md, and no bundle files (references/, scripts/, assets/) exist to back any of it. That fits anchor 3 ('references present but not clearly signaled / content that should be separate is inline' territory) rather than 4, since there is no in-file content at all to be appropriately placed.

3 / 5

Total

15

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states a specific, credible capability (sourcing public-domain art from named museum APIs), contrasts it with the alternatives users would otherwise reach for, and gives an explicit trigger clause with concrete visual contexts. Its only weaknesses are the broad 'default move' claim, which slightly raises conflict risk with other image skills, and a few missing natural synonyms.

DimensionReasoningScore

Specificity

The description gives one concrete, highly specified action — 'Source authentic, high-res PUBLIC-DOMAIN artwork from museum open-access APIs' naming eight museums — plus 'Verified keyless recipes + licensing rules inside'. It is more than 'names domain and 1-2 concrete actions' (3) because sourcing scope, quality, licensing, and keyless access are all explicit, but it stops short of anchor 5's 'multiple specific concrete actions' since there is effectively a single core verb.

4 / 5

Completeness

Both what and when are explicit: 'Source authentic, high-res PUBLIC-DOMAIN artwork from museum open-access APIs… instead of AI-generated or generic-stock imagery' states the what, and 'The default move whenever a visual needs an aesthetic, credible image (blog heroes, decks, social cards, essay/spec figures)' is a concrete when-clause with named trigger contexts, matching anchor 5. It uses third person ('Source', 'The default move'), so no voice penalty applies.

5 / 5

Trigger Term Quality

Natural user-facing terms are present: 'artwork', 'aesthetic, credible image', 'blog heroes, decks, social cards, essay/spec figures', plus the museum names. Common synonyms such as 'picture', 'photo', 'illustration', or 'painting' are missing, so it fits anchor 4 ('good keyword coverage; a few natural terms missing') rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The museum open-access / public-domain niche is highly distinct with specific named institutions, but 'The default move whenever a visual needs an aesthetic, credible image' claims broad default territory that overlaps with generic image-sourcing or visualization skills — 'mostly distinct; minor overlap risk' (4) rather than 5's 'minimal conflict risk'.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

huytieu/COG-second-brain

Path

.agents/skills/museum-art/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.