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 ./skills/octopus-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 core execution flow is genuinely strong — concrete commands, defensive git staging, explicit failure handling, and a good worked example. However, roughly half the file is promotional and redundant framing (benefits, comparison, best practices, summary) that inflates token cost without adding executable value, and the single-file structure offers no progressive disclosure.

Suggestions

Cut or collapse the 'Benefits of Quick Mode', 'Comparison: Quick Mode vs Full Workflow', 'Best Practices', and closing 'Summary' sections — they restate the 'When to Use' and 'Troubleshooting' content and would roughly halve the file.

Define $TASK_DESCRIPTION (or substitute the actual user request) in the summary-heredoc script so Step 5 is truly copy-paste executable.

Add a lightweight post-edit verification step (e.g. review `git diff --cached` before committing) to complete the feedback loop between making the change and the atomic commit.

DimensionReasoningScore

Conciseness

The body is noticeably verbose for a 'quick' skill: "Benefits of Quick Mode" (speed/cost/tracked/scope), the Quick-vs-Full comparison table, "Best Practices" DO/DON'T lists, and the closing "Summary" section largely restate the 'When to Use' lists or add marketing-style padding. Multiple full sections could be cut without losing executable guidance, matching anchor 2 ('several unnecessary explanations or padded sections') rather than 3.

2 / 5

Actionability

Steps 3-5 provide copy-paste-ready bash (literal-pathspec add/commit, state-manager.sh invocations, the summary heredoc) plus a complete worked example. Minor gaps keep it below 5: $TASK_DESCRIPTION is used in the heredoc but never defined, and `skills/blocks/codex-host-adapter.md` is referenced but not present in the bundle.

4 / 5

Workflow Clarity

A clear 5-step sequence (Understand → Change → Commit → Record → Summary) with real checkpoints: 'Inspect the existing index and working-tree diff before editing' and explicit commit-failure handling ('If staging or committing fails, stop the workflow... Preserve the edits for recovery'). It falls short of 5 because there is no post-change verification that the edit itself is correct before committing.

4 / 5

Progressive Disclosure

Section headers are good, but this is a ~370-line monolithic file with no bundle files; benefits, comparison table, troubleshooting, and directory-structure content are inlined where they could be trimmed or split out. The one external reference (`skills/blocks/codex-host-adapter.md`) sits in a host-adaptation note and does not exist in the bundle, matching anchor 3 ('some structure but could be better organized').

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 follows the what-plus-when pattern with an explicit "use for" clause, but it stays at a high level of abstraction. It never states what quick mode actually does (edit, commit, record state, summarize), which weakens specificity and makes trigger matching harder.

Suggestions

Enumerate 2-3 concrete actions in the description, e.g. 'Makes the edit, creates an atomic git commit, and records a summary' — this would lift specificity from naming the domain to listing real capabilities.

Add natural trigger synonyms users would say, such as 'simple fix', 'trivial change', 'one-off task', or 'typo fix', to improve trigger term coverage.

Make the 'when' clause more concrete by naming example tasks (typo corrections, config tweaks, small refactorings) instead of the generic 'small, self-contained requests'.

DimensionReasoningScore

Specificity

"Quick execution for ad-hoc tasks without full workflow overhead" names the domain but lists no concrete actions — the actual work (bug fixes, config changes, atomic commits, summaries) is absent. It matches anchor 2 ('Names the domain but actions are minimal or generic'), not 3, because no specific actions are enumerated.

2 / 5

Completeness

Both parts are present: what ("Quick execution for ad-hoc tasks without full workflow overhead") and when ("use for small, self-contained requests"). The 'when' clause is explicit but could be more specific with concrete trigger examples, matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Terms like "quick", "ad-hoc", "small", and "self-contained requests" are phrases users would naturally say, but common variations such as "simple fix", "trivial", or "one-off" are missing. This matches anchor 3 ('Some relevant keywords but missing common variations or synonyms') rather than 4's fuller coverage.

3 / 5

Distinctiveness Conflict Risk

The quick-vs-full-workflow framing carves out a niche among heavyweight workflow skills, but "Quick execution for ad-hoc tasks" is generic enough to overlap with any general task-execution or fix-it skill. This lands on anchor 3 ('Somewhat specific but could still overlap with similar skills').

3 / 5

Total

12

/

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

Path

skills/octopus-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.