git-workflow
Git workflow guide for the rc-unified-crm-extension monorepo. Covers commit message conventions, branching strategy, release process, and version bumping. Use when committing changes, creating branches, cutting releases, updating release notes, or asking about the project's Git conventions.
96
96%
Does it follow best practices?
Impact
93%
1.75xAverage score across 3 eval scenarios
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 clearly identifies its domain (Git workflow for a specific monorepo), lists concrete capabilities, and includes an explicit 'Use when...' clause with natural trigger terms. The description is concise, uses third-person voice, and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: commit message conventions, branching strategy, release process, version bumping. These are distinct, well-defined activities rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (Git workflow guide covering commit conventions, branching, releases, version bumping) and 'when' (explicit 'Use when...' clause listing five specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'commit', 'branches', 'releases', 'release notes', 'Git conventions', 'version bumping'. These cover common variations of how a developer would phrase requests about Git workflow. | 3 / 3 |
Distinctiveness Conflict Risk | Scoped to a specific monorepo ('rc-unified-crm-extension') and specific Git workflow concerns, making it clearly distinguishable from general coding skills or other project-specific 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-crafted skill that delivers project-specific Git workflow guidance concisely and actionably. The commit conventions with real repo examples, the clearly sequenced release process, and the CI/CD quick reference table are all excellent. The only minor weakness is that all content lives in a single file, though the total length is reasonable enough that this is a minor concern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what Git, npm workspaces, or CI/CD are. Every section delivers project-specific information Claude wouldn't already know — commit conventions from actual repo history, specific script paths, and workflow triggers. No padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable commands for the entire release process (npm run update, git tag, git push), specific file paths for connectors and configs, concrete commit message examples drawn from the actual repo, and exact test commands. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | The release process is clearly sequenced as numbered steps (update version → update release notes → commit → tag and push) with specific commands at each step. The branching flow is also clearly sequenced. The pre-push validation step (run tests locally) is explicitly called out before pushing, serving as a checkpoint. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's all inline in a single file. The CI/CD reference table and connector notes could potentially be split out for a cleaner overview. However, at ~100 lines total, the monolithic approach is borderline acceptable. No bundle files are provided to reference, which limits the score. | 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
- ringcentral/rc-unified-crm-extension
- Commit
f59d4a2
- 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.