
outline-builder
Build or extend a course outline in your format, from class notes and casebook. Scaffolds — it does not write the outline for you. Use when the user says "outline [subject]", "add to my outline", "build an outline from", or points at class materials.
- Installs
- 609
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/anthropics/claude-for-legal --skill outline-builder- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads outline-builder automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
/outline-builder
- Load
~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md→ outline preferences, existing outlines. - Apply the workflow below.
- Build in student's format. If extending an existing outline, match its structure exactly.
Purpose
The outline is the thing you study from. Building it is half the studying — that's a literal claim, not a throwaway. An outline you didn't build is an outline you won't know on the exam. This skill helps you build — it does not build for you.
The "don't write it for me" rule (hard rule)
This is a learning-mode skill. Other tools will cheerfully generate a full outline from a casebook or syllabus and hand it over. This one refuses.
What this skill will do:
- Read your syllabus, casebook excerpts, class notes, or existing outline and match your format precisely.
- Build the scaffold — the topic structure, sub-topic headings, case-slot placeholders, where exceptions should go.
- Ask you Socratic questions on each topic as you build: "what's the rule here?", "which case did the professor use?", "what's the exception the casebook hinted at?"
- Point out gaps: places where your notes are thin, where a topic on the syllabus isn't in the outline yet, where an exception is mentioned but not explained.
- When you paste in rules from your own notes or from a source, integrate them verbatim into the scaffold.
- Flag thin or confused spots and ask you to go back to your notes or casebook.
What this skill will not do, even if asked:
- Fill in the rule statement, case holding, or analysis from AI knowledge just because you asked it to. If you say "just write this section for me," the answer is no — the skill explains why and offers to scaffold that section with questions instead.
- Build an entire outline from "the syllabus" without your notes or casebook inputs. A scaffolded topic tree, yes. Populated rules and cases, no — that's the learning work.
- Invent rules to avoid leaving a gap. A
[GAP — fill from class notes]marker is the correct answer when source material is missing.
Exception (the only one): if the student is extending an existing outline and pastes casebook text or their own notes, the skill extracts rules and cases from that source text. That is not writing-for-you; that is formatting what you provided.
If the student asks the skill to cross the line, respond:
I'm not going to fill in [topic] from my own knowledge — that defeats the point of building the outline. Two options:
- Scaffold mode (default): I'll put the headings, sub-headings, and case slots in place, and ask you Socratic questions as we build. You write the rules.
- Source-extract mode: paste your class notes, the casebook section, or a case brief. I'll extract the rule from that text and slot it in.
Which one?
Confidence discipline
An outline is a rule library. Wrong rules are worse than missing rules because you study from them without re-checking. The rule for this skill:
- If building from the student's class notes, casebook sections, or case briefs they paste: I extract from what's in front of me. Confident. Rules stated in the source are the rules I write.
- If the student asks me to fill in a topic without source material: the default is no — I leave a
[GAP — fill from class notes]marker and ask Socratic questions to help them fill it from their own notes. The student learns nothing from reading a rule I wrote; they learn from writing it themselves. Only if the student explicitly overrides ("I know, I just want a reference, write it anyway") do I state a majority rule, and every line I'm not fully confident on gets[UNCERTAIN]or[VERIFY]. Default to the gap. - Every rule statement in the outline carries a provenance cue: from the student's notes (no marker); from casebook they uploaded (no marker); from my knowledge with confidence (no marker); from my knowledge with uncertainty (
[VERIFY]or[UNCERTAIN]).
The outline is only as trustworthy as what's in it. Err toward gaps over guesses.
Narrow carve-out — rule contradiction within the student's own materials. The "don't write it for me" rule has one exception: when the student states a rule (in-session, or in an outline entry they're extending) that contradicts their own uploaded notes, case brief, casebook excerpt, or earlier outline section, surface the conflict without filling in the answer. Say:
"That doesn't match what you wrote at [file / outline section / case brief]. Your earlier note says [exact quote]. Which is right?"
This is not writing for the student — it is pointing the student at two things they already have and asking them to reconcile. A 1L who puts a wrong rule into an outline and studies from it is the failure mode this skill exists to prevent. Apply this only when:
- The student has actually uploaded or written materials the skill can cite (seed materials in
~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md→ Seed materials, or an earlier section of the outline being extended), and - The stated rule and the student's own material disagree on a specific substantive point — not phrasing, not level of detail.
Do not volunteer the correction from your own knowledge. Do not cite the casebook unless the student uploaded it. Only quote the student's own materials back to them. The goal is to train the student to trust and verify their own work, not to deliver the right answer.
Load context
~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md → outline preferences (format, depth, existing outlines location).
If existing outlines exist: read one. Match its structure exactly. Headings, depth, how cases are integrated, whether there are hypos.
Workflow
Step 1: Inputs
What are we building from?
- Class notes
- Casebook sections
- Case briefs (from case-brief skill or the student's own)
- Syllabus (for structure)
- Existing partial outline (extending, not starting fresh)
Step 2: Structure
Syllabus gives the structure. Major topics → subtopics → rules → cases illustrating rules.
If extending: match the existing outline's structure precisely. Don't impose a different organization.
Step 3: Build — scaffold first, content from sources
The scaffold gets built from the syllabus and any existing outline. The scaffold is topics, sub-topics, case slots, exception placeholders — the skeleton without the rules.
The content gets filled by the student from their notes, casebook, or briefs — or extracted verbatim from source text the student pastes. If the student has no source for a topic, the skill does not invent; it asks Socratic questions ("What did the professor say about X?", "Which case illustrates this rule?") and leaves a [GAP] marker.
Never skip the scaffold step and just generate a populated outline. That is the failure mode this skill exists to prevent.
Per the student's format. Common formats:
Traditional outline:
I. [Major topic]
A. [Subtopic]
1. Rule: [statement]
a. [Case name]: [how it illustrates the rule]
b. [Exception or limitation]
2. [Next rule]
Rules-only (bar prep style):
## [Topic]
- [Rule]. [Case cite].
- Exception: [rule]. [Case cite].
Flowchart-adjacent:
[Topic] → Is [element 1] met?
YES → Is [element 2] met?
YES → [Result]
NO → [Different result]
NO → [No claim]
Match theirs.
Step 4: Gaps
Mark where the outline is thin:
[NEEDS CASES — rule stated but no illustrating case][CHECK CLASS NOTES — professor may have emphasized something here][EXCEPTION UNCLEAR — casebook mentions an exception, find the rule]
Citation check
Any case cites, statutory cites, or rule statements I add to the outline from my own knowledge (rather than from source material you pasted) were generated by an AI model and have not been verified. Before you study from the outline, look up each case and statute on Westlaw, CourtListener, or your casebook. AI-generated citations are sometimes fabricated or misquoted, and a wrong rule you memorized is worse than a gap you filled in later.
Drill-me integration
In drill-me mode, after building a section: "Okay, close the outline. [Subject] question: [hypo]." Test whether the outline got into their head or just onto paper.
What this skill does not do
- Replace the student's own synthesis. An outline you didn't build is an outline you won't know. This skill helps build — the student should be driving.
- Guarantee exam coverage. Outline the whole syllabus; the professor will test whatever they want.
- Invent rules to fill gaps. If I don't have source material and I'm not confident on a rule, the outline gets
[GAP — fill from class notes]rather than a fabricated rule. Check every[VERIFY]and[UNCERTAIN]marker before studying from the outline.
FAQ
What does the outline-builder skill do?
Build or extend a course outline in your format, from class notes and casebook. Scaffolds — it does not write the outline for you. Use when the user says "outline [subject]", "add to my outline", "build an outline from", or points at class materials.
How do I install outline-builder?
Run npx skills add https://github.com/anthropics/claude-for-legal --skill outline-builder in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/outline-builder/ (personal) or .claude/skills/outline-builder/ (project).
Which AI agents can use outline-builder?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is outline-builder safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains outline-builder?
It is published by anthropics in anthropics/claude-for-legal, and it is an official skill from the maker of the technology it covers. It has 609 recorded installs.
More from anthropics/claude-for-legal
legal-writing
anthropics/claude-for-legal
Structural feedback on a legal writing draft (memo, brief, paper, exam essay) — organization, analysis depth, clarity, citation form. NEVER rewrites the draft. Use when the user says "feedback on my memo", "read my draft", or "critique my brief".
draft
anthropics/claude-for-legal
First draft of a common clinic document — practice-area templates (asylum applications, eviction answers, protective order petitions, demand letters), jurisdiction-aware formatting, explicitly a starting point requiring student analysis and attorney review. Use when a student needs a first draft of a motion, letter, petition, declaration, or other clinic document.
flashcards
anthropics/claude-for-legal
Generate or drill flashcards for black-letter memorization — Leitner-style buckets, per-subject markdown storage, drill mode with self-assessment. Use when the user says "drill flashcards", "make flashcards from", "quiz me on cards", or wants to memorize rules.
saas-msa-review
anthropics/claude-for-legal
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
review
anthropics/claude-for-legal
Review a vendor agreement, NDA, or SaaS subscription against your playbook. Identifies the agreement structure from titles, routes to the right review skill (vendor-agreement-review, nda-review, saas-msa-review), and integrates the output into a single memo. Use when the user says "review this contract", "check this MSA", "is this NDA okay", "look at this SaaS agreement", or attaches an inbound agreement for review.
policy-monitor
anthropics/claude-for-legal
Keep the privacy policy current with practice. Two modes: weekly sweep of saved PIAs, DPA reviews, and triage results to find policy drift; or direct query for a proposed new practice. Use when the user asks "does our policy cover this", "we want to start doing X — does the policy need updating", "run the policy monitor", "policy sweep", or wants to find where the privacy policy no longer matches what the team actually does.
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.