publish

Encrypt brain pages into self-contained HTML with AES-256-GCM and PBKDF2.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/weiping/gbrain-cn --skill publish-weiping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/weiping/gbrain-cn/tree/main/skills/publish
Command: npx skills add https://github.com/weiping/gbrain-cn --skill publish-weiping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing sensitive brain content for external sharing can be risky and time-consuming; this Skill safely turns an internal page into a self-contained, optionally password-protected HTML artifact without using any LLM calls.

Core Features & Use Cases

  • Deterministic HTML publishing: Generates a beautiful standalone HTML document from a brain page using the deterministic publish workflow.
  • Client-side password protection: Supports optional AES-256-GCM encryption with PBKDF2 key derivation, so the server never needs to handle secrets.
  • Privacy-preserving stripping: Removes internal metadata, source citations, confirmation numbers, cross-links, and raw timeline evidence so only safe content is shared.
  • Sharing-ready outputs: Produces local files suitable for email, Slack, Airdrop, or uploading to static hosting/cloud storage with signed URLs.

Quick Start

Run gbrain publish on the brain markdown page you want to share, enabling password protection and choosing an output HTML file.

Frequently Asked Questions about publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share brain pages as password-protected HTML?

To share brain pages as password-protected HTML, run the publish workflow on your markdown page. It generates a self-contained HTML file using AES-256-GCM encryption with PBKDF2-derived keys, ensuring the server never handles your password.

What internal metadata is stripped when publishing a brain page to HTML?

When publishing a brain page to HTML, the workflow strips internal metadata including source citations, frontmatter, confirmation numbers, cross-links, and raw timeline evidence. This ensures only safe, external-facing content is shared.

Does client-side encryption leave any plaintext in the published HTML output?

No, client-side encryption using AES-256-GCM never includes plaintext inside the encrypted HTML output. The publish workflow produces fully self-contained files where content is securely locked using PBKDF2-derived keys.

What's the best way to securely share trip plans and research externally?

The best way to securely share trip plans and research is using the deterministic publish workflow. It converts internal pages into standalone, encrypted HTML artifacts suitable for email, Slack, Airdrop, or static hosting.

Can I publish a brain page to HTML without an internet connection?

Yes, you can publish a brain page to HTML without an internet connection. The process uses no LLM calls and operates deterministically to generate local files, applying client-side crypto for optional password protection.