speckit-git-initialize

Initialize a Git repository with an initial commit

1.26x

Quality

76%

Does it follow best practices?

Impact

90%

1.26x

Average score across 3 eval scenarios

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%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 an exemplar of a lean, simple skill: exact commands for both Bash and PowerShell, an explicit fallback, stated success output, and thorough graceful-degradation behavior with no filler. Nothing material is missing for the task it describes.

Dimension	Reasoning	Score
Conciseness	The ~46-line body explains nothing Claude already knows and has no padded sections; every line in Execution, Customization, Output, and Graceful Degradation is load-bearing, matching the lean anchor.	5 / 5
Actionability	Concrete per-shell script paths plus copy-paste-ready fallback commands ("git init && git add . && git commit -m 'Initial commit from Specify template'") make the guidance fully executable.	5 / 5
Workflow Clarity	This is a simple single-purpose skill with an unambiguous action; internal skip conditions, the success output, and explicit failure behavior ("stop rather than continuing with a partially initialized repository") provide the needed checkpoints, and git init is neither destructive nor batch so the cap-3 rule does not apply.	5 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external reference files (the .specify paths point into the user's project, not a bundle), and is organized into clearly signaled sections, satisfying the simple-skill guideline for a top score.	5 / 5
	Total	20 / 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 unambiguous about what the skill does, but it is minimal: it lacks any "when to use" trigger clause and misses natural trigger variations, capping completeness and trigger-term quality. Distinctiveness is decent thanks to the narrow git-init niche.

Suggestions

Add an explicit trigger clause, e.g., "Use when setting up a new project for version control or when the user asks to initialize git, make the first commit, or run git init."

Include natural trigger variations and synonyms such as "git init", "set up version control", and "first commit" to improve trigger-term coverage.

Optionally mention what the initialization includes (e.g., initial commit of project files) to sharpen the what-clause without adding fluff.

Dimension	Reasoning	Score
Specificity	"Initialize a Git repository with an initial commit" names the domain and one or two concrete actions but offers no broader coverage (e.g., branch setup, .gitignore, staging), matching the anchor for 1-2 concrete actions rather than the several-action anchors above.	3 / 5
Completeness	The "what" is clear, but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; this matches the anchor-3 example of a clear what with no when.	3 / 5
Trigger Term Quality	"Git repository" and "initial commit" are relevant natural keywords, but common variations users would say — "git init", "set up version control", "first commit" — are missing, which is the anchor-3 pattern rather than good coverage with a few gaps.	3 / 5
Distinctiveness Conflict Risk	Repository initialization is a clear, narrow niche with minimal conflict risk, but the short description could still overlap with general Git or commit-related skills, fitting "mostly distinct; minor overlap risk" better than the fully distinct anchor 5.	4 / 5
	Total	13 / 20 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: mixpanel/mixpanel-headless
Path: .claude/skills/speckit-git-initialize/SKILL.md
Commit: aa4e414

Reviewed: 1 day 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.