CtrlK
BlogDocsLog inGet started
Tessl Logo

speckit-init

Use when the user asks to install, initialize, integrate, upgrade, or document GitHub Spec Kit. Creates a repository-specific constitution and SPECKITINIT.md with complete copy-paste workflows using the public workflow catalog. Do NOT use to implement application features; use the installed Spec Kit implementation command.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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-structured, lean instruction-only skill with a clear sequenced workflow and a strong completion/validation standard. Minor opportunities exist to tighten section 3-4 prose and include more in-skill executable examples.

Suggestions

Tighten the section 3 curation bullet list and section 4 pack descriptions to reduce density and improve skim-ability.

Add one or two concrete copy-paste example invocations (e.g. a sample verified integration command block) to raise in-skill actionability.

Consider extracting the four command-pack specification in section 4 into a referenced file to strengthen progressive disclosure for this longer skill.

DimensionReasoningScore

Conciseness

Mostly lean imperative prose that assumes Claude's competence without explaining what Spec Kit is, but the dense catalog-curation bullets in section 3 and the long four-pack exposition in section 4 could be tightened further.

4 / 5

Actionability

Specific, actionable guidance with concrete commands ('specify --help', 'specify integration --help') and named command packs/steps, but in-skill executable commands are sparse since the skill directs Claude to generate copy-paste blocks rather than providing them.

4 / 5

Workflow Clarity

A clear six-step sequence culminating in an explicit completion standard with validation checkpoints ('validate shell commands using help or a safe dry run', 'inspect the final diff') and a feedback/error-reporting loop, matching the anchor-5 example.

5 / 5

Progressive Disclosure

Well-organized into six clearly numbered sections with a single clearly-signaled one-level external reference (the public workflow catalog); content is appropriately self-contained, though the body exceeds the simple-skill length where a 5 would be automatic.

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 description that explicitly states both capabilities and trigger conditions, with a clear negative boundary distinguishing it from the implementation skill. Only minor trigger-synonym coverage is missing.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('install, initialize, integrate, upgrade, or document', 'Creates a repository-specific constitution and SPECKITINIT.md') with comprehensive coverage of the setup domain, matching the anchor-5 example.

5 / 5

Completeness

Explicitly answers both what ('Creates a repository-specific constitution and SPECKITINIT.md with complete copy-paste workflows') and when ('Use when the user asks to install, initialize, integrate, upgrade, or document GitHub Spec Kit') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger verbs plus the named product 'GitHub Spec Kit', but a few common variations like 'setup'/'onboarding' are absent, so it sits just below the comprehensive anchor-5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (setup/init) with an explicit negative boundary ('Do NOT use to implement application features') that minimizes wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
administrakt0r/pro-skills-repo-administraktor
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.