CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

project-stage-detect

Analyze project state, detect stage, identify gaps, recommend next steps. 'Where are we in development?'

Quality

78%

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/project-stage-detect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 well-engineered diagnostic workflow with exceptional sequencing and validation logic, concrete commands, and copy-paste question scripts. Its weaknesses are repetition of the workflow-tier rationale across three sections and a handful of estimate fields (percentages, coverage) left without a stated method.

Suggestions

State the workflow-tier gap rules once (e.g. in step 3) and reference them from the opening blockquote and Follow-Up Actions instead of re-explaining the rationale each time.

Trim the persuasive asides (e.g. "the one thing it must never be... it would report Release for a project whose artifacts match its own Pre-Production row") to a single directive sentence.

Give a rough method for the report's [X%] completeness figures and the LOC/test-coverage estimates (e.g. bucket scales) so the template is fully computable.

DimensionReasoningScore

Conciseness

The body is mostly efficient — it teaches project-specific rules rather than concepts Claude already knows — but the workflow-tier point is re-explained three times (the opening blockquote, step 3, Follow-Up Actions) and blockquotes like "a stage detector that cannot contradict its input is the one thing it must never be" are persuasive padding that could be trimmed. This goes beyond the "minor instances of over-explanation" of a 4.

3 / 5

Actionability

Highly executable throughout: the exact invocation "bash .claude/scripts/artifact-check.sh" with constraints, per-directory checklists, copy-paste clarifying questions, a stage table, and a full report template. Not 5 because a few details remain unguided — the report's "[X%]" completeness figures have no computation method and "Estimate test coverage (rough heuristic)" / "Estimate lines of code (rough scale)" give no heuristic or scale.

4 / 5

Workflow Clarity

Six clearly sequenced steps with explicit validation logic: a deterministic pass first, a forced compare of configured vs. observed stage with a named escalation path, a first-match-wins Stage Confidence ordering (FAIL > CONCERNS > NOT ASSESSED > PASS) with reasoning for each rank, and an approval gate before any write. This is a read-only diagnostic skill, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent), and the body is well-sectioned with clearly signaled one-level-deep pointers to project docs (templates, automation-modes, code-root-resolution). Not 5 because at ~280 lines some self-contained material — the per-tier gap rules and the role-filtered recommendation lists — could live in reference files to keep SKILL.md a leaner overview.

4 / 5

Total

16

/

20

Passed

Description

75%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 concise, action-oriented description that names four concrete capabilities and includes a natural trigger question. Its main limitations are the slightly abstract "project state" object and an implicit rather than fully explicit "Use when..." trigger clause.

DimensionReasoningScore

Specificity

"Analyze project state, detect stage, identify gaps, recommend next steps" lists several specific, distinct actions covering the skill's capabilities. Falls short of 5 because "project state" is more abstract than anchor-5 examples with concrete objects (e.g. "extract text and tables from PDF files"), and beyond 3 because multiple actions are enumerated rather than 1-2.

4 / 5

Completeness

The "what" is explicit (analyze, detect, identify gaps, recommend) and the quoted "Where are we in development?" serves as equivalent explicit trigger guidance, so the missing-'Use when' cap at 3 does not apply. Not 5 because the "when" is a single implicit trigger question rather than clearly stated concrete trigger phrases like "Use when the user asks...".

4 / 5

Trigger Term Quality

"project state", "stage", "gaps", "next steps", and the quoted question "Where are we in development?" are natural phrases users would say when needing this skill. Not 5: missing common synonyms/variations like "milestone", "project health", "audit", or "onboarding" that would broaden trigger coverage.

4 / 5

Distinctiveness Conflict Risk

The stage-detection/gap-analysis framing carves out a fairly distinct niche with trigger terms unlikely to fire for unrelated skills. Not 5 because "analyze project state" and "identify gaps" have minor overlap risk with generic audit/review/onboarding skills.

4 / 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/project-stage-detect/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.