CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a clear, well-sequenced workflow with validation and error handling, but it is not fully actionable (computed logic deferred to references) and its progressive disclosure is incomplete because several real bundle files are never referenced.

Suggestions

Add a short executable snippet or the precise jq/sed update command for editing the version field so the core action is copy-paste ready rather than deferred to a reference.

Either reference ARD.md, PRD.md, and errors.md from the Resources section or remove them from the bundle so the listed references match the actual structure.

Trim the Examples section, which restates steps already in Instructions, to reduce token overlap with no loss of clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient and uses concrete commands, but it re-explains basic mechanics already covered by the references and includes repeated parallel content (the Examples section restates steps the Instructions already list), so it could be tightened.

2 / 3

Actionability

It gives concrete commands like `jq -r '.version'` and `pnpm run sync-marketplace`, but the core version computation is left to a reference and the file edits are described rather than shown as executable snippets, leaving some guidance incomplete.

2 / 3

Workflow Clarity

The numbered Instructions lay out a clear sequence with an explicit verification step (step 7 confirms all three files match) plus an error-handling table, giving clear checkpoints and an error-recovery loop for the sync/verification operations.

3 / 3

Progressive Disclosure

References are real and one level deep with a Resources list, but several bundle files exist that the body never signals (ARD.md, PRD.md, errors.md are unreferenced) and the references/README still advertises generic placeholders, so structure is present but incompletely organized.

2 / 3

Total

9

/

12

Passed

Description

82%

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 is specific and well-targeted with strong, natural trigger terms and a clear niche, but its 'Use when...' clause is generic boilerplate rather than an explicit trigger statement, capping completeness.

Suggestions

Replace 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.' with a concrete 'Use when the user asks to bump, update, or release a plugin version, or mentions version changes in the plugin marketplace.'

Tighten the description to remove the redundant filler clause and keep the file lists and triggers that already earn their place.

DimensionReasoningScore

Specificity

Lists multiple concrete actions spanning 'semantic version updates across plugin.json and marketplace catalog' and 'ensures version consistency', naming specific files and a concrete outcome rather than vague language.

3 / 3

Completeness

It answers 'what' (semantic version updates, consistency) and includes trigger phrases, but the 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose' is generic boilerplate rather than an explicit, meaningful 'Use when...' clause, capping completeness at 2 per the missing-explicit-trigger guidance.

2 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say — 'version bump', 'update version', or 'release' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The 'AI assistant-code-plugins repository' niche plus version-bump-specific triggers make it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.