CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

art-bible

Author the Art Bible — visual identity gating asset production. Run before /map-systems.

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

85%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.

A highly actionable, well-sequenced orchestration skill with excellent progressive disclosure — every step is executable, gated by user approval, and specialist content is correctly deferred to conditionally-loaded reference files. Its only real weakness is token efficiency: repeated per-section boilerplate, a next-steps section that duplicates Phase 6, and justificatory asides inflate the ~410-line body.

Suggestions

Delete the trailing "Recommended Next Steps" section — Phase 6's state-checked option pool already covers every option it lists.

State the approval→write rule once (the Collaborative Protocol section already does) and drop the per-section "Write the approved section to file immediately" repetitions.

Compress the spawn-policy rationale asides to one sentence each (e.g., "one call for 2–4 because they are interdependent; per-section approval and writes unchanged").

DimensionReasoningScore

Conciseness

The body is dense with operational specifics and never explains background concepts, but it carries noticeable redundancy that could be tightened: "Write the approved section to file immediately" is repeated per section though the Collaborative Protocol already states it once, the trailing "Recommended Next Steps" section duplicates Phase 6's next-step option pool, and multi-sentence design-rationale asides ("This is not reduced specialist involvement…", "Separate calls would ask the agent to reason about colour…") pad the spawn policy. This sits at "mostly efficient but includes some unnecessary explanation or could be tightened" — not anchor 2, since the padding is repetition and rationale rather than concept explanation.

3 / 5

Actionability

Guidance is fully executable throughout: exact grep patterns with flags ("Grep pattern=\"^## \" path=\"design/art/art-bible.md\" output_mode=\"content\" -n"), verbatim AskUserQuestion option strings, complete agent-delegation prompts, exact gate output tokens ("AD-ART-BIBLE: APPROVE") and exact header/sign-off strings to write. For an instruction-only skill this is copy-paste-ready and covers the common cases, matching anchor 5.

5 / 5

Workflow Clarity

Phases 0–6 are clearly sequenced with explicit validation checkpoints: per-section user approval via the "[A] Lock this in and write it" gate, the AD-ART-BIBLE checklist run against the file on disk, defined feedback loops ("On Revise flagged items, or to resolve a REJECT, re-draft each flagged section…"), NOT-ASSESSED handling, retrofit-mode status rules, and a hard failure path when no game concept exists. This matches anchor 5's "explicit validation steps; feedback loops for error recovery; checklists".

5 / 5

Progressive Disclosure

The bundle structure is exemplary: three real reference files (references/lens-art-director.md, lens-ux-designer.md, lens-technical-artist.md — all verified to exist), referenced one level deep with conditional load instructions that say exactly when to read each ("read references/lens-art-director.md before the first of those sections", "Outside Sections 7 and 8, do not load…") and when not to. Specialist detail is correctly split out of SKILL.md, matching anchor 5's well-signaled one-level-deep references with easy navigation.

5 / 5

Total

18

/

20

Passed

Description

73%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 terse, third-person description with a clear niche and an explicit (if sequencing-based) when-to-run cue. Its main weakness is thin capability coverage — a single action verb plus a purpose clause — and missing natural synonym triggers such as "art direction" or "style guide".

Suggestions

Enumerate 1-2 more concrete capabilities in the description (e.g., "define visual identity, color system, and asset standards across 9 sections") so specificity goes beyond a single action verb.

Add an explicit user-trigger clause, e.g., "Use when the user asks for an art bible, art direction, or a visual style guide," to complement the pipeline cue "Run before /map-systems".

Include natural synonyms such as "art direction" or "style guide" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Author the Art Bible — visual identity gating asset production" names the domain and exactly one concrete action (authoring), with the rest of the line being a purpose clause rather than actions. It matches "names domain and 1-2 concrete actions, but not comprehensive"; it does not list several specific actions (anchor 4) and is more concrete than the minimal/generic action of anchor 2.

3 / 5

Completeness

The "what" is clear ("Author the Art Bible — visual identity gating asset production") and a "when" is explicitly stated ("Run before /map-systems"), so both halves are present as in anchor 4. It is not anchor 5 because the "when" is pipeline sequencing rather than concrete user-trigger phrases, and not anchor 3 because the when is explicitly stated, not merely implied.

4 / 5

Trigger Term Quality

Natural domain keywords are present — "Art Bible", "visual identity", "asset production", "/map-systems" — giving good coverage beyond the single-keyword case of anchor 3. It falls short of anchor 5 because common variations users might say ("art direction", "style guide", "visual style") are missing.

4 / 5

Distinctiveness Conflict Risk

"Art Bible" is a clear niche artifact with distinct triggers (visual identity, asset production, the /map-systems pipeline position), making it highly unlikely to fire for the wrong skill. It clearly matches anchor 5's "clear niche with distinct triggers; minimal conflict risk".

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/art-bible/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.