Outline Builder logo

Outline Builder

Community
WILLOSCAR
outline-builder

Convert a taxonomy (`outline/taxonomy.yml`) into a bullet-only outline (`outline/outline.yml`) with sections/subsections.

Overview

PublisherWILLOSCAR
Repositoryresearch-units-pipeline-skills
Skill nameoutline-builder
Stars
513
Forks
39
Bundled files
7
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.

  • 7 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Outline Builder 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/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/outline-builder
  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/WILLOSCAR/research-units-pipeline-skills.git /tmp/research-units-pipeline-skills
mkdir -p .claude/skills
cp -r /tmp/research-units-pipeline-skills/.codex/skills/outline-builder .claude/skills/outline-builder
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Outline Builder 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 Outline Builder 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 Outline Builder 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.

Outline Builder

Triggers & routing

  • Trigger: outline builder, bullet outline, outline.yml, 大纲生成, bullets-only.
  • Use when: structure 阶段(NO PROSE),已有 taxonomy,需要生成可映射/可写作的章节与小节骨架(每小节≥3 bullets)。
  • Skip if: 已经有批准过且可映射的 outline(避免无意义 churn)。
  • Network: none.
  • Guardrail: bullets-only;移除 TODO/模板语句;每小节至少 3 个可检查 bullets。

outline/outline.refined.ok freezes a reviewed outline only while the marker is newer than the outline, all declared inputs, the defaults asset, and the generator. Upstream changes invalidate the marker and trigger a backed-up regeneration.

Build outline/outline.yml from either:

  • outline/taxonomy.yml (legacy H3-first compatibility path)
  • outline/chapter_skeleton.yml + outline/section_briefs.jsonl (section-first transition path)

Compatibility mode is active: this migration keeps the current output contract while moving intro/related defaults, Stage A bullet templates, and domain-specific comparison framing into references/ and assets/.

Load Order

Always read:

  • references/overview.md
  • references/stage_a_contract.md

Read by task:

  • references/intro_related_patterns.md when changing Introduction / Related Work defaults
  • references/examples_good.md and references/examples_bad.md for bullet calibration

Machine-readable asset:

  • assets/outline_defaults.yaml

Inputs

Required:

  • outline/taxonomy.yml

Optional human calibration only:

  • ref/agent-surveys/STYLE_REPORT.md
  • ref/agent-surveys/text/

Output

Keep the current output contract:

  • outline/outline.yml

Compatibility mode

Current mode is reference-first with script compatibility:

  • front-chapter defaults live in assets/outline_defaults.yaml
  • Stage A bullet defaults and comparison-axis packs live in assets/outline_defaults.yaml
  • examples and boundary rules live in references/
  • scripts/run.py still owns outline materialization, section-first input selection, and placeholder-safe overwrite behavior

Script boundary

Use scripts/run.py only for:

  • loading taxonomy or section-first structure inputs plus the defaults asset
  • rendering the outline skeleton deterministically
  • preserving existing non-placeholder outlines
  • choosing comparison-axis packs from machine-readable defaults

Do not treat the script as the main place for:

  • domain framing for Introduction / Related Work
  • long bullet banks or writing exemplars
  • prompt-heavy guidance about how a good outline should read

Output shape rules

Keep these stable:

  • outline/outline.yml is a YAML list
  • Introduction and Related Work remain the first two H2 sections
  • each H3 subsection contains the Stage A bullets: Intent: / RQ: / Evidence needs: / Expected cites:
  • each H3 subsection adds several topic-specific bullets after the Stage A fields
  • the helper never overwrites non-placeholder user work

Quick Start

  • uv run python .codex/skills/outline-builder/scripts/run.py --help
  • uv run python .codex/skills/outline-builder/scripts/run.py --workspace <workspace>

Execution notes

When running this skill in compatibility mode, scripts/run.py currently reads:

  • outline/taxonomy.yml, or
  • outline/chapter_skeleton.yml + outline/section_briefs.jsonl
  • assets/outline_defaults.yaml

The optional style references under ref/agent-surveys/ are for human calibration only:

  • use ref/agent-surveys/STYLE_REPORT.md to sanity-check chapter counts / thickness
  • skim ref/agent-surveys/text/ only to calibrate structure rather than wording

Script

Quick Start

  • uv run python .codex/skills/outline-builder/scripts/run.py --workspace <workspace>

All Options

  • --workspace <dir>
  • --unit-id <id>
  • --inputs <path1;path2>
  • --outputs <path1;path2>
  • --checkpoint <C*>

Examples

  • uv run python .codex/skills/outline-builder/scripts/run.py --workspace <workspace>

Troubleshooting

  • If Related Work still carries domain-specific framing, patch assets/outline_defaults.yaml before changing Python.
  • If subsection bullets feel generic, review references/stage_a_contract.md and references/examples_good.md.
  • If the outline is structurally valid but too fragmented, reroute to outline-budgeter rather than expanding this script.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Outline Builder AI skill do?

Convert a taxonomy (`outline/taxonomy.yml`) into a bullet-only outline (`outline/outline.yml`) with sections/subsections.

Why use Outline Builder on TypingMind?

Because you install it once and use it with any model. Outline Builder 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 Outline Builder in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/outline-builder. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Outline Builder?

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 Outline Builder?

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

Is the Outline Builder AI skill free?

It is published on GitHub by WILLOSCAR. Check the repository for licensing terms. 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 👇