CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

octopus-quick

Quick execution for ad-hoc tasks without full workflow overhead — use for small, self-contained requests

Quality

63%

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-quick/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 skill body delivers genuinely executable guidance with a clear step sequence, strong git hygiene (literal-pathspec adds, commit --only, explicit failure handling), and a concrete worked example. Its main weakness is token efficiency — roughly half the file restates the same scope, escalation, and best-practice points across redundant sections — and it keeps everything in one long file rather than splitting peripheral detail out.

Suggestions

Remove or merge the redundant sections — "Benefits of Quick Mode", the comparison table, "Best Practices", "Troubleshooting", and the closing "Summary" — since they restate the "When to Use" and escalation content, cutting the file roughly in half.

Define $TASK_DESCRIPTION (or substitute the actual task text) in the summary-generation script so the heredoc is fully copy-paste ready.

Move the complete worked example and the quick-vs-full-workflow comparison into a reference file (or trim them to a few lines) so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: "Benefits of Quick Mode", the "Comparison: Quick Mode vs Full Workflow" table, "Best Practices" DO/DON'Ts, "Troubleshooting", and the closing "Summary" all restate content already covered in "When to Use" and the escalation section — several padded sections that could be cut roughly in half. It avoids anchor 1 because it does not explain concepts Claude already knows; the padding is redundancy, not tuition.

2 / 5

Actionability

Mostly executable guidance: copy-paste-ready commands for atomic commits ("git --literal-pathspecs add -- \"${QUICK_FILES[@]}\""), state recording ("state-manager.sh write_decision \"quick\" ..."), and a heredoc summary script, plus a fully worked typo-fix example. Minor gaps keep it from anchor 5 — e.g., $TASK_DESCRIPTION is used in the summary script but never defined, and the co-author attribution is hardcoded to a specific model version.

4 / 5

Workflow Clarity

A clear 5-step sequence (understand → change → commit → record → summarize) with an explicit failure checkpoint ("If staging or committing fails, stop the workflow... Preserve the edits for recovery") and defined escalation indicators. It falls short of anchor 5 because error handling is stop-and-escalate rather than a fix-and-retry feedback loop, and there is no verification of the committed result.

4 / 5

Progressive Disclosure

The file is well-sectioned with clear headers, but it is a ~390-line monolith with no external references or bundle files; content such as the complete worked example, the comparison table, and the troubleshooting section is inlined where it could be trimmed or split out. It is not anchor 2 because the structure itself is good and nothing is buried, but it does not reach anchor 4 given the length and inlined peripheral content.

3 / 5

Total

13

/

20

Passed

Description

53%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 correctly answers both what the skill does and when to use it, with an explicit trigger clause and relevant keywords. However, it stays at a high level of abstraction — no concrete action types or natural trigger phrases like "quick fix" — limiting its specificity and distinctiveness.

Suggestions

List 2-3 concrete action types in the description (e.g., "fix typos, update config values, rename symbols, bump dependency versions") to raise specificity.

Add natural trigger phrases users would actually say, such as "quick fix", "one-off task", or "minor change", to improve trigger term coverage.

Sharpen the when-clause with explicit user-language triggers (e.g., "use when the user says 'quick fix' or asks for a fast, one-off change") to reduce overlap with general coding skills.

DimensionReasoningScore

Specificity

The description names the domain ("Quick execution for ad-hoc tasks without full workflow overhead") but lists no concrete actions — phrases like "quick execution" are generic, unlike anchor-3 examples that name 1-2 specific operations. It does not reach anchor 1 since it is not pure abstraction, but it never states what is actually done.

2 / 5

Completeness

Both parts are present: the "what" ("Quick execution for ad-hoc tasks without full workflow overhead") and an explicit "when" clause ("use for small, self-contained requests"). It falls short of anchor 5 because the "when" lacks concrete trigger phrases a user would actually utter.

4 / 5

Trigger Term Quality

It includes some relevant natural keywords ("ad-hoc tasks", "small, self-contained requests", "quick") but misses common variations and synonyms users would say, such as "quick fix", "one-off task", or "minor change". Not anchor 4 because the coverage of natural phrasing has clear gaps.

3 / 5

Distinctiveness Conflict Risk

The description is scoped to a fast-track execution mode rather than a generic task domain, but "small, self-contained requests" is broad enough to overlap with general coding or fix-it skills. It is somewhat specific yet could still collide with similar workflow skills.

3 / 5

Total

12

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-quick/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.