Skip to content
Back to skills

Second Brain Publish

ASecurity

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.

  • 809 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 19, 2026
ai-agentsgit

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add undefined-ui/second-brain-os --skill second-brain-publish --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Second Brain Publish?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Second Brain Publish
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/undefined-ui-second-brain-publish/badge)](https://www.skillsdirectory.com/skills/undefined-ui-second-brain-publish)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: second-brain-publish
description: >-
  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.
---

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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.