CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sys-configure

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

Quality

69%

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

67%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 short and delivers a clear, concrete redirect action with an appropriately minimal one-level reference to the real setup command. Its main weaknesses are the inlined resume-receipt paragraph that duplicates setup internals it explicitly says not to duplicate, and the dual directive (run the command vs read its source file) that blurs the single intended action.

Suggestions

Delete or compress the resume-receipt/readback paragraph — it describes setup-command internals that belong in commands/setup.md, not in this redirect, and the body itself warns against duplicating setup logic.

Pick one directive: either 'Run `/octo:setup`' or 'Read .../commands/setup.md and follow it', so the single action is unambiguous and workflow clarity can reach 5 for a simple skill.

Move the four-item configuration scope list (provider auth, RTK tokens, work mode, onboarding) next to the action line and cut the remaining prose, tightening the whole body to a lean redirect stub.

DimensionReasoningScore

Conciseness

The paragraph 'Setup uses a separate, private resume receipt... Remote sessions never open it automatically' (~6 lines) explains setup-command internals a redirect skill does not need, directly contradicting its own 'Do NOT duplicate setup logic here.' Anchor 3 — mostly efficient with some unnecessary explanation; not 4 because this block is the largest part of the body, more than a minor trim.

3 / 5

Actionability

Gives concrete, executable directives: 'Run `/octo:setup`' and a specific file path with env-var fallback. Anchor 4 — mostly executable with minor gaps; not 5 because two slightly different directives coexist ('invoke the setup command directly' vs 'Read .../commands/setup.md and follow it'), and not 3 since both are concrete rather than vague or pseudocode.

4 / 5

Workflow Clarity

As a single-action redirect skill the '**Action:** Run `/octo:setup`' line is unambiguous, satisfying the simple-skill exception in spirit. Anchor 4 rather than 5 because the action is stated two different ways (run the command vs read the file) and the receipt paragraph interrupts the flow; no destructive or batch operations, so the validation cap does not apply.

4 / 5

Progressive Disclosure

The body is under 50 lines with one clearly signaled, one-level-deep reference (commands/setup.md) — good structure. Anchor 4 rather than 5 because setup-behavior detail that belongs in the referenced file is inlined (the resume-receipt paragraph), despite the body's own instruction not to duplicate setup logic; not 3 since structure and reference signaling are otherwise clean and no bundle files are needed.

4 / 5

Total

15

/

20

Passed

Description

57%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 short and product-anchored with a clear 'what' (a redirect to the setup wizard) and minimal conflict risk, but it lacks any 'when to use' trigger guidance and only carries a couple of the natural trigger phrases that its own frontmatter trigger field enumerates. It reads as an internal alias label rather than a self-contained triggering description.

Suggestions

Add an explicit 'when' clause to the description, e.g. 'Use when the user wants to configure Claude Octopus, set up providers or API keys, or run octopus onboarding.'

Fold the natural trigger phrases already listed in the frontmatter trigger field ('configure providers', 'set up API keys', 'setup octopus') into the description itself so model invocation can rely on the description alone.

Briefly state the scope of configuration covered (provider installation/auth, token optimization, work mode selection) so the 'what' is more than a single redirect action.

DimensionReasoningScore

Specificity

Names the domain ('Configure Claude Octopus') and one concrete action ('redirects to /octo:setup interactive wizard'), but does not enumerate what configuration covers (providers, API keys, work modes). Matches anchor 3 — 1-2 concrete actions, not comprehensive; not 4 because no list of specific actions is present.

3 / 5

Completeness

The 'what' is clear (redirect to the setup wizard), but there is no 'Use when...' clause or equivalent trigger guidance in the description, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

'Configure' and 'setup' are natural phrases a user would say, but common variations the skill's own trigger field lists ('configure providers', 'set up API keys', 'octopus configuration') are absent from the description. Anchor 3 — some relevant keywords, missing common variations; not 4 because keyword coverage is thin for a two-line description.

3 / 5

Distinctiveness Conflict Risk

'Claude Octopus' is a named product, giving a clear niche with distinct triggers; 'configure' is generic but anchored to the product name, so conflict risk with other skills is minimal. Matches anchor 5; not 4 because no realistic overlap with other skills exists.

5 / 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

Path

.claude/skills/sys-configure/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.