version-bumper

Execute 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.

Quality

60%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/examples/jeremy-plugin-tool/skills/version-bumper/SKILL.md

Quality

Discovery

50%

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 identifies a specific domain (semantic versioning in a plugin repository) and includes some useful trigger terms, but is significantly weakened by circular, filler phrases like 'Use when appropriate context detected' and 'Trigger with relevant phrases based on skill purpose' which provide zero actionable guidance. The description would benefit from removing the filler and replacing it with concrete trigger scenarios and more specific action descriptions.

Suggestions

Replace the vague 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.' with explicit trigger guidance, e.g., 'Use when the user asks to bump a version, prepare a release, or update plugin.json/marketplace catalog versions in the AI assistant-code-plugins repository.'

Add more specific trigger term variations such as 'semver', 'patch bump', 'minor version', 'major version', 'version number', 'new release' to improve matching coverage.

List more concrete actions beyond 'handles semantic version updates' — e.g., 'increments major/minor/patch version numbers, synchronizes version strings across plugin.json and the marketplace catalog file, validates version consistency.'

Dimension	Reasoning	Score
Specificity	Names the domain (semantic version updates) and mentions specific files (plugin.json, marketplace catalog), but the actions are limited to 'handles semantic version updates' without listing concrete steps like 'bumps major/minor/patch version', 'updates changelog', etc.	2 / 3
Completeness	The 'what' is partially addressed (handles semantic version updates across specific files), but the 'when' clauses are weak and circular — 'Use when appropriate context detected' and 'Trigger with relevant phrases based on skill purpose' are meaningless filler that don't provide explicit trigger guidance.	2 / 3
Trigger Term Quality	Includes some natural trigger terms like 'version bump', 'update version', and 'release', but the final sentence 'Trigger with relevant phrases based on skill purpose' is vague filler that adds no real trigger terms. Missing variations like 'semver', 'patch version', 'minor bump', 'major release'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'plugin.json', 'marketplace catalog', and 'AI assistant-code-plugins repository' provides some specificity to a particular repo/context, but the generic phrasing around triggers and the broad term 'release' could overlap with other release or versioning skills.	2 / 3
	Total	8 / 12 Passed

Implementation

70%

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-structured skill with clear workflow sequencing, good progressive disclosure to reference files, and appropriate error handling. Its main weakness is the lack of executable, copy-paste-ready code examples — the instructions describe what to do in prose but don't provide concrete command snippets inline. The content could also be tightened by removing some explanatory text that Claude doesn't need.

Suggestions

Add inline executable command examples for key steps (e.g., the jq command to update version in plugin.json: `jq '.version = "1.2.4"' plugin.json > tmp && mv tmp plugin.json`)

Replace the narrative example descriptions with concrete command sequences showing actual inputs and outputs

Trim the prerequisites section — Claude can infer tool requirements from the instructions themselves

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some unnecessary elements. The error handling table, while useful, adds bulk. The prerequisites section explains things Claude could infer. The examples section describes processes narratively rather than showing concrete commands, adding verbosity without proportional value.	2 / 3
Actionability	The workflow steps are specific and reference concrete tools (jq, pnpm), but no executable code blocks or copy-paste-ready commands are provided inline. Key operations like parsing semver components and computing new versions are deferred to reference files rather than shown directly. The examples describe processes in prose rather than showing actual commands.	2 / 3
Workflow Clarity	The 8-step workflow is clearly sequenced with an explicit validation checkpoint at step 7 (verify version consistency across all three files). The error handling table provides a feedback loop for common failure modes. The process flows logically from reading current version through bumping, syncing, and verifying.	3 / 3
Progressive Disclosure	The skill provides a clear overview with well-signaled one-level-deep references to specific resource files (version-bump-process.md, update-locations.md, release-workflow.md, examples.md). The main SKILL.md contains enough context to understand the workflow while deferring detailed algorithms and additional examples to reference files. Navigation is straightforward.	3 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3a2d27d

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.