Skip to content
cccskills
FreePublished on GitHubEnglish overview

terminal-recovery

Diagnose failed, timed-out, or incomplete terminal commands using command output and environment checks. The skill guides targeted retries, avoids duplicate long-running jobs, and verifies that the intended files, processes, or service state were produced.

OriginalShow the original description

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

odysseus-dev/odysseus
AI rating100/ 100See how to install

Good for

  • Diagnose a command failure from its error output
  • Investigate missing dependencies or incorrect paths
  • Check a long-running command after a timeout
  • Verify files or service state after recovery

Overview

What it does

The skill investigates terminal commands that fail, time out, or produce insufficient output, then works toward recovery. It reads the exit status, standard output, and error output. Minimal read-only checks examine the working directory, files, executables, permissions, and other relevant conditions. It classifies the cause, changes one related condition, and tests the diagnosis with a small command.

When it helps

Use it when a command behaves unexpectedly and you do not know what to fix. It also helps when a long-running task appears stuck, or when a success message leaves you unsure whether the intended file or service actually exists.

Example requests

  • “Investigate this error output, fix the cause, and check again.”
  • “Check whether the task that timed out is still running.”
  • “Verify that the files produced after recovery meet the requirements.”

Notes

The procedure avoids repeating a failed command without changes. It checks necessity before installing packages or changing global configuration. Long-running tasks are checked through their existing session identifiers to avoid duplicate launches. A successful exit code alone does not establish completion: the resulting files or operating state must also be checked.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodIt explicitly covers investigating and recovering from command failures, timeouts, and incomplete output.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
AGoodSteps specify output inspection, cause classification, condition changes, session checks, and artifact verification.
SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt requires read-only diagnostic checks, necessity checks before installation or global changes, and checks to avoid duplicate launches.
Easy setupDoes it need few tools or API keys, and are they documented?
AGoodIt assumes terminal execution and specifies no particular additional tools or API keys.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

When to Use

Use when a command fails, times out, produces incomplete output, or behaves differently from what the task requires.

Procedure

  1. Read the command, exit status, standard output, and standard error before choosing a response.
  2. Confirm the working directory, relevant files, executable availability, permissions, and environment assumptions with minimal read-only probes.
  3. Classify the failure as syntax, missing dependency, wrong path, permissions, resource pressure, timeout, service state, or task logic.
  4. Change one relevant condition and retry the narrowest command that can test the diagnosis.
  5. For a long-running command, use the returned session identifier to poll or provide input instead of launching duplicates.
  6. After recovery, run the original acceptance check and inspect the resulting files or service state.

Pitfalls

  • Do not rerun an unchanged failing command repeatedly.
  • Do not install packages or change global configuration before confirming they are missing and necessary.
  • Do not launch a second server or training job before checking for an existing process and port or device conflicts.
  • Do not treat partial output or a zero exit status as proof that the requested state was produced.

Verification

  • The diagnosed cause is supported by command output or environment state.
  • The corrected command exits as expected.
  • The requested artifact, process, or state passes an independent acceptance check.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

action-evidence-synthesis

FreeSummaryAI rating 100

Turn scattered messages, meeting notes, and documents into sourced action lists and status briefs. The skill reconciles updates, separates facts from tentative inferences, and highlights decisions, dependencies, risks, and unanswered questions.

  • Build a sourced action list from meeting notes
  • Combine messages and documents into a status brief
  • Assess feasibility using dependencies and blockers
odysseus-dev/odysseus94.2KUpdated Oct 21, 2026

artifact-completion

FreeSummaryAI rating 100

Create a complete first version of a requested file or other deliverable early, then refine it and check its format, required content, location, and usability before reporting the work as finished.

  • Creating a report with all required sections
  • Saving a deliverable in a specified location
  • Checking that a generated file opens correctly
odysseus-dev/odysseus94.2KUpdated Oct 21, 2026

developer-docs

FreeSummaryAI rating 100

Find official documentation for a library, framework, or API and apply it to the task at hand. Check the relevant version, distinguish documented facts from assumptions, and verify code changes with a focused test or concrete command.

  • Checking how an API or option works
  • Implementing behavior for a specific version
  • Applying official guidance to an existing project
odysseus-dev/odysseus94.2KUpdated Oct 21, 2026

multimodal-evidence

FreeSummaryAI rating 90

Extract and verify text, numbers, objects, and sequences from images, documents, and video. Record where each finding appears, check exact labels and values, and build answers whose supporting evidence can be traced back to the input.

  • Extracting and checking numbers in documents
  • Tracing video events to timestamps
  • Reading and verifying labels in images
odysseus-dev/odysseus94.2KUpdated Oct 21, 2026

odysseus

FreeSummaryAI rating 100

Use Codex to manage Odysseus todos, calendars, memory, and documents, and read or draft email. Through its permission-scoped API, the skill also supports reminders and launching, inspecting, or stopping Cookbook model servers.

  • Create a timed reminder as a todo
  • Check calendar events and add appointments
  • Read email and prepare an editable reply draft
odysseus-dev/odysseus94.2KUpdated Oct 21, 2026

odysseus

FreeSummaryAI rating 100

Use Claude Code to manage Odysseus tasks, email, calendar events, stored facts, and documents through a permission-scoped API. You can also start, inspect logs for, and stop Cookbook model servers using the access granted by your token.

  • Creating a task with a timed reminder
  • Reading email and preparing a reply draft
  • Saving calendar events, preferences, and documents
odysseus-dev/odysseus94.2KUpdated Oct 21, 2026

See all skills by odysseus-dev

Report a problem with this skill