Repair Orchestrator logo

Repair Orchestrator

Community
XuanRanL
repair-orchestrator

5-level repair escalation when quality gates fail. Surgical → Section-rewrite → Stage-rewrite → Full-regen → From-scratch. Hard cap 4 rounds total. Use when quality.json reports overall_passed=false OR reviewer rejects. Last line of defense before declaring an article unsalvageable.

Overview

PublisherXuanRanL
Repositoryloamwright-SEO-Skill
Skill namerepair-orchestrator
Stars
52
Forks
9
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by XuanRanL on GitHub. Read the source before you install it.

Installation

Install the Repair Orchestrator AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/XuanRanL/loamwright-SEO-Skill/tree/main/subskills/cross-cutting/repair-orchestrator
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/XuanRanL/loamwright-SEO-Skill.git /tmp/loamwright-SEO-Skill
mkdir -p .claude/skills
cp -r /tmp/loamwright-SEO-Skill/subskills/cross-cutting/repair-orchestrator .claude/skills/repair-orchestrator
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Repair Orchestrator in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Repair Orchestrator on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Repair Orchestrator is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Repair Orchestrator

The escalating repair pipeline. Driven by quality.json findings.

Inputs

  • workspace/{task_id}/quality.json (one or more gates failed)
  • workspace/{task_id}/review.json (if independent-reviewer ran)
  • state.repair_iteration (current attempt count; cap = 4)

5 escalation levels

Level 1 — SURGICAL (cheapest, fastest)
  Edit specific lines indicated by quality.json.repairs[].instruction
  Use Edit tool only (preserve everything else)
  If quality improves ≥3 score → progress; loop back at Level 1 again
  If improvement <3 → escalate to Level 2

Level 2 — SECTION-REWRITE
  Identify which section(s) most contribute to failures
  Spawn writer agent for that section with:
    - original section spec
    - failures list as "things to fix"
    - stronger constraints
  Re-run quality gates
  If still failing → escalate to Level 3

Level 3 — STAGE-REWRITE
  Rerun one whole stage of build phase:
    - If structural issues: outline-architect (revise outline)
    - If reference issues: fact-check-and-citation (verify everything again)
    - If voice issues: humanizer (with stricter settings)
  Re-run quality gates
  If still failing → escalate to Level 4

Level 4 — FULL-REGEN
  Rerun all of Phase Build (preserve research.json + angle.json + outline.json)
  Re-run quality gates
  If still failing → escalate to Level 5

Level 5 — FROM-SCRATCH
  Rerun from Plan phase:
    - Pick alternative title from angle.alternative_titles_considered
    - New outline from scratch
    - New writer agents
  Re-run quality gates
  If still failing → HALT, return best-of-N to user

Hard cap: 4 total rounds across all levels. After round 4, return whatever artifact had highest quality.json score with a documented "could not converge" message.

Decision tree

Read quality.json.repairs[] and quality.gates:

python
def pick_level(quality, prior_iterations, prior_level):
    # First iteration after gate fail
    if prior_iterations == 0:
        return 1  # Always start surgical
    
    # Surgical didn't improve enough
    if prior_level == 1:
        # Was improvement small?
        delta = current_score - prior_score
        if delta < 3:
            return 2  # Escalate
        return 1  # Continue surgical
    
    # Section rewrite didn't help
    if prior_level == 2:
        # How many sections needed rewrite?
        problem_sections = [s for s in sections if has_issues(s)]
        if len(problem_sections) > 3:
            return 3  # Stage-level fix
        return 2  # Try again
    
    # Stage rewrite didn't help → full regen
    if prior_level == 3:
        return 4
    
    # Full regen didn't help → from scratch
    if prior_level == 4:
        return 5

What each level fixes

Level 1: Surgical — best for

  • Banned word hits
  • Em-dash hits
  • Citation marker → APA replacement
  • Minor wording polish

Level 2: Section-rewrite — best for

  • One H2 missing Citation Capsule
  • One section badly off voice
  • Word count outside band in 1-2 sections
  • Format doesn't match for 1-2 sections

Level 3: Stage-rewrite — best for

  • Structural: H2 hierarchy wrong → outline-architect
  • Multiple unverified citations → fact-check-and-citation
  • Voice inconsistent across most sections → humanizer (rewrite mode)

Level 4: Full-regen — best for

  • AI-Slop score consistently high
  • Many sections fail quality
  • Multiple gates failing

Level 5: From-scratch — last resort

  • Article topic just doesn't work in current angle
  • Try alternative title from angle.alternative_titles_considered
  • Completely new outline

Cost

Each level has roughly cumulative cost (worst case 4 rounds):

  • Level 1 × 4 iterations: ~$0.10 (cheap edits)
  • Level 1 + 1 × Level 2: ~$0.25 (one section rewrite)
  • Up to Level 3: ~$0.50 (one stage rerun)
  • Up to Level 4: ~$1.50 (full build rerun)
  • Up to Level 5: ~$2.50 (mostly full pipeline rerun)

Cap is set so total repair never exceeds ~$2.50 over baseline article cost.

Output

After each escalation, write workspace/{task}/repair-log.json (append):

json
{
  "iterations": [
    {
      "iteration": 1,
      "level": 1,
      "trigger": "AI-Slop score 24 > 20 threshold",
      "actions": [
        {"type": "edit", "line": 47, "before": "crucial", "after": "central"}
      ],
      "score_before": 24, "score_after": 18,
      "duration_seconds": 12,
      "verdict": "improved, but still failing other gates"
    },
    {
      "iteration": 2,
      "level": 1,
      "trigger": "Em-dash count 1 > 0",
      "actions": [...],
      "score_before": 18, "score_after": 16,
      "verdict": "ship"
    }
  ],
  "final_level": 1,
  "total_iterations": 2,
  "outcome": "passed"
}

Handoff

If passed:

  • recommended_next_skill: independent-reviewer (final blessing)
  • → phase-publish if reviewer approves

If exhausted (4 rounds done, still failing):

  • completion_status: BLOCKED
  • Return workspace/{task}/repair-log.json + best-of-N draft to user
  • User decides: accept with caveats, abort, or take over manually

See also

  • schemas/quality.schema.json (input format)
  • agents/editor-in-chief.md (tombstoned 2026-08-12 — Level 2 dispatches agents/writer.md below)
  • agents/writer.md (Level 2 dispatched agent)
  • subskills/build/section-drafter/SKILL.md (Level 3/4 dispatched skill)

Frequently asked questions

What does the Repair Orchestrator AI skill do?

5-level repair escalation when quality gates fail. Surgical → Section-rewrite → Stage-rewrite → Full-regen → From-scratch. Hard cap 4 rounds total. Use when quality.json reports overall_passed=false OR reviewer rejects. Last line of defense before declaring an article unsalvageable.

Why use Repair Orchestrator on TypingMind?

Because you install it once and use it with any model. Repair Orchestrator is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Repair Orchestrator in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/XuanRanL/loamwright-SEO-Skill/tree/main/subskills/cross-cutting/repair-orchestrator. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Repair Orchestrator?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Repair Orchestrator?

As many as you like. As long as a model supports skills, you can use Repair Orchestrator with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Repair Orchestrator AI skill free?

Yes. It is published on GitHub by XuanRanL under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇