Skip to content
cccskills
FreePublished on GitHub

second-brain-write

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Audit an agent's context layout against the four places: system prompt, tools, history, tail. Use when the user asks to audit, review or fix their agent's context, prompt caching, token spend per turn, or CLAUDE.md / AGENTS.md layout. Read-only: reports findings and a fix list, changes nothing. Do NOT use for writing evals (evals-bootstrap) or for loop design (goal-test).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

Scaffold a first eval suite for an agent: mine real failures into cases, write behavioural checks over traces, and generate the runner. Use when the user wants evals, regression tests for an agent, a golden set, or asks how to know a prompt/model change did not break things. Do NOT use for a single task's done-check (goal-test) or for auditing context (context-audit).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

Find the decisions in a pipeline that do not need the expensive model and propose the gate for each: a rule, a classic classifier, or a small model, with fail-closed routing. Use when the user asks to cut model costs or latency, says the big model handles everything, or wants a triage / routing / filter layer in front of an agent. Analysis plus an optional baseline scaffold. Do NOT use for auditing context layout (context-audit) or for building eval suites (evals-bootstrap).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

Turn a vague task into a testable definition of done and generate an executable goal-test script for it, optionally with a bounded retry loop around a headless agent. Use when the user wants to run an agent in a loop, asks how to know when an agent task is finished, or says a goal like "improve X" needs to become checkable. Do NOT use for building eval suites over many cases — that is evals-bootstrap.

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

Audit an agent's harness against the four rings: containment, guides, sensors, permissions. Use when the user asks whether their agent setup is safe, wants a review of sandboxing / permissions / hooks / AGENTS.md guardrails, or asks what a bad session could break. Read-only: reports the blast radius and a hardening list, changes nothing. Do NOT use for context layout (context-audit) or cost routing (gate-check).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

Import a large archive into the vault in controlled batches: triage what is worth ingesting, process oldest first, checkpoint after every batch, and keep cost visible. Use this skill whenever the user wants to import years of bookmarks, an export from another notes app, a downloads folder, a chat history dump, or says "backfill", "bulk import", "process my archive". Do NOT use for ingesting one or a few new sources, which is second-brain-ingest.

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

See all skills by undefined-ui

Report a problem with this skill