Agent skill

Oops

by poteto in poteto/noodle

Infrastructure fix for broken builds, failed tests, stale state, and environment drift.

MITAuto-check passedTesting & QA

Install Oops

skills CLI
$ npx skills add poteto/noodle --skill oops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install poteto/noodle oops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/oops .claude/skills/oops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
oops
GitHub stars
437
Token cost
~481 tokens
SKILL.md length
175 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

Infrastructure fix for broken builds, failed tests, stale state, and environment drift.

  • Works in 5 steps: Reproduce → Diagnose → Fix → …
  • Environment drifts
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Failing and flaky tests

What it does

Oops is an agent skill from poteto/noodle. Infrastructure fix for broken builds, failed tests, stale state, and environment drift. Covers both user-project and Noodle-internal failures. Triggers when builds break, tests fail, state is stale, or environment drifts. Use on 'oops', 'fix the build', 'tests are failing', 'something broke', 'broken build'.

Its SKILL.md is about 480 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Failing and flaky tests. The repository describes itself as: Orchestrate agents using skills. The licence is MIT.

When your agent uses it

  • Environment drifts
  • Tasks that involve Failing and flaky tests

Example prompts

  • “fix the build”
  • “tests are failing”
  • “something broke”
  • “/oops”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Reproduce
  2. Diagnose
  3. Fix
  4. Verify
  5. Commit

What it can do on your machine

Read from SKILL.md and the folder at commit 82d2921. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Oops loads about 481 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 175 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
When it runs · the whole SKILL.md, loaded when a task matches
~481

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from poteto/noodle at commit 82d2921, republished under its MIT licence (© poteto). 175 words, ~481 tokens.

Download SKILL.mdSave it as .claude/skills/oops/SKILL.md (or your agent's skills folder).
name
oops
description
Infrastructure fix for broken builds, failed tests, stale state, and environment drift. Covers both user-project and Noodle-internal failures. Triggers when builds break, tests fail, state is stale, or environment drifts. Use on 'oops', 'fix the build', 'tests are failing', 'something broke', 'broken build'.
schedule
When infrastructure failures are detected (build breaks, test failures, stale Noodle state)

Oops

Fix infrastructure failures. Applies to both user-project code and Noodle-internal state.

Fix flow

Reproduce -> Diagnose -> Fix -> Verify -> Commit

1. Reproduce

Run the failing command. Capture exact error output. If intermittent, run multiple times to confirm.

2. Diagnose

Suspect state before code. Check in this order:

  1. Noodle state — .noodle/ files, queue consistency, config validity
  2. Environment — Go version, missing deps, stale caches, tmux session health
  3. Config — .noodle.toml (project root), .agents/skills/ structure, brain/ integrity
  4. Persistent files — lock files, temp files, incomplete writes
  5. Code — only after ruling out state and environment
Principles
  • [[fix-root-causes]]
  • [[prove-it-works]]

Noodle-internal checklist:

  • .noodle/ state files: corrupt, stale, or inconsistent?
  • Queue state: orphaned tasks, stuck sessions?
  • Config: valid TOML, referenced paths exist?
  • tmux sessions: zombie processes, detached sessions?
3. Fix

Trace to root cause. Never paper over symptoms.

After fixing, grep for the same pattern elsewhere — the bug may exist in multiple locations.

4. Verify

Run the original failing command. Confirm it passes. Run related tests to check for regressions.

5. Commit

Commit message describes the root cause, not symptoms.

# Good: fix(queue): stale lock file prevented task dequeue after crash
# Bad:  fix: tasks not running

© poteto, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/oops of poteto/noodle.

Open the folder on GitHubat commit 82d2921

Compare with similar skills

Oops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Oops compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Oops this skillpoteto/noodle437—~481Automated safety check: PassMIT
Swig Testswig/swig6.3k—~2.3kAutomated safety check: PassCustom licence
Triage CI FailureDataDog/datadog-agent3.8k—~2.3kAutomated safety check: PassApache-2.0
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Fix Ready PRsfastrepl/anarlog9.5k—~1.4kAutomated safety check: PassMIT
Trx Analysismicrosoft/vstest969—~1.8kAutomated safety check: PassMIT

Similar skills

  • Swig Test

    swig/swig

    Run SWIG test suite for specific languages. An agent skill from swig/swig.

    6.3k GitHub stars~2.3k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Triage CI Failure

    DataDog/datadog-agent

    Official

    Classify a failed CI as either caused by an active incident, flakiness, or a true code regression.

    3.8k GitHub stars~2.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Fix Ready PRs

    fastrepl/anarlog

    Inspect every open non-draft PR for CI failures and unresolved Cursor Bugbot findings, then fix them on the existing PR branches.

    9.5k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Trx Analysis

    microsoft/vstest

    Official

    Parse and analyze Visual Studio TRX test result files. An agent skill from microsoft/vstest.

    969 GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed
  • Wio

    workersio/skills

    Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.

    190 GitHub stars~5.8k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

More from poteto/noodle

All 26 skills in this repo
  • Meditate

    poteto/noodle

    Audit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities.

    437 GitHub stars~1.1k tokensUpdated 6 mo ago
    Auto-check passed
  • Ruminate

    poteto/noodle

    Mine past Claude Code and Codex conversations for uncaptured patterns, corrections, and knowledge.

    437 GitHub stars~1.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Ast Grep

    poteto/noodle

    Structural code search via ast-grep — use when code shape and element relationships matter, not just text.

    437 GitHub stars~531 tokensUpdated 6 mo ago
    Auto-check passed
  • Execute

    poteto/noodle

    Implementation methodology for executing tasks. An agent skill from poteto/noodle.

    437 GitHub stars~989 tokensUpdated 6 mo ago
    Auto-check passed
  • Noodle

    poteto/noodle

    Operate the Noodle CLI — explain commands, find flags, create/edit .noodle.toml config.

    437 GitHub stars~1.3k tokensUpdated 6 mo ago
    Auto-check passed
  • Plan

    poteto/noodle

    Systematic planning for medium-to-large tasks. An agent skill from poteto/noodle.

    437 GitHub stars~1.6k tokensUpdated 6 mo ago
    Auto-check passed

Categories

Questions about Oops

What does Oops do?

Infrastructure fix for broken builds, failed tests, stale state, and environment drift. Oops is an agent skill from poteto/noodle. Infrastructure fix for broken builds, failed tests, stale state, and environment drift.

When should I use Oops?

Oops fits situations like: environment drifts; tasks that involve Failing and flaky tests.

How do I install Oops in Claude Code?

Run `npx skills add poteto/noodle --skill oops -a claude-code`. Or copy the skill folder (.agents/skills/oops in poteto/noodle) into .claude/skills/oops in your project. Claude Code loads it when a task matches its description.

How do I install Oops in Codex?

Run `npx skills add poteto/noodle --skill oops -a codex`. Or copy the skill folder (.agents/skills/oops in poteto/noodle) into .agents/skills/oops in your project. Codex loads it when a task matches its description.

Can I use Oops in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add poteto/noodle --skill oops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oops, .gemini/skills/oops, .github/skills/oops and .opencode/skills/oops in your project.

What does Oops need to run?

SKILL.md names no scripts, command-line tools or credentials: Oops is instructions for the agent only.

Does Oops access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Oops safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Oops use?

Oops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Oops use?

About 481 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Oops?

Skills that share tags, products or a category with Oops: Swig Test (swig/swig, 6.3k stars), Triage CI Failure (DataDog/datadog-agent, 3.8k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Fix Ready PRs (fastrepl/anarlog, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Oops?

poteto (a GitHub user) maintains it in poteto/noodle, which has 437 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on March 19, 2026.

Source: poteto/noodle on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.