CtrlK
BlogDocsLog inGet started
Tessl Logo

claim-issue

Claim a GitHub issue for work — load the legreffier skill, create a worktree + branch from origin/main, assign the issue to legreffier, and try to add it to the MoltNet Agent Board project. Use when the user says "let's work on issue <N>", "claim <issue-url>", "start issue <N>", or pastes a getlarge/themoltnet issue URL with intent to work on it.

76

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 content is highly actionable with executable commands and a well-sequenced, validation-checked workflow including strong failure-mode handling. The main weakness is a duplicated dependency-install step and minor redundancy that could be tightened for better token efficiency.

Suggestions

Merge the pnpm install guidance: step 3 and step 4 both describe running `pnpm install` in the new worktree — collapse into a single step to remove the duplication.

Trim explanatory asides that restate intent (e.g. "so the branch is immediately runnable") where the command already makes the purpose clear.

Consolidate the legreffier-gh.md / .claude/rules references into a single clearly-signaled pointer rather than mentioning the path across multiple steps.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but `pnpm install` is duplicated across step 3 and step 4 and a few explanatory asides could be trimmed; it sits noticeably above the mostly-efficient anchor.

4 / 5

Actionability

Provides copy-paste-ready `gh`/`git` commands with exact flags, concrete branch-slug derivation rules, and specific recovery commands (e.g. `git worktree add "$WORKTREE" issue-<N>-<slug>`) covering the common cases.

5 / 5

Workflow Clarity

A clear 7-step sequence split into read-only and mutation phases, with explicit checkpoints (closed-state check, single mutation-phase confirmation) and a "Failure modes to surface, not hide" feedback section with recovery loops for a batch/mutation operation.

5 / 5

Progressive Disclosure

Self-contained body with clear section headers (Inputs, Steps, Failure modes) and no nested references, but the duplicated pnpm install across steps 3-4 and reliance on external non-bundle paths (legreffier-gh.md) leave minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

100%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 is third-person, concise, and comprehensive — it enumerates concrete actions, provides natural user trigger phrases, and explicitly scopes the skill to the MoltNet repo. It satisfies both the what and when requirements cleanly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Claim a GitHub issue", "create a worktree + branch from origin/main", "assign the issue to legreffier", and "add it to the MoltNet Agent Board project" — giving comprehensive coverage of the workflow.

5 / 5

Completeness

Clearly states what the skill does and follows with an explicit "Use when the user says..." clause listing concrete trigger phrases, satisfying both what and when.

5 / 5

Trigger Term Quality

Includes natural phrasings a user would actually say ("let's work on issue <N>", "claim <issue-url>", "start issue <N>") plus a concrete getlarge/themoltnet URL pattern with synonyms.

5 / 5

Distinctiveness Conflict Risk

Scoped to MoltNet issue claiming with distinct triggers tied to a specific repo, giving a clear niche with minimal overlap risk against other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
getlarge/themoltnet
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.