CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-intake

Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted

66

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-intake/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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-structured instruction skill with a clear sequenced workflow, explicit validation/checkpoint rules, and concrete commands. The main weakness is a dangling script reference and a few trimmable rationale sentences.

DimensionReasoningScore

Conciseness

The body is lean and does not re-explain concepts Claude already knows; a few short rationale sentences ('An unverified bug report is a hypothesis...') could be trimmed but most tokens earn their place, fitting anchor 4 rather than the fully stripped anchor 5.

4 / 5

Actionability

Provides concrete executable commands (gh issue list, bd ready, gh issue edit --add-label) and one complete bash snippet for the comment gate, with specific state definitions; it is mostly executable with minor gaps around the categorise/verify steps, matching anchor 4.

4 / 5

Workflow Clarity

A clear five-step sequence (Categorise, Verify, Assign state, Write brief, Record) is paired with an explicit Verify step, a Stop/Checkpoint Rules section, and a final Verification checklist, satisfying anchor 5's explicit validation and feedback loops for destructive/batch moves like closing.

5 / 5

Progressive Disclosure

A single, well-sectioned file with clear headers and one-level cross-references to sibling skills; the inlined reference to scripts/safe-gh-comment.sh is a dangling path (no bundle dir exists), a minor organization gap that keeps it at anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

78%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 tight, third-person description that cleanly answers both what and when with concrete trigger phrases. It is slightly light on enumerating multiple distinct actions and has minor overlap with adjacent issue-management skills.

DimensionReasoningScore

Specificity

Names the domain ('incoming issues and pull requests', 'triage states') and one composite action ('Move ... through triage states until each is actionable or closed'), but does not enumerate several distinct concrete actions; this matches anchor 3 rather than 4, which requires multiple specific actions.

3 / 5

Completeness

It explicitly states what the skill does ('Move ... through triage states until each is actionable or closed') and gives a concrete 'use when' clause with trigger phrases ('use when the queue has piled up or a report arrives unsorted'), matching anchor 5; it is not the 4 anchor because 'when' is concrete rather than only weakly specified.

5 / 5

Trigger Term Quality

Natural trigger terms 'issues', 'pull requests', 'queue has piled up', and 'report arrives unsorted' cover what a user would actually say; a few common synonyms (e.g. 'tickets', 'inbox') are missing, so it sits at anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The triage/intake niche is distinct from review or planning skills, but it overlaps with general issue-management workflows, so it is mostly distinct (anchor 4) rather than minimal-conflict (anchor 5).

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nyldn/claude-octopus
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.