speckit-git-initialize

Initialize a Git repository with an initial commit

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-git-initialize/SKILL.md

Quality

Content

100%

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, fully actionable, and well-organized, with concrete commands for both shells and explicit graceful-degradation guidance for failure cases. It is an exemplar for a simple single-purpose skill.

Dimension	Reasoning	Score
Conciseness	The ~45-line body assumes Claude's competence (no explanation of what Git or commits are) and every section (Execution, Customization, Output, Graceful Degradation) earns its place without padding.	3 / 3
Actionability	Provides exact script paths and copy-paste-ready fallback commands for both Bash ("git init && git add . && git commit -m \"Initial commit from Specify template\"") and PowerShell, which are fully executable.	3 / 3
Workflow Clarity	As a simple single-task skill the action is unambiguous, and the Graceful Degradation section gives an explicit error-recovery checkpoint ("Stop this command rather than continuing with a partially initialized repository").	3 / 3
Progressive Disclosure	The skill is under 50 lines with no need for external references, and content is cleanly split into well-signaled sections, satisfying the simple-skill allowance for a top score.	3 / 3
	Total	12 / 12 Passed

Description

50%

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 concisely states the core action but omits any explicit trigger guidance, leaving the "when to use" question unanswered and limiting every dimension to the midpoint. Adding a Use-when clause and broader natural-language triggers would substantially improve it.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when setting up version control for a new project or when no Git repository exists yet") to answer when Claude should invoke this skill and raise completeness.

Broaden trigger term coverage with natural variations users actually say, such as "repo", "version control", and "first commit", to improve trigger_term_quality.

Mention the guardrail behaviors (skip if Git is missing or a repo already exists) in the description to add specificity and reduce overlap with other git skills.

Dimension	Reasoning	Score
Specificity	States concrete actions ("Initialize a Git repository" and "with an initial commit") but these describe a single setup workflow rather than multiple distinct actions, so it is not comprehensive like the 3-anchor example.	2 / 3
Completeness	It clearly answers what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	"Git repository" and "initial commit" are natural terms a user might say, but common variations like "repo", "version control", or "first commit" are missing.	2 / 3
Distinctiveness Conflict Risk	The action is specific to repository initialization, but without explicit trigger guidance it could still overlap with other git-related skills in the same domain.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: unoplatform/uno
Path: .claude/skills/speckit-git-initialize/SKILL.md
Commit: 5927220

Reviewed: about 15 hours 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.