gitter
Create commits and pull requests for current git work. Use when the user wants to commit changes, open a pull request, or refresh a branch PR.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 strong, well-crafted description that concisely covers specific actions, includes natural trigger terms, and clearly separates the 'what' from the 'when'. It uses proper third-person voice and provides enough specificity to distinguish it from related git skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create commits', 'pull requests', and 'refresh a branch PR'. These are clear, actionable operations. | 3 / 3 |
Completeness | Clearly answers both what ('Create commits and pull requests for current git work') and when ('Use when the user wants to commit changes, open a pull request, or refresh a branch PR') with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'commit changes', 'open a pull request', 'refresh a branch PR', 'git work'. These are terms users naturally use when requesting these actions. | 3 / 3 |
Distinctiveness Conflict Risk | Focuses on a clear niche of git commit and PR operations. The specific triggers (commit, pull request, refresh branch PR) are distinct and unlikely to conflict with other skills like code review or git history analysis. | 3 / 3 |
Total | 12 / 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 well-structured dispatch skill that is admirably concise and clearly organized. Its main weakness is that all substantive guidance is delegated to external files that aren't provided in the bundle, making it impossible to verify the skill delivers actionable, validated workflows. The SKILL.md itself functions as a clean router but provides minimal standalone value.
Suggestions
Include the bundle files (commit.md, pr.md) so the skill can be fully evaluated — or inline at least the key commands (e.g., `git add`, `git commit`, `gh pr create`) as a quick reference.
Add brief inline descriptions of what each action does beyond the single phrase, e.g., 'commit: stages changed files and creates a commit with a conventional commit message' to improve actionability without sacrificing conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean — no unnecessary explanation, no padding. Every line serves a purpose: routing logic and action references. Assumes Claude's competence entirely. | 3 / 3 |
Actionability | The routing logic is clear, but the actual executable guidance lives entirely in referenced files (commit.md, pr.md) which are not provided. The SKILL.md itself contains no concrete commands or code examples. | 2 / 3 |
Workflow Clarity | The 3-step dispatch logic is clear and unambiguous, but since the actual workflows for committing and PR creation are delegated to external files (not provided), we cannot verify validation checkpoints or feedback loops for these potentially destructive git operations. | 2 / 3 |
Progressive Disclosure | Good structure with a concise overview pointing to one-level-deep references (commit.md, pr.md). However, no bundle files were provided, so we cannot verify the referenced files exist or contain appropriate content, and the navigation could benefit from brief inline summaries of what each action does beyond the minimal descriptions. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- shillem/cc-marketplace
- Commit
bc6a504
- 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.