CtrlK
BlogDocsLog inGet started
Tessl Logo

sys-configure

Configure Claude Octopus — redirects to /octo:setup interactive wizard

62

Quality

73%

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

Quality

Content

86%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 body is an exemplar of a redirect skill: short, honest about being an alias, with a fully executable action and a clearly signaled one-level-deep reference. Its only flaws are a paragraph of opaque internal-behavior description that could be trimmed and a mild tension between invoking the command versus reading the target file.

DimensionReasoningScore

Conciseness

The body is ~25 lean lines dominated by an unambiguous action block; the middle paragraph describing the setup wizard's internals ("separate, private resume receipt... strict configuration persistence and readback") is opaque over-explanation that a redirect skill does not need and could be trimmed. Mostly efficient with only minor over-explanation, matching anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

"**Action:** Run `/octo:setup`" plus the explicit path "${HOME}/.claude-octopus/plugin/commands/setup.md" are concrete, executable, copy-paste-ready instructions with a clear capability list. The single action is fully specified with no gaps.

5 / 5

Workflow Clarity

For a simple single-purpose redirect skill the action is unambiguous, but the body gives two parallel directives — "invoke the setup command directly" versus "Read .../setup.md and follow it" — leaving slight ambiguity about which path to take. No destructive or batch operations, so the validation cap does not apply; this sits just below the clean single-action case of 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no bundle files needed; the single external reference (${HOME}/.claude-octopus/plugin/commands/setup.md) is clearly signaled and exactly one level deep. Per the rubric's simple-skill exception, well-organized short content with no need for external references scores 5.

5 / 5

Total

18

/

20

Passed

Description

61%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 concise, honest, and distinct — it clearly states the redirect behavior and names the right product niche. Its main weakness is that all trigger/when guidance is delegated to a separate trigger field rather than the description itself, capping completeness, and it under-sells the concrete capabilities (provider auth, token optimization, onboarding) that the body enumerates.

Suggestions

Append an explicit when-clause to the description field itself, e.g. "Use when the user wants to configure Claude Octopus, set up providers, or add API keys" — the when-guidance currently lives only in the separate trigger field.

Enumerate the concrete capabilities in the description (provider installation and auth, RTK token optimization, work mode selection) instead of the generic "Configure" verb, mirroring the body's bullet list.

Keep the "Claude Octopus" qualifier in every trigger phrase to reduce overlap with generic configuration skills, since the bare aliases config/configure are highly generic.

DimensionReasoningScore

Specificity

Names the domain ("Configure Claude Octopus") and one concrete action ("redirects to /octo:setup interactive wizard"), but the actual capabilities (provider auth, token optimization, work-mode selection) are not enumerated. It exceeds score 2 (which requires only minimal/generic actions) but lacks the several specific actions needed for 4.

3 / 5

Completeness

The "what" is clear (redirect to the /octo:setup wizard), but the description field contains no "Use when..." clause or equivalent trigger guidance — that guidance lives only in the separate frontmatter trigger field. Per the rubric guideline, a missing explicit when-clause caps completeness at 3.

3 / 5

Trigger Term Quality

"configure", "setup", "octopus", and "wizard" are natural phrases a user would say when needing this skill. Missing a few common variations/synonyms (e.g., "providers", "API keys"), which appear only in the separate trigger field, so it falls short of the comprehensive synonym coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

"Claude Octopus" carves out a clear niche with distinct triggers and minimal conflict risk, but the bare "Configure" wording (matching the generic aliases config/configure) creates minor overlap risk with other configuration-related skills. Not 5 due to that residual overlap; well above the broad overlap of scores 1-3.

4 / 5

Total

14

/

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
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.