Skip to content

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

second-brain-write

Verified

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.

FileKindSize
SKILL.mdskill md1.9 KB
---
name: second-brain-write
description: >-
  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: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall