git-workflow
Defines branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, task tracking conventions. Load when committing, pushing, or opening PRs.
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 skill description that concisely covers what the skill defines (branch naming, PR templates, commit message format, escalation policy, task tracking) and when to use it (committing, pushing, opening PRs). It uses third person voice appropriately and includes natural trigger terms that align well with user actions in git workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/topics: branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, and task tracking conventions. | 3 / 3 |
Completeness | Clearly answers both 'what' (defines branch naming conventions, PR template requirements, commit message format, escalation policy, task tracking) and 'when' ('Load when committing, pushing, or opening PRs') with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users and Claude would encounter: 'committing', 'pushing', 'opening PRs', 'branch naming', 'commit message', 'PR template'. These are terms that naturally arise in git workflow contexts. | 3 / 3 |
Distinctiveness Conflict Risk | Targets a clear niche of git workflow conventions and policies. The specific combination of branch naming, PR templates, commit messages, and escalation policy is distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that efficiently communicates Git workflow conventions with concrete examples and actionable commands. The PR creation shell snippet addressing the zsh heredoc gotcha is particularly valuable. The only weakness is that external references (discovered-issues-policy snippet, tracker-config.md, task-management skill) cannot be fully verified and could be more clearly linked.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line carries actionable information. No unnecessary explanations of what Git is or how PRs work. The table format is efficient, and the PR body-file technique addresses a real gotcha without over-explaining. | 3 / 3 |
Actionability | Provides concrete branch naming patterns, exact commit message format with example, executable shell commands for PR creation with the --body-file workaround, and specific fallback instructions when MCP tools are unavailable. Copy-paste ready. | 3 / 3 |
Workflow Clarity | The delivery checklist is a clear 5-step sequence covering branch creation through issue update. The discovered-issues policy and MCP-unavailable fallback provide error recovery paths. For a process-oriented (non-destructive) workflow like Git branching/PRs, the steps are unambiguous and well-ordered. | 3 / 3 |
Progressive Disclosure | References to discovered-issues-policy snippet and task-management skill are present and one-level deep, which is good. However, the snippet path (../../snippets/discovered-issues-policy.md) and tracker-config.md cannot be verified since no bundle files are provided, and the references to 'task-management skill' and 'tracker-config.md' are somewhat vaguely signaled without clear links. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%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 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
7a69a05
- 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.