CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-issues

Track project blockers, bugs, and gaps across sessions — use when issues pile up or need triage

Quality

72%

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 ./.claude/skills/skill-issues/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 highly actionable, well-sequenced skill body whose subcommand flows leave little ambiguity about what to do. Its costs are redundancy (several sections restate others) and a monolithic structure that inlines scripts and reference material that should live in bundle files.

Suggestions

Cut the redundant "Quick Reference", "Common Patterns", and "The Bottom Line" sections, which restate the Subcommands and When to Use content, and drop the duplicate severity table (it is already encoded in the AskUserQuestion options).

Move the ID-generation bash script into a scripts/ file (e.g., scripts/next-issue-id.sh) and the severity definitions, ISSUES.md template, and best-practice examples into references/ files, keeping SKILL.md as a concise overview with one-level-deep, clearly signaled references.

Add a post-write verification step after modifying ISSUES.md (e.g., re-read the file and confirm the new/moved issue ID is present and no existing rows were lost) to close the validation gap on the skill's one destructive operation, and fix the `sed -i ''` command so it works on GNU sed as well as macOS.

DimensionReasoningScore

Conciseness

The core subcommand flows, ID algorithm, and file-preservation patterns earn their tokens, but several sections are pure padding: "Quick Reference" restates the Subcommands section, "Common Patterns" restates existing flows, the severity table duplicates the AskUserQuestion options, and "The Bottom Line" adds nothing. This is 'mostly efficient but could be tightened' rather than 'noticeably verbose' since no space is spent explaining concepts Claude already knows.

3 / 5

Actionability

The body provides copy-paste-ready bash for ID generation, initialization, and existence checks, plus exact AskUserQuestion payloads and output templates for every subcommand. Minor gaps keep it from a 5: `sed -i ''` is macOS-only and would fail on GNU sed, the resolve flow's row-move steps are described but not scripted, and the template copy depends on an unverified external plugin path.

4 / 5

Workflow Clarity

Each subcommand has a numbered, sequenced flow with explicit validation checkpoints (existence check with error message before resolve, structured severity/category prompts before add, not-found handling in show). Not a 5 because there is no post-write verification that ISSUES.md was modified correctly — the one risky (destructive-to-file) operation lacks a validate-after-write feedback loop.

4 / 5

Progressive Disclosure

Section headers are clear and consistent, but the skill is a 490-line monolith with no bundle files at all: the 20-line ID-generation script belongs in scripts/, and the severity definitions, best practices, and ISSUES.md template belong in references/. This matches 'some structure but content that should be separate is inline'.

3 / 5

Total

14

/

20

Passed

Description

70%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 solid description that answers both what and when in third-person voice with reasonably natural trigger phrases. Its main weaknesses are thin action coverage (only 'track' is named despite four subcommands) and a when-clause that captures only the triage/review use case.

DimensionReasoningScore

Specificity

"Track project blockers, bugs, and gaps across sessions" names the domain and one concrete action (track), but does not enumerate the concrete operations the skill actually performs (list, add, resolve, show). It matches 'names domain and 1-2 concrete actions, but not comprehensive' rather than 'lists several specific actions'.

3 / 5

Completeness

Both parts are explicitly present: what ("Track project blockers, bugs, and gaps across sessions") and when ("use when issues pile up or need triage"). It falls short of a 5 because the when-clause covers only pile-up/triage situations, not the add/resolve/show intents the skill supports, so the trigger guidance could be more specific.

4 / 5

Trigger Term Quality

Natural phrases like "issues pile up", "need triage", "blockers", "bugs", and "gaps" are phrases users would actually say, giving good keyword coverage. Not a 5 because common variations such as "problem", "defect", or "track this for later" are absent.

4 / 5

Distinctiveness Conflict Risk

"Across sessions" carves out a clear niche (persistent local issue tracking) distinct from GitHub issues or git workflows, with only minor overlap risk against closely related bug-tracking skills. It lacks the crisp disambiguation (e.g., 'not GitHub issues') that would earn a 5.

4 / 5

Total

15

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (512 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-issues/SKILL.md

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.