adopt

Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.

Quality

81%

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

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 thorough, highly actionable multi-phase audit workflow with strong sequencing and verification loops. It loses points on conciseness due to cross-phase repetition and on progressive disclosure because it is a long single file with no external references despite containing a large embeddable plan template.

Suggestions

De-duplicate the "existing stories" explanation and infrastructure bootstrap ordering so each appears once, with later phases referring back rather than restating.

Extract the Phase 6 adoption-plan markdown template (and possibly the per-artifact audit tables) into a reference file under references/, keeping SKILL.md as an overview that links to it.

Dimension	Reasoning	Score
Conciseness	Largely efficient domain-specific guidance, but content is repeated across phases — the "existing stories" rationale appears in Phase 4, the Phase 6 template, and the Collaborative Protocol, and infrastructure bootstrap ordering is restated in both Phase 4 and Phase 6 — so it could be tightened.	2 / 3
Actionability	Highly executable: exact file paths, grep patterns, heading patterns, valid status-value lists, and concrete commands like "/architecture-decision retrofit docs/architecture/adr-[NNNN]-[slug].md" make the guidance copy-paste ready.	3 / 3
Workflow Clarity	Seven phases are clearly sequenced with explicit AskUserQuestion checkpoints (fresh-project gate, pre-write confirmation, gap preview) and a verify feedback loop ("Re-run /adopt ... to verify all blocking and high gaps are resolved").	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~434-line monolith; the full Phase 6 adoption-plan markdown template and detailed audit tables are inline content that could be split into reference files rather than kept in SKILL.md.	2 / 3
	Total	10 / 12 Passed

Description

85%

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 strong, specific description with explicit trigger guidance and excellent distinctiveness from a sibling skill. Its only weakness is jargon-heavy phrasing that limits how naturally users would voice the trigger terms.

Suggestions

Soften niche jargon ("brownfield onboarding", "template format compliance") toward phrasing users would naturally say, e.g. "Use when you join an existing project or upgrade the template".

Consider mirroring common user phrasings like "migrate an existing project" or "check my project works with the template" to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "audits existing project artifacts for template format compliance", "classifies gaps by impact", and "produces a numbered migration plan" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly answers both what (audits, classifies, produces a migration plan) and when, with an explicit "Run this when..." trigger clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Explicit triggers exist ("Run this when joining an in-progress project or upgrading from an older template version") but the surrounding vocabulary ("brownfield onboarding", "template format compliance") is niche jargon rather than broadly natural terms users would say.	2 / 3
Distinctiveness Conflict Risk	Explicitly distinguishes itself from a sibling skill — "Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work" — giving it a clear niche unlikely to conflict.	3 / 3
	Total	11 / 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/adopt/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.