Skip to content

undefined-ui/second-brain-os / skills/second-brain-write

second-brain-write

Unverified

Draft from the vault: outline from concept pages, keep citations to the user's own sources, and surface where their material disagrees. Use this skill when the user wants to write an article, post, essay or newsletter based on what they have collected, or asks what they could write about a topic. Do NOT use for research reports, for writing with no grounding in the vault, or for editing text the user wrote themselves unless asked.

Write from the vault

The research is already done, cited and connected. What is left is the argument, and that is the part the user should keep.

Core rule

Assemble structure and evidence. Do not hand back finished prose as if it were theirs.

Workflow

  1. Find the relevant concept pages and say what they collectively argue.
  2. Surface the disagreements. These are where the user has something to say that is not the consensus view, and they are the most useful part of the outline.
  3. Build the outline from pages, each point tied to the page behind it.
  4. Mark the weak points: claims resting on one source, self-reported figures, anything the vault flags as unverified.
  5. Draft only if asked, and say plainly that the phrasing is a first pass to be rewritten in their voice.
  6. Offer to ingest the finished piece back as a source once published.

Output format

Angle: <what this piece argues that the sources do not individually>
Outline:
  1. <point> - [[page]], [[page]]
Weak points: <claims with thin support>
Missing: <what would strengthen it>

Calibration

If every point in the outline comes from one page, this is a summary of that page, not an article. Say so.

Never introduce a specific number or quote that has no source page behind it. That is the failure mode of writing with a model, and in a cited piece it is the one that costs the most.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall