bump-ark

Open or advance a Positron PR that bumps the Ark submodule to a given Ark PR (its head while open, its merge commit once merged) or to latest Ark main, with Positron e2e test tags. Use when the user runs /bump-ark with a PR number or "main" and optional @:tags.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/bump-ark/SKILL.md

Quality

Content

71%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.

A well-written, actionable skill body with clear workflow semantics and safety guardrails for a risky PR-bumping operation. The main weakness is progressive disclosure: it references bundled scripts that are not present in the bundle directories, leaving navigation and file structure underdeveloped.

Suggestions

Verify and ship the referenced bundle files (bump_ark.py, parse_description.py, bump_notes.py) under scripts/ or references/ so the in-body path references resolve; the bundle directories are currently empty/absent.

Add a short '## Files' or inline pointer listing the bundled scripts and their roles so the file structure is navigable one level deep rather than buried in prose.

Tighten the release-notes-scraping and body-composition paragraphs, which repeat implementation detail already implied by the script, to lift conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely earns its tokens (branch naming, author-guard semantics, body assembly), though the body-composition and release-notes-scraping paragraphs repeat implementation detail that could be tightened.	4 / 5
Actionability	Provides a concrete, executable invocation ('python3 .claude/skills/bump-ark/bump_ark.py <args>') with explicit flag semantics and exit-code behavior; minor gaps are the details delegated to the bundled script rather than shown inline.	4 / 5
Workflow Clarity	Clear sequencing with concrete validation/checkpoint behavior (re-running is safe, exit 3 on colleague-owned PR, relay-only on ownership conflict, dry-run preview) for a destructive-ish git/PR operation; just short of an explicit validate-fix-retry feedback loop.	4 / 5
Progressive Disclosure	Reasonably organized into sections, but there are no bundle files present (references/, scripts/, assets/ absent) despite the body referring to bundled artifacts (bump_ark.py, parse_description.py, bump_notes.py); the script is referenced by path with no navigational pointer, so structure is inline rather than split across files.	3 / 5
	Total	15 / 20 Passed

Description

85%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.

A strong, specific description that clearly states both the skill's purpose and its trigger conditions in third person. Minor room to broaden natural-language synonym coverage, but it avoids fluff and over-claims.

Suggestions

Consider adding a couple of natural-language synonyms a user might say (e.g. 'bump the Ark submodule', 'update Ark') alongside the '/bump-ark' command name to broaden trigger coverage.

The 'once merged' finalize behavior is core to the skill; a brief explicit nod to the re-run-finalizes lifecycle could sharpen the 'what' beyond the body.

Dimension	Reasoning	Score
Specificity	Names several concrete actions (open/advance a Positron PR, bump the Ark submodule to a given commit or latest main, add e2e test tags) with minor coverage gaps such as the finalize-on-merge behavior being only implied.	4 / 5
Completeness	Explicitly states both what the skill does ('Open or advance a Positron PR that bumps the Ark submodule...') and when to use it ('Use when the user runs /bump-ark with a PR number or "main" and optional @:tags').	5 / 5
Trigger Term Quality	Includes natural trigger terms like '/bump-ark', 'PR number', 'main', and '@:tags' that a user would actually say, though it leans on the command name rather than broad synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Ark/Positron submodule bumping via a specific /bump-ark command) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: posit-dev/positron
Path: .claude/skills/bump-ark/SKILL.md
Commit: 9bb0f27

Reviewed: about 21 hours 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.