CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

adopt

Brownfield audit — do existing artifacts actually work? Numbered migration plan. Unlike /project-stage-detect, checks compliance not existence.

Quality

73%

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/adopt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-engineered hub skill: the body is an efficient overview that precisely scopes modes, arguments, and collaboration rules while delegating all step detail to seven real one-level-deep reference files. The only notable inefficiency is the seven-fold verbatim repetition of the phase-read directive.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows, but the identical directive sentence ('Read references/N... now and follow it... Read it again if the conversation was compacted') is repeated verbatim across all seven phases and could collapse into a single line.

4 / 5

Actionability

Concrete specifics abound: an executable bang command, the exact output path 'docs/adoption-plan-[date].md', enumerated argument values (full/gdds/adrs/stories/infra), and an explicit config resolution chain (project.local.yaml -> project.yaml -> default collaborative). Scored 4 rather than 5 because the actual audit steps live entirely in the reference files, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

A strict Phase 1-7 sequence with real checkpoints: the audit must complete silently before presenting, the summary gates the write, and writing is always user-confirmed. Not 5 because there is no explicit validate-and-recover loop over the audit results themselves.

4 / 5

Progressive Disclosure

Verified against the actual bundle: all seven referenced files (references/1-detect.md through 7-first-action.md) exist, are exactly one level deep, and are clearly signaled at their point of use, while the body stays a pure overview with easy navigation.

5 / 5

Total

17

/

20

Passed

Description

57%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 is terse, distinct, and states its core capability clearly, but it lacks any explicit 'when to use' trigger guidance and only names the domain at a high level without the concrete artifact types it audits. It reads more like a positioning tagline than a complete trigger description.

Suggestions

Add an explicit 'Use when...' clause naming the situations that call for this skill (e.g., 'Use when adopting this template into an existing project, or when existing GDDs/ADRs/stories may not match the template's expected formats').

List the concrete artifact types audited (GDDs, ADRs, stories, registry/manifest/sprint-status/stage.txt) so the capability coverage matches what the skill actually does.

Include natural trigger synonyms such as 'adopt', 'onboard', 'existing project', and 'format check' alongside 'brownfield audit'.

DimensionReasoningScore

Specificity

Names the domain ('Brownfield audit') and 1-2 concrete actions ('checks compliance not existence', 'Numbered migration plan'), but omits the audited artifact types (GDDs, ADRs, stories, infra) and the output location, so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear (compliance audit plus a numbered migration plan), but no 'Use when...' clause or equivalent explicit trigger guidance exists; 'when' is only weakly implied by the contrast with /project-stage-detect, which caps this at 3.

3 / 5

Trigger Term Quality

Relevant keywords like 'audit', 'existing artifacts', and 'migration plan' are present, but natural variations users would actually say ('adopt', 'existing project', 'format check', 'onboard') are missing.

3 / 5

Distinctiveness Conflict Risk

'Unlike /project-stage-detect, checks compliance not existence' explicitly differentiates the skill from its single most-confusable sibling, establishing a clear niche with minimal conflict risk.

5 / 5

Total

14

/

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/adopt/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.