CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 instruction-only skill body: clear sequenced workflow with explicit validation checkpoints, and the large catalog correctly externalized into a single well-signaled reference. Weakest points are repeated truthfulness reminders that could be consolidated and the absence of a small example skeleton for the command packs it mandates.

Suggestions

Consolidate the truthfulness/verified-evidence rules (currently repeated in sections 2, 3, 4, 5, and 6) into a single 'operating rules' statement to reduce token cost.

Add a short skeleton example of one command-pack block (invocation code block + verification terminal block) so the required SPECKITINIT.md format is concrete rather than only described.

Trim meta-instructions like 'Treat it as a reference library, not a document to copy' to a single imperative, since the surrounding bullet list already encodes the curation rules.

DimensionReasoningScore

Conciseness

Dense, non-obvious domain guidance with no filler explanations of concepts Claude already knows, but the truthfulness/verified-evidence theme recurs across sections 2-6 ('do not claim installation... succeeded', 'verified local evidence', 'Never claim that Spec Kit is installed... without filesystem and CLI evidence') and could be consolidated. Fits anchor 4 ('minor instances of over-explanation that could be trimmed'), not 5.

4 / 5

Actionability

Concrete commands ('specify --help', 'specify integration --help', the official repo URL), named files ('.specify/', 'specs/', 'SPECKITINIT.md'), the four required command packs, and the full ordered sequence (specify, clarify, plan, checklist, tasks, analyze, implement, converge). No example skeleton of a command pack is shown, but deferring exact '/speckit.*' syntax is explicitly justified as version-dependent and sourced from the installed integration, so this is mostly executable guidance with minor gaps (anchor 4).

4 / 5

Workflow Clarity

Clear six-step sequence (discover -> verify CLI -> curate catalog -> author command packs -> constitution/maintenance -> completion standard) with an explicit validation section: dry-run shell validation, link/fence/placeholder checks, diff inspection, and reporting skipped checks and unknowns. Error feedback is present ('If health checks fail, report that result and do not claim installation, upgrade, or integration succeeded'). Matches anchor 5.

5 / 5

Progressive Disclosure

The body is a skimmable overview of rules, and the 44KB workflow catalog is appropriately externalized to a clearly-signaled, verified, one-level-deep reference ('Read the [reusable Spec Kit workflow catalog](references/speckit-skills-guides-workflows/SPECKIT-workflows.md)'). Matches anchor 5: clear overview with well-signaled one-level-deep references.

5 / 5

Total

18

/

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: third-person voice, explicit what and when, concrete actions and outputs, and an explicit exclusion boundary. The only gap is a few missing natural trigger variants like 'set up' or 'setup'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('install, initialize, integrate, upgrade, or document') and concrete outputs ('Creates a repository-specific constitution and SPECKITINIT.md with complete copy-paste workflows'), comprehensively covering the skill's niche. Matches the score-5 anchor rather than 4 because action coverage has no gaps within its domain.

5 / 5

Completeness

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

5 / 5

Trigger Term Quality

Natural verbs users would say (install, initialize, integrate, upgrade, document) plus the product name 'GitHub Spec Kit'. Missing common variations such as 'set up/setup' and the lowercase 'speckit' spelling, so it fits anchor 4 ('a few natural terms missing') rather than 5's synonym saturation.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Spec Kit setup/authoring) with an explicit negative trigger ('Do NOT use to implement application features; use the installed Spec Kit implementation command') that disambiguates it from the implementation skill. Minimal conflict risk.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 1 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

administrakt0r/pro-skills-repo-administraktor

Path

skills/development-skills/speckit-init/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.