undefined-ui/second-brain-os / skills/second-brain-publish
second-brain-publish
UnverifiedPrepare a subset of the vault for publishing: check opt-in flags, find private material, and report what would leak through links before anything is exported. Use this skill when the user wants to publish notes as a site or digital garden, asks what is safe to make public, or is setting up an export. Do NOT use for exporting a single document, or for running the publishing tool itself.
Prepare to publish
Once something is crawled, it is out. Every check here is cheap; the failure it prevents is permanent.
Core rule
Explicit opt-in only. A page publishes because it says publish: true, never
because nothing excluded it.
Workflow
- List the opt-in set. Every page marked for publication.
- Follow their links. A published page linking to a private one either leaks the title or produces a dead link. Report both.
- Scan for anything that should never ship: credentials, other people's private information, confidential work, personal detail in examples.
- Check the frontmatter for fields not meant to be public, such as confidence labels or private source paths.
- Report, do not export. The user runs the build.
Output format
Publishable: <n> pages
Links to unpublished pages: <n>
[[public page]] -> [[private page]]
Flagged content: <list with reasons>
Frontmatter to strip: <fields>
Verdict: <safe to build | fix these first>
Calibration
Err toward flagging. A false positive costs the user ten seconds; a miss is permanent.
If the user asks to publish the whole vault, ask what they intend to do about the private material rather than proceeding.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 463k | Updated | Claude CodeCodex | Verified | Install |
| 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: 463k | Updated | Claude CodeCodex | Verified | Install |
| 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: 195k | Updated | Claude CodeCodex | Verified | Install |
| 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: 195k | Updated | Claude CodeCodex | Verified | Install |