release-workflow
Use when preparing or executing a release for the glean-claude-plugins marketplace. Triggers on "release", "bump version", "publish", "npm run release", "new version", or when the user wants to cut a new plugin version.
67
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
62%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger terms and distinctiveness, clearly scoping itself to the glean-claude-plugins release process with excellent keyword coverage. However, it is notably weak on specificity — it fails to describe what concrete actions the skill performs during a release (e.g., version bumping, changelog generation, npm publishing, tagging). The imbalance between strong 'when' guidance and weak 'what' guidance limits its overall quality.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Bumps package version, updates changelog, builds artifacts, publishes to npm, and creates git tags for the glean-claude-plugins marketplace.'
Restructure to lead with a clear 'what it does' statement listing 3-5 specific release steps before the 'Use when' trigger clause.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks concrete actions describing what the skill actually does. It mentions 'preparing or executing a release' but doesn't specify what steps are involved (e.g., bumping version numbers, building packages, publishing to npm, updating changelogs). The actions are vague and abstract. | 1 / 3 |
Completeness | The 'when' is explicitly and thoroughly addressed with a 'Use when' clause and multiple trigger scenarios. However, the 'what' is very weak — it only says 'preparing or executing a release' without describing the concrete steps or capabilities involved in the release process. | 2 / 3 |
Trigger Term Quality | Excellent trigger term coverage including natural phrases users would say: 'release', 'bump version', 'publish', 'npm run release', 'new version', and 'cut a new plugin version'. These are concrete, varied, and match real user language. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific project name 'glean-claude-plugins marketplace' and domain-specific triggers like 'npm run release' and 'cut a new plugin version'. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 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 an excellent release workflow skill. It is concise, fully actionable with executable commands at every step, has clear sequencing with validation checkpoints before and after the release, and is well-organized for its scope. The warning about adding new plugins to the bumper configuration is a valuable safety detail that prevents silent version drift.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section serves a purpose. No unnecessary explanations of what release-it is or how npm works. The inline comments on Step 4 efficiently describe what the command does without over-explaining. The warning about adding new plugins is concise and critical. | 3 / 3 |
Actionability | Every step has a concrete, copy-paste-ready command. Expected outputs are specified (e.g., 'nothing to commit, working tree clean', 'All 10 plugin versions should show the new version number'). The plugin list and the warning about `.release-it.json` configuration are specific and actionable. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced with explicit 'do not skip steps' instruction. Validation checkpoints are present at Steps 1-3 (pre-flight) and Step 5 (post-release verification). There are clear fix-then-proceed feedback loops ('Fix any errors before proceeding', 'fix them before proceeding and commit the fix separately'). | 3 / 3 |
Progressive Disclosure | For a single-purpose procedural skill under 80 lines, the content is well-organized into logical sections (Pre-flight, Release, Post-release, Plugin list). No external references are needed as the workflow is self-contained and appropriately scoped. | 3 / 3 |
Total | 12 / 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
- gleanwork/claude-plugins
- Commit
39a5c99
- 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.