commit-work
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.
Install with Tessl CLI
npx tessl i github:softaworks/agent-toolkit --skill commit-workOverall
score
97%
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
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.
| Dimension | Reasoning | 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 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
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.
| Dimension | Reasoning | 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 |
Total | 12 / 12 Passed |
Validation
69%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- Reviewed
Table of Contents
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.