create-repo-skill

Create or update a skill in this repository the right way — canonical home in .agents/skills, internal-vs-public marking, symlink mirroring into .claude/skills, and public docs registration for product skills. Use whenever adding a new skill, converting a workflow into a skill, or when .claude/skills and .agents/skills look out of sync.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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 dense but highly actionable skill body that leans on genuinely repo-specific invariants Claude would not know. Validation is present via the sync check but is somewhat decoupled from the main creation workflow.

Suggestions

Fold a one-line 'run the sync check below' verification step into the numbered creation flow so validation is inline rather than only in a trailing section.

Trim historical justifications (e.g. 'this happened to three skills before symlinks became the rule') to keep the invariants lean, or move them to a brief rationale note.

Consider extracting the long public-skill registration path list (step 2's sub-bullet) into a references file to reduce inline density and improve navigability.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but explanatory asides like 'this happened to three skills before symlinks became the rule' and 'Codex's installer silently skips symlinked files' add rationale that could be trimmed in places.	4 / 5
Actionability	Fully executable guidance: copy-paste commands (`mkdir`, `ln -s ../../.agents/skills/<name>`, `pnpm format:write`, `pnpm sync-plugin-skills`, `pnpm ci:check`) and exact file paths to edit cover the common cases.	5 / 5
Workflow Clarity	A clear numbered creation flow and a separate sync-check loop with explicit drift feedback ('Anything flagged: move canonical content...'), but the validation checkpoint lives in its own section rather than inline in the creation steps, leaving a minor gap.	4 / 5
Progressive Disclosure	Well-organized into clear sections (invariants, creating a skill, sync check) with no bundle files needed, though the long inlined path-list bullet in step 2 is dense and could be split out.	4 / 5
	Total	17 / 20 Passed

Description

92%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 strong, specific description that clearly states both the capability and explicit use-when triggers in third person. Trigger-term coverage is good though not exhaustive of synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create or update a skill', 'canonical home in .agents/skills', 'internal-vs-public marking', 'symlink mirroring into .claude/skills', and 'public docs registration' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' ('Create or update a skill... the right way') and 'when' ('Use whenever adding a new skill, converting a workflow into a skill, or when... out of sync') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural triggers like 'adding a new skill', 'converting a workflow into a skill', and '.agents/skills and .claude/skills look out of sync' map well to what a user would say, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a narrow, repo-specific niche (skill scaffolding under .agents/skills vs .claude/skills) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: every-app/open-seo
Path: .agents/skills/create-repo-skill/SKILL.md
Commit: 7b9ee0e

Reviewed: 2 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.