CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bump

Bump a pinned dependency version. Use harness.md to bump an agent harness (codex, claude-code, pi, hermes-agent, prime-agent, mini-swe-agent, ...).

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bump/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%Weight 40%Scale 1-5

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

The body is maximally concise and correctly uses a pointer pattern for progressive disclosure, but the pointer targets a file that is missing from the bundle, leaving the skill with no executable content. The general pinned-dependency bump case advertised in the description is entirely unaddressed.

Suggestions

Add harness.md to the bundle (e.g. in references/) or inline its bump steps in SKILL.md — the current link points to a nonexistent file.

Cover the general pinned-dependency bump workflow (which manifests to edit, how to pick the new version, how to verify) in the body or a reference file, since the description promises it but the body only handles agent harnesses.

If harness.md covers multiple harness-specific procedures, list them as separately labeled links so the structure is navigable at a glance.

DimensionReasoningScore

Conciseness

The body is two lean lines with zero padding, no explanation of concepts Claude already knows, and every token serves navigation — "To bump an agent harness version, follow [harness.md](harness.md)" assumes Claude's competence completely.

5 / 5

Actionability

The only guidance is a pointer to harness.md, and that file does not exist anywhere in the bundle (no references/, scripts/, or assets/ directories), so the instruction cannot actually be executed; the general pinned-dependency bump case stated in the description has no guidance at all in the body.

2 / 5

Workflow Clarity

While this is a simple single-action skill that could score high if self-contained, the single action ("follow harness.md") is broken because the target file is missing, and no workflow exists for the non-harness pinned-dependency case the description promises.

2 / 5

Progressive Disclosure

The reference is well-signaled and one level deep in form, but scored against the actual bundle structure the referenced path is a dangling pointer — harness.md is absent, so navigation leads nowhere and the skill contains no instructional content behind the link.

2 / 5

Total

11

/

20

Passed

Description

61%Weight 40%Scale 1-5

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 states a clear, concrete purpose with distinctive named harness targets, but it lacks an explicit "Use when..." trigger clause and natural synonyms like "upgrade". It is functional but not fully discoverable or complete.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to bump or upgrade a pinned dependency version, or to update an agent harness (codex, claude-code, pi, ...)."

Include natural synonyms such as "upgrade" or "update the pinned version" alongside "bump" for better trigger coverage.

Mention the concrete actions involved (which manifests/files get edited, e.g. package.json, pyproject.toml, requirements.txt) to lift specificity.

DimensionReasoningScore

Specificity

"Bump a pinned dependency version" names the domain and a single concrete action, and the enumerated harness names (codex, claude-code, pi, hermes-agent, prime-agent, mini-swe-agent) add specificity, but coverage is not comprehensive — no mention of which manifests or files are involved or other bump scenarios.

3 / 5

Completeness

There is a clear "what" ("Bump a pinned dependency version") but no "Use when..." clause or equivalent explicit trigger guidance — "Use harness.md to bump an agent harness" describes usage of a file, not when to invoke the skill, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"bump" and "pinned dependency" plus the concrete harness names (codex, claude-code, etc.) are natural terms users would say, but common synonyms like "upgrade" or "update the pinned version" are missing.

4 / 5

Distinctiveness Conflict Risk

The enumerated harness names give it distinct triggers and a clear niche, but "Bump a pinned dependency version" broadly overlaps with generic dependency-update skills, so minor conflict risk remains.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

PrimeIntellect-ai/verifiers

Path

skills/bump/SKILL.md

Revision

eaab317

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill