second-brain-publish
FeaturedPrepare 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.
Install
Quality Score: 89/100
Skill Content
Details
- Author
- undefined-ui
- Repository
- undefined-ui/second-brain-os
- Created
- 2 weeks ago
- Last Updated
- today
- Language
- HTML
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
publish
Analyze which documentation is safe to publish externally, detect information that would leak, and produce external-lens rewrite briefs. Use before publishing docs, opening a repository, or moving internal documentation to a public site.
second-brain-privacy
Audit the vault for material that should not be in it: credentials, other people's private information, confidential work, and anything the user would not want synced or backed up. Use this skill when the user asks about privacy, is about to share or sync the vault, has just imported chat history or meeting notes, or asks what is sensitive in their notes. Do NOT use to delete anything on your own, or as a substitute for the publishing check.
safe-to-publish
Decide whether teaching material is safe to put in front of people, and stop the marking scheme escaping. Use when a case, an answer key, a dataset, a handout or a whole site is about to become visible to students or colleagues, when someone asks whether a solution file could leak, or when a check "keeps getting ignored". Covers putting a deterministic gate between authored and published that refuses rather than warns, exporting by whitelist rather than filter, planting sentinels in everything that must not escape, and the version of both patterns for material that is just files rather than an application.