CtrlK
BlogDocsLog inGet started
Tessl Logo

speckit-git-initialize

Initialize a Git repository with an initial commit

78

1.26x
Quality

70%

Does it follow best practices?

Impact

90%

1.26x

Average score across 3 eval scenarios

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

The canonical home for this skill is speckit-git-initialize in unoplatform/uno

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 for a simple single-purpose skill, with concrete commands and clear error handling. The only mild gap is the lack of a validate-retry feedback loop, though the operation is not destructive.

DimensionReasoningScore

Conciseness

The body is lean, assumes Git knowledge, and uses concrete paths/commands with only minor re-explanation (the 'script handles all checks internally' list restates the fallback), fitting 'efficient; minor instances of over-explanation' above the padded 3 and below the perfectly lean 5.

4 / 5

Actionability

It gives concrete script paths and copy-paste-ready fallback commands for both Bash ('git init && git add . && git commit -m ...') and PowerShell, covering the common cases fully executably.

5 / 5

Workflow Clarity

The sequence (run script or fallback → init/add/commit) is clear with an explicit error feedback loop ('surface the error... stop rather than continuing'), but there is no validate-then-retry loop, matching 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

At under 50 lines with a single task and no need for external references, the well-organized Execution/Customization/Output/Graceful Degradation sections meet the simple-skill exception for a top score.

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 concise and names a clear, concrete action but omits any 'when to use' trigger guidance, which caps completeness and trigger coverage. It is specific and distinct but not comprehensive.

Suggestions

Add a 'Use when...' clause stating the triggering context (e.g. 'Use when setting up a new spec-kit project that needs version control').

Broaden trigger terms with natural synonyms such as 'git init', 'version control', or 'first commit' to improve keyword coverage.

Mention staging (git add) or default branch setup in the description to lift specificity from 1-2 actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

The phrase 'Initialize a Git repository with an initial commit' names the domain and two concrete actions (init, commit) but omits staging/branch details, matching the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action 4 or 5.

3 / 5

Completeness

It clearly answers 'what' (initialize a Git repo with an initial commit) but offers no 'Use when...' trigger guidance, so per the boundary guideline a clear 'what' with missing 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

'Git repository' and 'initial commit' are natural terms a user might say, but coverage is thin with no synonyms or file extensions, fitting 'some relevant keywords but missing common variations' rather than the broader 4.

3 / 5

Distinctiveness Conflict Risk

Repo initialization is a specific niche unlikely to fire for unrelated skills, though 'Git repository' is broad enough to overlap with sibling git commands, placing it just below the minimal-conflict 5 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
mixpanel/mixpanel-headless
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.