speckit-git-initialize

Initialize a Git repository with an initial commit

1.26x

Quality

48%

Does it follow best practices?

Impact

90%

1.26x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/speckit-git-initialize/SKILL.md

Quality

Discovery

32%

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 very terse—it communicates the basic action but lacks a 'Use when...' clause, natural trigger term variations, and sufficient detail to distinguish it from other Git-related skills. It reads more like a one-line summary than a skill description designed for selection among many options.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to create a new Git repository, run git init, or set up a project with version control from scratch.'

Include natural trigger term variations such as 'git init', 'new repo', 'start a new project', 'set up version control', and 'first commit'.

Expand the 'what' portion to list specific actions like creating .gitignore, setting up default branch, and making the first commit with a standard message.

Dimension	Reasoning	Score
Specificity	Names a specific domain (Git) and two actions (initialize a repository, make an initial commit), but doesn't list additional concrete actions or details beyond the basic task.	2 / 3
Completeness	Describes what the skill does but completely lacks any 'Use when...' clause or explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also quite thin, warranting a score of 1.	1 / 3
Trigger Term Quality	Includes natural keywords like 'Git repository' and 'initial commit' that users might say, but misses common variations like 'git init', 'new repo', 'set up a repo', 'first commit', or 'start a project'.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to Git initialization, but could overlap with broader Git skills or project scaffolding skills since it doesn't clearly delineate its niche or when it should be chosen over other Git-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a functional skill with clear, executable fallback commands and good structure. Its main weaknesses are some verbosity in the Customization and Graceful Degradation sections that explain things Claude already knows, and the lack of explicit post-execution verification steps. The dual platform support (Bash/PowerShell) is well handled.

Suggestions

Trim the Customization section to a single line like 'Replace the script to add project-specific steps (e.g., .gitignore templates, LFS setup, hooks)' rather than listing each option separately.

Add a brief verification step after execution, such as 'Verify: `git log --oneline` should show the initial commit.'

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some unnecessary sections. The 'Customization' section lists things Claude already knows about Git configuration, and the 'Graceful Degradation' section repeats information already covered in the 'Execution' section (script handles checks internally). Could be tightened.	2 / 3
Actionability	Provides concrete, executable commands for both Bash and PowerShell, with specific script paths and fallback commands that are copy-paste ready. The fallback commands are fully executable.	3 / 3
Workflow Clarity	The workflow is present but lacks explicit validation checkpoints. The skill mentions error handling behavior but doesn't provide a clear sequence for verifying success beyond checking for the output message. For a destructive operation (initializing a repo and making a commit), there's no explicit verification step like checking `git log` or `git status` after execution.	2 / 3
Progressive Disclosure	The content is reasonably structured with clear sections, but the Customization and Graceful Degradation sections add inline content that could be trimmed or referenced elsewhere. No bundle files are provided, so the referenced script paths (.specify/extensions/git/scripts/...) cannot be verified, though the structure is reasonable for a standalone skill.	2 / 3
	Total	9 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: mixpanel/mixpanel-headless
Commit: 3ce3191

Reviewed: 2 days 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.