CtrlK
BlogDocsLog inGet started
Tessl Logo

speckit-git-initialize

Initialize a Git repository with an initial commit

60

Quality

70%

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/speckit-git-initialize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

The body is lean, highly actionable, and well-structured with clear fallbacks and graceful degradation. Its only gap is the lack of an explicit success-verification checkpoint in the workflow.

DimensionReasoningScore

Conciseness

The body is efficient with concrete commands and minimal padding; the Customization list and the "script handles all checks" bullets add slight explanation that could be trimmed, keeping it just below the lean anchor of 5.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands for both Bash and PowerShell plus explicit fallback commands, covering the common cases as the 5 anchor requires.

5 / 5

Workflow Clarity

The single action is unambiguous and the Graceful Degradation section supplies a feedback loop (surface errors, stop rather than continue partially), but there is no explicit verify-the-commit checkpoint, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and has no need for external bundle files; its clearly organized sections (Execution, Customization, Output, Graceful Degradation) satisfy the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

53%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 clear and specific about a single concrete action but omits any explicit trigger guidance and lacks synonyms users would naturally say. It is distinct but would benefit from a "Use when..." clause.

Suggestions

Add an explicit "Use when..." trigger clause, e.g. "Use when setting up a new spec-kit project that needs version control or when the user asks to initialize Git."

Broaden trigger terms with natural synonyms users actually say, such as "set up Git", "create a Git repo", or "version control setup".

Mention a second concrete capability (e.g., skipping when a repo already exists) to lift specificity above a single action.

DimensionReasoningScore

Specificity

"Initialize a Git repository with an initial commit" names the domain and one concrete action (the initial commit), matching the anchor for 1-2 concrete actions; it does not list multiple specific actions needed for a 4.

3 / 5

Completeness

It clearly states what the skill does but provides no "Use when..." trigger guidance, so per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "Initialize a Git repository" and "initial commit" are relevant but lack common synonyms users say ("set up Git", "create a repo", "version control"), fitting the anchor for some keywords missing variations.

3 / 5

Distinctiveness Conflict Risk

The description targets a clear niche (git initialization with an initial commit) with only minor overlap risk against other git-related skills, fitting the mostly-distinct anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
unoplatform/uno
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.