consistency-check

Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variables. Grep-first approach — reads registry then targets only conflicting GDD sections rather than full document reads.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

77%

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 workflow with executable commands, concrete conflict rules, and validation loops, held back mainly by verbosity and a monolithic single-file structure.

Suggestions

Trim the 'core optimization' rationale paragraph and the duplicated intro sentence to reduce token load — the grep commands already demonstrate the approach.

Move the large Phase 5 report template and Phase 6b reflexion-log template into a reference file (e.g. references/report-templates.md) referenced one level deep, to improve progressive disclosure.

Cut the meta-commentary comparing this skill to /design-system and /review-all-gdds unless it directly changes execution.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the 'core optimization' rationale paragraph, the intro that re-states the description, and the meta-commentary about other skills add tokens that could be trimmed without losing clarity.	2 / 3
Actionability	Provides fully executable grep/git commands with exact flags, concrete conflict-detection rules, and copy-paste-ready report and reflexion-log templates.	3 / 3
Workflow Clarity	Seven clearly sequenced phases with explicit guard conditions ('If the file does not exist... Stop and exit'), conflict classification, and re-run-to-verify feedback loops for this batch operation.	3 / 3
Progressive Disclosure	The ~300-line skill is a single monolithic file with no bundle references; it is well-sectioned but the long report/log templates that could be separated are inline, and it exceeds the simple-skill threshold that would allow a 3.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific, distinctive description with concrete conflict-detection actions, weakened by domain jargon instead of natural trigger terms and a missing explicit 'when to use' clause.

Suggestions

Add a 'Use when...' clause to the description (e.g., 'Use when checking GDDs for conflicting stats, item values, or formula variables before architecture or review') so the trigger guidance is in the frontmatter, not just the body.

Swap some domain jargon for natural trigger terms a user would actually say, such as 'consistency check', 'find conflicting values', or 'verify GDDs agree'.

Consider adding a user-facing keyword like 'cross-review' or 'consistency' early in the description to improve natural-language matching.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (scan GDDs against the registry, detect inconsistencies) and enumerates specific conflict types ('same entity with different stats, same item with different values, same formula with different variables'), all in third person.	3 / 3
Completeness	The description clearly states what the skill does but lacks an explicit 'Use when...' trigger clause; the when-guidance lives only in the body, so completeness is capped at 2.	2 / 3
Trigger Term Quality	Keywords like 'GDDs', 'entity registry', and 'cross-document inconsistencies' are domain-internal jargon rather than natural terms a user would say, and common natural variations ('check consistency', 'find conflicts') are absent.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche — cross-document consistency checking against a game-design entity registry — making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 984023d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.