Agent skill

Remediation Loop

by Inebrio in Inebrio/Routerly

Drive a story from BLOCKED back to PASS after validation, with a hard iteration cap.

AGPL-3.0Auto-check passed

Install Remediation Loop

skills CLI
$ npx skills add Inebrio/Routerly --skill remediation-loop -a claude-code

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

GitHub CLI
$ gh skill install Inebrio/Routerly remediation-loop --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/Inebrio/Routerly.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/remediation-loop .claude/skills/remediation-loop && 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
remediation-loop
GitHub stars
100
Token cost
~609 tokens
SKILL.md length
367 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Drive a story from BLOCKED back to PASS after validation, with a hard iteration cap.

  • Works in 4 steps: Assign. Give each blocking finding to… → Fix, narrowly. The engineer fixes the… → Re-validate in full. The validator… → …
  • A validation report lists blocking findings
  • SKILL.md covers One iteration, Cap: three iterations, Rules and Record
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Remediation Loop is an agent skill from Inebrio/Routerly. Drive a story from BLOCKED back to PASS after validation, with a hard iteration cap. Use when a validation report lists blocking findings.

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

The repository describes itself as: Self-hosted LLM gateway that routes requests across AI providers (OpenAI, Anthropic, Gemini, Mistral, Ollama) using intelligent multi-policy scoring — including an LLM-native… The licence is AGPL-3.0.

When your agent uses it

  • A validation report lists blocking findings

Example prompts

  • “/remediation-loop”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Assign. Give each blocking finding to whoever owns that surface. One
  2. Fix, narrowly. The engineer fixes the listed findings and nothing
  3. Re-validate in full. The validator re-runs the whole protocol, not
  4. Read the verdict. PASS ends the loop. BLOCKED starts the next

What it can do on your machine

Read from SKILL.md and the folder at commit bcf58f1. 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

Remediation Loop loads about 609 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 367 words of instructions outside code blocks.

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

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 Inebrio/Routerly at commit bcf58f1, republished under its AGPL-3.0 licence (© Inebrio). 367 words, ~609 tokens.

Download SKILL.mdSave it as .claude/skills/remediation-loop/SKILL.md (or your agent's skills folder).
name
remediation-loop
description
Drive a story from BLOCKED back to PASS after validation, with a hard iteration cap. Use when a validation report lists blocking findings.

Remediation loop

Triggered by blocking findings, and by nothing else. Non-blocking findings are recorded in the story record and never restart this loop.

One iteration

  1. Assign. Give each blocking finding to whoever owns that surface. One engineer per finding where the findings are independent; one engineer for all of them where they share a file.
  2. Fix, narrowly. The engineer fixes the listed findings and nothing else. No refactor, no cleanup, no improvement noticed in passing: an unrelated change in a remediation diff is how a second bug arrives disguised as a fix.
  3. Re-validate in full. The validator re-runs the whole protocol, not only the failed criteria. A fix that breaks a criterion that passed before is the most common outcome, and a delta check never sees it.
  4. Read the verdict. PASS ends the loop. BLOCKED starts the next iteration.

Cap: three iterations

After the third BLOCKED, stop. Do not start a fourth.

Escalate to the human with: the findings that survived, what was tried in each iteration and why it did not work, whether the blocker is in the code or in the story, and the options with their costs.

Show full SKILL.md (173 more words)Show less

Rules

  • A finding fixed by weakening its check is not fixed. Deleting the test, loosening the assertion, or removing the criterion returns the story to the validator as still blocked.
  • The engineer does not close a finding. Only the validator's next report closes it.
  • A new blocking finding introduced by a fix counts against the same cap. It does not reset the counter: introducing blockers while removing them is exactly the signal the cap exists to catch.
  • The same finding surviving two iterations means the diagnosis is wrong. Stop patching the symptom, re-read the code around it, and say what you now think is happening before the third attempt.
  • A finding that contradicts the story is not a fix. It goes back up as a story problem, and the loop pauses until that is answered.

Record

Append to the story's validation file, one block per iteration: the findings, who took them, what changed, and the resulting verdict. The history is what makes the third failure legible to the human who has to decide.

© Inebrio, AGPL-3.0. 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/remediation-loop of Inebrio/Routerly.

Open the folder on GitHubat commit bcf58f1

Compare with similar skills

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

Remediation Loop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Remediation Loop this skillInebrio/Routerly100—~609Automated safety check: PassAGPL-3.0
Block Kitopenclaw/openclaw392k—~624Automated safety check: PassMIT
Story ReadinessDonchitos/Claude-Code-Game-Studios26k—~6.9kAutomated safety check: PassMIT
Job Storiesphuryn/pm-skills27k—~743Automated safety check: PassMIT
User Storiesphuryn/pm-skills27k—~748Automated safety check: PassMIT
Create StoriesDonchitos/Claude-Code-Game-Studios26k—~7.2kAutomated safety check: PassMIT

Similar skills

  • Block Kit

    openclaw/openclaw

    Use proactively for structured or interactive Slack replies, and when asked to author or validate native Slack Block Kit JSON.

    392k GitHub stars~624 tokensUpdated today
    Auto-check passed
  • Story Readiness

    Donchitos/Claude-Code-Game-Studios

    Is a story implementation-ready?. An agent skill from Donchitos/Claude-Code-Game-Studios.

    26k GitHub stars~6.9k tokensUpdated 9 days ago
    Product & Project ManagementAuto-check passed
  • Job Stories

    phuryn/pm-skills

    Turns a feature into job stories in the When, I want to, so I can format, each with six to eight acceptance criteria tied to the user's situation and outcome.

    27k GitHub stars~743 tokensUpdated 23 days ago
    Product & Project ManagementAuto-check passed
  • User Stories

    phuryn/pm-skills

    Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria.

    27k GitHub stars~748 tokensUpdated 23 days ago
    Product & Project ManagementAuto-check passed
  • Create Stories

    Donchitos/Claude-Code-Game-Studios

    Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria.

    26k GitHub stars~7.2k tokensUpdated 9 days ago
    Product & Project ManagementAuto-check passed
  • Stories

    sanity-io/sanity

    Official

    Invoke FIRST, before creating, editing, or deleting components, stories, styles, CSS, themes, colors, or design tokens — anything that changes how the UI looks, no exceptions.

    6.4k GitHub stars~621 tokensUpdated today
    Frontend & DesignAuto-check passed

More from Inebrio/Routerly

All 17 skills in this repo
  • Docs Conventions

    Inebrio/Routerly

    Where documentation lives in this repository, how a page is structured, and what a change owes the docs.

    100 GitHub stars~624 tokensUpdated 2 days ago
    Auto-check passed
  • Feature Lifecycle

    Inebrio/Routerly

    Run a Tier 1 or Tier 2 feature end to end — feature level, story level, parallelism, integration, and retrospective.

    100 GitHub stars~3k tokensUpdated 2 days ago
    Auto-check passed
  • Story Lifecycle

    Inebrio/Routerly

    Run one user story end to end in its own worktree, from claim to merge.

    100 GitHub stars~905 tokensUpdated 2 days ago
    Auto-check passed
  • Test Conventions

    Inebrio/Routerly

    Where tests live in this repository, how to run them, and what a story owes in coverage.

    100 GitHub stars~467 tokensUpdated 2 days ago
    Auto-check passed
  • Validation Protocol

    Inebrio/Routerly

    How to validate a story against its criteria and write the report, including what counts as evidence and what counts as blocking.

    100 GitHub stars~628 tokensUpdated 2 days ago
    Auto-check passed
  • Analysis Format

    Inebrio/Routerly

    Shape of a feature analysis document (00-analysis.md). An agent skill from Inebrio/Routerly.

    100 GitHub stars~472 tokensUpdated 2 days ago
    Auto-check passed

Questions about Remediation Loop

What does Remediation Loop do?

Drive a story from BLOCKED back to PASS after validation, with a hard iteration cap. Remediation Loop is an agent skill from Inebrio/Routerly. Drive a story from BLOCKED back to PASS after validation, with a hard iteration cap.

When should I use Remediation Loop?

Remediation Loop fits situations like: A validation report lists blocking findings.

How do I install Remediation Loop in Claude Code?

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

How do I install Remediation Loop in Codex?

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

Can I use Remediation Loop 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 Inebrio/Routerly --skill remediation-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/remediation-loop, .gemini/skills/remediation-loop, .github/skills/remediation-loop and .opencode/skills/remediation-loop in your project.

What does Remediation Loop need to run?

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

Does Remediation Loop 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 Remediation Loop 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 Remediation Loop use?

Remediation Loop is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Remediation Loop use?

About 609 tokens (SKILL.md is roughly 2.4k 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 Remediation Loop?

Skills that share tags, products or a category with Remediation Loop: Block Kit (openclaw/openclaw, 392k stars), Story Readiness (Donchitos/Claude-Code-Game-Studios, 26k stars), Job Stories (phuryn/pm-skills, 27k stars) and User Stories (phuryn/pm-skills, 27k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Remediation Loop?

Inebrio (a GitHub organization) maintains it in Inebrio/Routerly, which has 100 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.

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