agentleFS
surfmind-spacesurfmind-space/awesome-surfmind/skills/outline-builder/SKILL.md

outline-builder

Skill8 starsChanged 5 months agoMITView on GitHub

Turns messy notes, pages, or selected text into a structured outline with headings, key points, evidence, and gaps. Use when the user wants to "organize my notes", "create an outline", "structure my thoughts", "outline from notes", or pull bullet points and key points out of rough material.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep headings specific enough that the user can draft from them directly.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Outline Builder

Turn the user's selected text, page, or notes into a structured outline with headings, key points, evidence, and gaps. Work only from what is present; never invent facts, numbers, names, or sources.

  1. Determine the target format and audience.
  2. Extract the main thesis, supporting points, evidence, examples, objections, and gaps.
  3. Arrange sections in a logical reading order.
  4. Keep headings specific enough that the user can draft from them directly.

Return concise headings and include these sections when they fit: Working title, Outline, Evidence to include, Gaps to fill.

Separate supported facts from assumptions and recommendations. Preserve important names, numbers, links, code, dates, currencies, and user constraints. Do not over-structure tiny inputs, and do not hide weak evidence inside confident headings. If the context is insufficient, say what is missing and give the best supported next step.

Example

Notes (selected text):

remote work post — pros: less commute, focus time. cons: lonely, harder onboarding. survey said 70% want hybrid? double check. mention manager training

Outline:

Working title: The Case for Hybrid Work

Outline

  1. Hook — the commute people got back
  2. Benefits of remote: reclaimed time, deep focus
  3. The costs: isolation, harder onboarding
  4. Why hybrid splits the difference
  5. What makes hybrid work: manager training

Evidence to include

  • Survey: 70% prefer hybrid (verify the figure and source before publishing)

Gaps to fill

  • A concrete onboarding example
  • What "manager training" should cover

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.