git-workflow
Defines branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, and task tracking conventions. Load when committing, pushing, or opening PRs.
100
100%
Does it follow best practices?
Impact
Pending
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, includes natural trigger terms, and occupies a clear niche. Minor improvement could include additional trigger term variations like 'git', 'pull request', or 'merge request'.
| 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 conventions) and 'when' ('Load when committing, pushing, or opening PRs'). | 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 standards. 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
100%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-crafted convention/policy skill that is concise, actionable, and well-organized. It provides exact commands, naming patterns, and examples without over-explaining. The progressive disclosure is appropriate, delegating related policies to referenced files while keeping the core workflow self-contained.
| 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 checklist is tight. The discovered issues policy is delegated via reference rather than inlined. | 3 / 3 |
Actionability | Provides concrete branch naming patterns, exact commit message format with example ('TAS-42: Fix token refresh'), copy-paste ready PR creation command with flags, and specific fallback behavior when tools are unavailable. | 3 / 3 |
Workflow Clarity | The delivery checklist is a clear 5-step sequence covering branch creation through issue update. For this type of skill (conventions/policy rather than destructive operations), the workflow is unambiguous and complete. The MCP unavailability fallback provides an error recovery path. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections. References to external files (discovered-issues-policy snippet, tracker-config.md, task-management skill) are one level deep and clearly signaled. The skill stays focused on its scope without inlining referenced content. | 3 / 3 |
Total | 12 / 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
f5c8508
- 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.