plugins/midpage/skills/draft-long-form-memo/SKILL.md
Writes a formal objective legal research memo (Questions Presented, Brief Answers, Facts, IRAC Discussion, Conclusion) as a .docx. Use to "draft a research memo on whether…" Predicts, never advocates.
npx skillsauth add openai/plugins draft-long-form-memoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Produce the thorough, objective memorandum a litigator hands a partner: it predicts, it does
not advocate. The test for every sentence: would you write it the same way no matter which
side retained you? Read the shared guides first — references/litigation-writing.md (the
craft; same point-first discipline, neutral verbs), references/citations.md (how every cite
links), and references/legal-docx.md. The research method is below — the memo is only as
good as the research under it.
All law comes from the Midpage tools this session. search finds candidates; findInOpinion
previews; analyzeOpinion is what permits a citation — no case is cited without it.
jurisdictionType, circuits/courts/states, dates). Binding authority first,
persuasive labeled as such. If you filter publishStatus, run a parallel unknown query
too (California: default published plus unknown).highlights (previews only — never quote them) and treatment; use
findInOpinion as the free double-click before spending an analyzeOpinion call.analyzeOpinion the strongest case on each
side. The prediction is only honest if the contrary line got the same effort.analyzeOpinion gate, on every case cited. Pass a question naming the exact
element. Check doesNotAddress first — if your point is listed, the case doesn't stand for
it. Build sentences from supportedPropositions (verified quote + deeplinkURL); rank by
centrality (lead with holdings, never sell background as one); carry scope qualifiers;
never present a concurrence/dissent (opinionSection) as the court's holding; surface
negative treatment honestly.MEMORANDUM, then To / From / Date / Re: lines. From is always
"Midpage Legal Research" — never an AI assistant's name. Front matter is single-spaced, no
first-line indent (the body is double-spaced).h1 headings: state the rule with linked
controlling authority, apply it to the facts, then give the contrary or competing authority
its fair statement — distinguish it, weigh it, note negative treatment honestly — and
resolve with a predictive conclusion. Use predictive verbs ("a court would likely hold"),
never advocacy verbs ("plaintiff plainly fails").Per references/legal-docx.md, memo profile, double-spaced:
const B = D.builders("memo", { lineSpacing: 480 });
// front matter lines: B.p([...], { lineSpacing: 240, firstLineIndent: 0 })
// Questions Presented: B.numbered(q, { instance: 1 })
// Brief Answers: B.numbered(a, { instance: 2 }) // distinct instance → restarts at 1
Questions and Brief Answers are real numbered lists (hanging indents, wrapped lines aligned under the text) — never a literal "1." plus a tab.
draft-brief's job.analyzeOpinion this session; search/findInOpinion alone are not enough. No invented
authority, ever. Respect doesNotAddress, scope, centrality, and opinionSection;
surface negative treatment.references/citations.md; short
verbatim quotes woven into prose, no block quotes, no short cites.development
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
data-ai
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
tools
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
development
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.