version-bumper
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill version-bumperExecute automatically handles semantic version updates across plugin.json and marketplace catalog when user mentions version bump, update version, or release. ensures version consistency in AI assistant-code-plugins repository. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
45%
Overall
Validation
Implementation
Activation
Validation
81%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md line count is 45 (<= 500) | Pass |
frontmatter_valid | YAML frontmatter is valid | Pass |
name_field | 'name' field is valid: 'version-bumper' | Pass |
description_field | 'description' field is valid (321 chars) | Pass |
description_voice | 'description' uses third person voice | Pass |
description_trigger_hint | Description includes an explicit trigger hint | Pass |
compatibility_field | 'compatibility' field not present (optional) | Pass |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
metadata_field | 'metadata' field not present (optional) | Pass |
license_field | 'license' field is present: MIT | Pass |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_present | SKILL.md body is present | Pass |
body_examples | Examples detected (code fence or 'Example' wording) | Pass |
body_output_format | Output/return/format terms detected | Pass |
body_steps | Step-by-step structure detected (ordered list) | Pass |
Total | 13 / 16 Passed |
Implementation
22%This skill is a generic template with placeholder content that provides no actual guidance on version bumping. Despite the description promising semantic version updates across specific files, the body contains no concrete instructions, code examples, or version-specific workflows. The Output section hints at what should happen but the Instructions section fails to explain how.
Suggestions
- Add concrete code or commands showing how to read current version from plugin.json, compute the new semantic version, and update the files
- Include a specific workflow with validation steps: read version → compute bump → update plugin.json → update marketplace.extended.json → regenerate marketplace.json → validate
- Provide at least one concrete example showing input (e.g., 'bump minor version') and expected file changes with before/after JSON snippets
- Replace generic instructions like 'Provide necessary context' with specific parameters needed (e.g., bump type: major/minor/patch, plugin path)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but filled with generic placeholder text that adds no value. Phrases like 'automated assistance for the described functionality' and 'Invoke this skill when the trigger conditions are met' are vague filler rather than actionable content. | 2 / 3 |
Actionability | The instructions are entirely abstract with no concrete code, commands, or specific examples. 'Provide necessary context and parameters' and 'Apply modifications as needed' give Claude no executable guidance on how to actually bump versions. | 1 / 3 |
Workflow Clarity | The 4-step workflow is generic boilerplate that could apply to any skill. There are no specific steps for version bumping, no validation checkpoints, and no guidance on how to update plugin.json or marketplace files. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is so sparse that there's nothing meaningful to disclose progressively. The structure exists but the content doesn't justify it. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
50%The description identifies a clear domain (semantic versioning for a specific repository) and includes some trigger terms, but suffers from placeholder language ('Use when appropriate context detected', 'Trigger with relevant phrases') that provides no actionable guidance. The specificity of actions is moderate, and the 'when' clause fails to give Claude meaningful selection criteria.
Suggestions
- Replace the vague 'Use when appropriate context detected' with explicit triggers like 'Use when user asks to bump version, prepare a release, update plugin.json version, or sync marketplace catalog versions'
- Add more specific actions such as 'increments major/minor/patch versions, updates plugin.json and marketplace catalog in sync, validates version consistency'
- Remove the meaningless phrase 'Trigger with relevant phrases based on skill purpose' and instead list concrete variations users might say like 'bump to v2.0', 'release new version', 'update semver'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (semantic version updates) and specific files (plugin.json, marketplace catalog), but the actions are limited to 'handles version updates' without detailing concrete steps like 'increment major/minor/patch', 'sync versions', or 'validate consistency'. | 2 / 3 |
Completeness | The 'what' is partially addressed (version updates across specific files), but the 'when' clause is weak - 'Use when appropriate context detected' and 'Trigger with relevant phrases based on skill purpose' are meaningless placeholders rather than explicit guidance. | 2 / 3 |
Trigger Term Quality | Includes some natural keywords ('version bump', 'update version', 'release') but the phrase 'Trigger with relevant phrases based on skill purpose' is vague filler that adds no value. Missing variations like 'bump version', 'new release', 'semver', or version number patterns. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of specific files (plugin.json, marketplace catalog) and repository (AI assistant-code-plugins) provides some distinctiveness, but generic terms like 'release' and 'update version' could overlap with other versioning or release management skills. | 2 / 3 |
Total | 8 / 12 Passed |
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.