CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

consistency-check

Scan GDDs against the entity registry for cross-document conflicts. Grep-first approach targets conflicting sections, different stats.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/consistency-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a strong operational skill: every phase is directly executable with exact commands, templates, and validation/feedback loops, and edge cases (empty registry, no GDDs in scope, unregistered names, stale registry) all have explicit handling. The main cost is length — duplicated tier rules and justificatory asides could be trimmed or split into reference files without losing any instruction.

DimensionReasoningScore

Conciseness

The body is dense with project-specific instruction and almost never explains concepts Claude already knows, but it carries several rationale asides that assume Claude needs convincing ("nothing was compared, so there is no PASS to give", the Phase 3 "core optimization" arithmetic, the Phase 7 breadcrumb paragraph), and the workflow-tier rules are explained twice (intro block and Phase 3). Mostly efficient but could be tightened — not 4, where over-explanation would be only minor.

3 / 5

Actionability

Guidance is fully executable throughout: exact tool invocations (Grep with pattern, glob and -C 3; Read with path; a copy-paste git log command), a complete report template, exact file paths, YAML comment formats, and concrete AskUserQuestion options. For an instruction-only skill this is copy-paste-ready and covers the common cases.

5 / 5

Workflow Clarity

Seven explicitly sequenced phases each with inputs, stop conditions for empty registries/scopes (NOT ASSESSED verdicts), and clear outputs; the write path has real validation checkpoints — re-read-before-edit anchoring, `registry.sh validate` with fix-before-verdict and a fallback when the script is missing, plus re-run-to-confirm loops. This matches the explicit-validation-with-feedback-loops anchor.

5 / 5

Progressive Disclosure

No bundle files exist, so everything must live in SKILL.md; the file is well-sectioned per phase and points to external mode docs (.claude/docs/automation-modes.md, workflow-modes.md) instead of inlining them, and the referenced project files are real operational targets. Not 5 because ~370 lines with a 40-line report template and the reflexion-log format inline is content that could split into reference files.

4 / 5

Total

17

/

20

Passed

Description

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

The description states a clear, domain-specific capability in third person, but reads like a compressed feature list rather than trigger guidance. It lacks any "use when" clause and omits the natural synonyms (consistency, inconsistencies) a user would most likely say, capping both completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to check consistency, find cross-document conflicts or contradictions between GDDs, or verify GDD values against the entity registry."

Replace the telegraphic "different stats" fragment with concrete additional actions (e.g. "flags stale registry entries and writes a conflict report") to broaden both specificity and trigger coverage.

Cut implementation jargon like "Grep-first approach" from the description — it is not a term a user would say when they need this skill — and favor user-facing synonyms such as "inconsistencies" or "mismatches".

DimensionReasoningScore

Specificity

"Scan GDDs against the entity registry for cross-document conflicts" names the domain plus one concrete action, and "Grep-first approach targets conflicting sections" adds a method detail — but that is only 1-2 actions with no mention of reporting, stale-registry detection, or corrections, matching the 'not comprehensive' anchor rather than 'several specific actions'.

3 / 5

Completeness

The "what" is clear (scan GDDs against the registry for conflicts), but there is no "Use when..." clause or any equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. Not 2 because the "what" is concrete, not vague.

3 / 5

Trigger Term Quality

It includes relevant domain keywords ("GDDs", "entity registry", "cross-document conflicts") but misses the natural variations users would actually say — "consistency", "inconsistencies", "contradictions" — while "Grep-first approach" is implementation jargon rather than a user trigger, matching 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The GDD/entity-registry niche is specific enough to be mostly distinct, but the skill ecosystem includes /review-all-gdds and /design-review which also cover GDD checking, and the description offers no distinguishing trigger phrase — 'mostly distinct; minor overlap risk with closely related skills'. Not 5 because distinct triggers are absent.

4 / 5

Total

13

/

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/consistency-check/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.