tessl install https://github.com/softaworks/agent-toolkit --skill commit-workgithub.com/softaworks/agent-toolkit
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
Average Score
97%
Content
100%
Description
100%
Generated
Validations
Total score
11/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md line count is 56 (<= 500) | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'commit-work' | |
description_field 'description' field is valid (267 chars) | |
description_voice 'description' uses third person voice | |
description_trigger_hint Description includes an explicit trigger hint | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' field not present (optional) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys No unknown frontmatter keys found | |
body_present SKILL.md body is present | |
body_examples No examples detected (no code fences and no 'Example' wording) | |
body_output_format No obvious output/return/format terms detected; consider specifying expected outputs | |
body_steps No step-by-step structure detected (no ordered list); consider adding a simple workflow |
Content
Total score
12/12| Dimension | Score |
|---|---|
conciseness The content is lean and efficient, using bullet points and checklists without explaining basic git concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3/3 |
actionability Provides specific, executable git commands throughout (git add -p, git diff --cached, git restore --staged -p). The workflow is concrete with exact commands to run at each step. | 3/3 |
workflow_clarity Clear 8-step numbered workflow with explicit validation checkpoints (step 4 sanity checks, step 5 description test, step 7 verification). Includes feedback loop guidance ('go back to step 2' if commit is too big). | 3/3 |
progressive_disclosure Well-organized with clear sections (Goal, Inputs, Workflow, Deliverable). References external file (commit-message-template.md) appropriately for detailed template without bloating the main skill. | 3/3 |
Overall Assessment
This is an excellent skill that demonstrates best practices: it's concise yet comprehensive, provides executable commands at every step, includes explicit validation checkpoints and feedback loops, and appropriately references external resources. The checklist format makes it easy to follow and the split criteria in step 2 provide concrete guidance for decision-making.
Description
Total score
12/12| Dimension | Score |
|---|---|
specificity Lists multiple specific concrete actions: 'review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits)'. These are distinct, actionable capabilities. | 3/3 |
completeness Clearly answers both what ('Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages') AND when ('Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits'). | 3/3 |
trigger_term_quality Includes natural keywords users would say: 'commit', 'commit message', 'stage changes', 'split work into multiple commits'. These match common user vocabulary when working with git. | 3/3 |
distinctiveness_conflict_risk Clear niche focused specifically on git commits with distinct triggers like 'commit', 'stage changes', 'Conventional Commits'. Unlikely to conflict with general code or document skills. | 3/3 |
Overall Assessment
This is a well-crafted skill description that excels across all dimensions. It uses third person voice, lists specific concrete actions, includes natural trigger terms users would actually say, and explicitly provides both 'what' and 'when' guidance. The mention of 'Conventional Commits' adds specificity that helps distinguish it from generic git skills.