CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

terminal-recovery

Recover from failed terminal commands using evidence-driven diagnosis and bounded retries

Quality

77%

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 ./resources/skills/agent/terminal-recovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a lean, well-structured, instruction-only skill with a clear sequenced workflow, explicit verification checkpoints, and valuable non-obvious pitfalls. Its only gap is the absence of concrete example commands, which keeps actionability at 4 rather than 5.

Suggestions

Add one or two concrete example read-only probes (e.g., "which <tool>", "ls -l <path>", checking exit code with "echo $?") to close the minor actionability gap.

DimensionReasoningScore

Conciseness

The ~27-line body is entirely directive — "Read the command, exit status, standard output, and standard error", "Do not rerun an unchanged failing command repeatedly" — with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching anchor 5.

5 / 5

Actionability

Guidance is concrete and executable: "Classify the failure as syntax, missing dependency, wrong path, permissions, resource pressure, timeout, service state, or task logic" and "use the returned session identifier to poll or provide input" give specific, followable directives. It falls short of anchor 5 only because no concrete example commands or common-case illustrations are included (e.g., example read-only probes), leaving minor gaps — anchor 4's profile.

4 / 5

Workflow Clarity

A clearly sequenced 6-step procedure (gather evidence → probe environment → classify → change one condition and retry → manage long-running sessions → verify) with a dedicated "## Verification" section defining explicit acceptance checks ("The corrected command exits as expected", "passes an independent acceptance check"). Step 4 embodies an explicit feedback loop (diagnose → change one condition → retest), and the Pitfalls section guards against blind reruns — matching anchor 5. This is not a destructive/batch operation, so no cap applies.

5 / 5

Progressive Disclosure

The body is under 50 lines with four well-organized sections (When to Use, Procedure, Pitfalls, Verification), no bundle files, and no content that needs splitting into references. Per the rubric's simple-skill guideline, this earns anchor 5 on well-organized sections alone.

5 / 5

Total

19

/

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 states a clear what with a recognizable niche, but lacks any explicit 'Use when...' trigger clause and misses natural trigger synonyms (error, exit code, timeout, fix). It sits at the midpoint: serviceable, but not competitive for reliable triggering.

Suggestions

Add an explicit trigger clause, e.g. "Use when a command fails, returns a non-zero exit code, times out, or produces unexpected or incomplete output."

Include natural user phrasings/synonyms such as "command failed", "error", "exit code", "timeout", or "fix a failing command" to improve trigger-term coverage.

Name concrete actions in the description (e.g., "read exit status and stderr, classify the failure, retry the narrowest command") to lift specificity toward anchor 4.

DimensionReasoningScore

Specificity

"Recover from failed terminal commands using evidence-driven diagnosis and bounded retries" names the domain (failed terminal commands) and 1-2 approach-level actions ("diagnosis", "retries"), but these are methodological rather than several distinct concrete capabilities like the anchor-4 example ("Extracts text from PDF files, fills forms, converts pages to images"). It is above anchor 2 because it goes beyond naming the domain — diagnosis and bounded retries are stated actions.

3 / 5

Completeness

The "what" is clear (recover failed terminal commands via evidence-driven diagnosis and bounded retries), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied by the word "failed". Per judging guidelines, a missing 'Use when...' clause caps completeness at 3, matching anchor 3 ("clear 'what' but 'when' is missing or only weakly implied").

3 / 5

Trigger Term Quality

Natural terms present: "failed", "terminal", "commands", "recover". Missing common variations and synonyms users would say: "error", "command failed", "exit code", "fix", "debug", "timeout". This matches anchor 3 ("Some relevant keywords but missing common variations or synonyms") rather than anchor 4, which expects good keyword coverage across multiple distinct trigger phrases.

3 / 5

Distinctiveness Conflict Risk

"failed terminal commands" carves out a concrete niche (terminal command failure recovery) that is mostly distinct, with only minor overlap risk against general debugging/troubleshooting skills — matching anchor 4. Not anchor 5 because it lacks the explicit, distinct trigger phrases the anchor-5 example carries ("Use when working with PDF files or when the user mentions PDFs").

4 / 5

Total

13

/

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

odysseus-dev/odysseus

Path

resources/skills/agent/terminal-recovery/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.