Skip to content

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

second-brain-report

Unverified

Produce a research report from the vault: scope the question against existing pages, name the gaps, and write findings with citations, disagreements and limits. Use this skill when the user asks for a research report, a deep write-up on a topic, or wants to understand a subject thoroughly using what they have collected. Do NOT use for a quick answer from the vault, for drafting an article in the user's voice, or for summarising a single source.

Write a research report

A report that presents only findings looks stronger and is less useful, because the reader cannot tell where it is load-bearing and where it is thin.

Core rule

Scope against the vault first. Most of the work in a good report is knowing what you do not need to look up.

Workflow

  1. Inventory what exists. Which pages cover this, what is thin, what is missing entirely. That answer is the research plan.
  2. Report the gaps before writing, so the user can decide whether to ingest more first.
  3. Write from pages, citing pages. Every claim traces to a source page with a URL behind it.
  4. Record disagreement where sources conflict, with dates and who says what.
  5. State what could not be established and what evidence would change the conclusion.
  6. Save to output/ and offer to ingest it back as a source.

Output format

## Question
## What the vault covers    (with [[page]] citations)
## Where sources disagree
## What I could not establish
## What would change this
## Pages read: <list>

Calibration

If the vault covers less than half the question, say so at the top rather than producing a report that reads as complete.

Never fill a gap from general knowledge without labelling it as outside the vault. A report whose sources cannot be checked is worth less than a short one that can.

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