Fable New Issue Loop logo

Fable New Issue Loop

Community
richkuo
fable-new-issue-loop

Use when the user asks to have a Fable 5.1 subagent draft and file a GitHub issue, then autonomously drive it all the way to a reviewed PR in one shot — "fable-new-issue-loop", "fable create the issue and run it to completion". Runs fable-new-issue to create a fully-specified issue (drafted by a Fable 5.1 subagent), then hands the new issue's `owner/repo#N` reference to validate-issue-loop (validate → update → work-on-issue-loop) — stopping instead when a duplicate is found or the discussion hasn't converged on one issue.

Overview

Publisherrichkuo
Repositoryrk-skills
Skill namefable-new-issue-loop
Stars
50
Forks
8
Bundled files
Instructions only
LicenseMIT
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 richkuo on GitHub. Read the source before you install it.

Installation

Install the Fable New Issue Loop 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/richkuo/rk-skills/tree/main/skills/fable-new-issue-loop
  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/richkuo/rk-skills.git /tmp/rk-skills
mkdir -p .claude/skills
cp -r /tmp/rk-skills/skills/fable-new-issue-loop .claude/skills/fable-new-issue-loop
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Fable New Issue Loop 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 Fable New Issue Loop 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 Fable New Issue Loop 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.

fable-new-issue-loop

Chain fable-new-issue → validate-issue-loop into one autonomous run: a Fable 5.1 subagent drafts the issue, the main agent files it, and the loop drives it to a reviewed PR without a human in between.

This skill is new-issue-loop with a different front of the chain. Follow the new-issue-loop skill for the full procedure: the complete-issue rule, the input contract, the stop gate, the handoff to validate-issue-loop (always the explicit owner/repo#N reference), the ownership of the plan: yes signal, the report format, and the Red Flags. Apply only the deltas below.

Deltas from new-issue-loop

  • Step 1, front of the chain. Invoke the fable-new-issue skill (Skill tool, skill: fable-new-issue) in place of new-issue. Let it run its full process (Fable 5.1 subagent draft, duplicate gate, spot-check, filing) and capture the created issue from its report as owner/repo#N per new-issue-loop step 1.
  • Step 2, stop gate. new-issue-loop's stop gate applies with one extra row for the Fable draft; the effective table:
ConditionAction
fable-new-issue found an existing open issue/PR already covering it (no issue filed)STOP. Report the duplicate and the offer to update/comment instead; do not merge scopes yourself.
The conversation held several distinct candidatesIf one clearly converged, file it and continue the chain with it; the unfiled candidates go in the final report. If none clearly converged, STOP — report the candidates and ask which to file. Never bundle, never auto-file the extras.
fable-new-issue split the work and named unfiled follow-upsContinue with the core issue only; relay the unfiled follow-ups in the final report.
The draft was structurally wrong and fable-new-issue paused for a human decisionSTOP. Relay what is off. Do not file or re-dispatch on your own.
The drafting dispatch failed a second time on the Agent path (fable-dispatch section 7)STOP. Relay the failure report. Do not re-dispatch, and do not draft or file the issue yourself.
The section 7 snapshot diff shows that the drafting subagent wroteSTOP. Relay the changed paths. Do not revert them, file, or continue on that tree; the user decides.
  • Step 4, report. Mark the issue line as drafted by the model that served, as fable-new-issue recorded it (Fable 5.1 when Fable served). Cap the whole report at 55 words and 5 sentences, plain simple English in ASD-STE100 — apply the Response Style rules in CLAUDE.md/AGENTS.md.
  • One extra Red Flag. Tempted to skip the Fable subagent and draft or file the issue yourself to go faster: never.

Frequently asked questions

What does the Fable New Issue Loop AI skill do?

Use when the user asks to have a Fable 5.1 subagent draft and file a GitHub issue, then autonomously drive it all the way to a reviewed PR in one shot — "fable-new-issue-loop", "fable create the issue and run it to completion". Runs fable-new-issue to create a fully-specified issue (drafted by a Fable 5.1 subagent), then hands the new issue's `owner/repo#N` reference to validate-issue-loop (validate → update → work-on-issue-loop) — stopping instead when a duplicate is found or the discussion hasn't converged on one issue.

Why use Fable New Issue Loop on TypingMind?

Because you install it once and use it with any model. Fable New Issue Loop 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 Fable New Issue Loop in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/richkuo/rk-skills/tree/main/skills/fable-new-issue-loop. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Fable New Issue Loop?

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 Fable New Issue Loop?

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

Is the Fable New Issue Loop AI skill free?

Yes. It is published on GitHub by richkuo under the MIT 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 👇