speckit-git-feature

Create a feature branch with sequential or timestamp numbering

Quality

55%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

77%

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

This is a well-structured, actionable skill that provides clear execution paths for both Bash and PowerShell with specific commands and flags. The workflow is logically sequenced with prerequisite checks and graceful degradation. Minor improvements could be made in conciseness by trimming explanatory text and tightening the environment variable override section.

Suggestions

Tighten the 'Environment Variable Override' section — the bullet points explaining behavior could be condensed into a single sentence since Claude can infer the implications.

The 'User Input' boilerplate section ('You MUST consider the user input before proceeding') adds little value and could be removed or reduced to save tokens.

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some unnecessary sections like explaining what the user input is and the graceful degradation details that could be more terse. The environment variable override section is somewhat verbose for what it conveys.	2 / 3
Actionability	Provides exact command-line invocations for both Bash and PowerShell with all flags, specific file paths for configuration, and clear instructions on what flags to use and avoid. The guidance is concrete and copy-paste ready.	3 / 3
Workflow Clarity	Clear sequential workflow: check prerequisites → determine numbering mode (with explicit config lookup order) → generate short name → run script → handle output. Includes validation (git check), graceful degradation, and explicit constraints (run once, don't pass --number).	3 / 3
Progressive Disclosure	Content is well-structured with clear sections, but everything is inline in a single file. The references to external scripts and config files are present but no bundle files were provided to verify. The skill is moderately long and some sections (like environment variable override details) could potentially be separated.	2 / 3
	Total	10 / 12 Passed

Description

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 concise and identifies a specific task (creating numbered feature branches), but it lacks a 'Use when...' clause, misses common trigger term variations (e.g., 'git', 'branch naming'), and only describes a single action. It would benefit significantly from explicit trigger guidance and broader keyword coverage.

Suggestions

Add a 'Use when...' clause with trigger terms like 'create branch', 'git branch', 'new feature branch', 'branch naming convention'.

Expand the capability description to mention related actions such as naming conventions, branch prefixes, or integration with git workflows.

Include common file or tool references like 'git' to improve trigger term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names a specific action ('create a feature branch') and mentions numbering schemes ('sequential or timestamp numbering'), but only describes a single action rather than listing multiple concrete capabilities.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also thin—so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'feature branch' and 'numbering' that users might say, but misses common variations like 'git branch', 'branch naming', 'branch convention', or 'new branch'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'sequential or timestamp numbering' adds some distinctiveness, but 'feature branch' is a common concept that could overlap with general git workflow or branching skills.	2 / 3
	Total	7 / 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: fd7b9ba

Reviewed: 27 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.