release
Automated release workflow for oh-my-claudecode
63
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/release/SKILL.mdQuality
Discovery
22%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 description is too minimal to effectively guide skill selection. It names a domain (release workflow) and a specific project but fails to describe concrete actions or provide any trigger guidance. Claude would struggle to know when to select this skill over others without explicit 'Use when...' conditions.
Suggestions
Add specific actions the workflow performs, e.g., 'Bumps version numbers, generates changelogs, creates git tags, and publishes releases'
Include a 'Use when...' clause with trigger terms like 'release', 'publish', 'version bump', 'changelog', 'tag release', or 'deploy oh-my-claudecode'
Specify the scope more clearly - is this for npm publishing, GitHub releases, or both? Include relevant file types or commands involved
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Automated release workflow') without listing any concrete actions. It doesn't specify what the workflow does - no mention of versioning, changelog generation, tagging, publishing, or any specific release tasks. | 1 / 3 |
Completeness | Only partially answers 'what' (automated release workflow) and completely lacks any 'when' guidance. No 'Use when...' clause or trigger conditions are provided, making it unclear when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('release', 'workflow', 'oh-my-claudecode') but misses common variations users might say like 'publish', 'version bump', 'deploy', 'tag', or 'changelog'. The project name is specific but limits discoverability. | 2 / 3 |
Distinctiveness Conflict Risk | The specific project name 'oh-my-claudecode' provides some distinctiveness, but 'automated release workflow' is generic enough to potentially conflict with other release or deployment skills. Without explicit triggers, overlap risk exists. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
87%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 release skill that provides clear, actionable guidance for a multi-step release process. The version files reference table and executable commands are particularly strong. The main weakness is the lack of explicit error recovery steps, particularly around test failures or failed npm publish attempts.
Suggestions
Add explicit error recovery guidance after Step 2 (e.g., 'If tests fail: fix issues, re-run tests, do not proceed until all pass')
Consider adding rollback instructions if npm publish or GitHub release creation fails mid-process
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information. No unnecessary explanations of concepts Claude already knows (git, npm, semantic versioning basics). Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides fully executable commands (git tag, npm publish, gh release create) and specific file locations with exact field names. The version files reference table is particularly actionable with precise paths and patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but validation is limited. Step 2 requires tests to pass but there's no explicit feedback loop for what to do if tests fail. The verification checklist at the end is good but lacks explicit 'if verification fails' recovery steps. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections: usage, checklist, reference table, and notes. Content is appropriately sized for a single SKILL.md file (~80 lines) with no need for external references. The table format for version files is excellent for quick reference. | 3 / 3 |
Total | 11 / 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
- Yeachan-Heo/oh-my-claudecode
- Commit
48ffaac
- 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.