second-brain-publish

Solid

Prepare 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.

AI & Automation 46 stars 7 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
62
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 1. **List the opt-in set.** Every page marked for publication. 2. **Follow their links.** A published page linking to a private one either leaks the title or produces a dead link. Report both. 3. **Scan for anything that should never ship:** credentials, other people's private information, confidential work, personal detail in examples. 4. **Check the frontmatter** for fields not meant to be public, such as confidence labels or private source paths. 5. **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.

Details

Author
undefined-ui
Repository
undefined-ui/second-brain-os
Created
3 days ago
Last Updated
today
Language
HTML
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

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.

46 Updated today
undefined-ui
Data & Documents Listed

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.

0 Updated 1 weeks ago
CUHK-Business-School-AI-Hub
AI & Automation Listed

publish-readiness

Use before making a private repository public, before the first push of a new public repo, or when the user asks "is this safe to publish", "check for leaks", or wants a pre-publication scan. Also use after discovering identifying content already leaked into a public repo's history.

4 Updated 1 weeks ago
escoffier-labs