publish

Package brain content into self-contained HTML with AES-256-GCM encryption.

174|144|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/inbrainfun/inbrain --skill publish-inbrainfun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/inbrainfun/inbrain/tree/main/skills/publish
Command: npx skills add https://github.com/inbrainfun/inbrain --skill publish-inbrainfun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sharing brain pages without exposing internal metadata or requiring server-side hosting can be risky or cumbersome. This skill packages brain content into a self-contained, password-protected HTML file that can be safely distributed to external collaborators, with client-side encryption and no server dependencies.

Core Features & Use Cases

  • Self-contained HTML documents: no server required for viewing or sharing.
  • Client-side encryption: AES-256-GCM with PBKDF2 key derivation to protect content.
  • Privacy-first publishing: strips private YAML frontmatter, citations, and internal references while preserving external URLs.
  • Use Case: securely share research briefs, deal memos, or brain pages via a single link.

Quick Start

Run inbrain publish on a brain Markdown file with the --password flag to generate a self-contained, password-protected HTML page.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I share a markdown document as a self-contained HTML page with password protection?

To share a markdown document as a self-contained HTML page with password protection, run the inbrain publish workflow with the --password flag. This packages your content into a standalone HTML file secured by client-side AES-256-GCM encryption, requiring no server-side hosting.

How does client-side password protection work for shared HTML files?

Client-side password protection for shared HTML files works by encrypting content directly in the browser using AES-256-GCM with PBKDF2 key derivation. The self-contained HTML document requires no server-side logic, ensuring secure offline viewing.

Can I strip private metadata from markdown when publishing to HTML?

Yes, you can strip private metadata from markdown when publishing to HTML. This workflow automatically removes private YAML frontmatter, citations, and internal references while preserving external URLs for safe external distribution.

Do I need a server to host a password-protected HTML page?

No, you do not need a server to host a password-protected HTML page. The publishing workflow outputs a deterministic, self-contained HTML document with client-side encryption, allowing secure distribution via a single file or link.

What is the best way to securely share research briefs without exposing internal references?

The best way to securely share research briefs without exposing internal references is packaging them into a self-contained HTML file. This strips internal metadata and applies AES-256-GCM encryption, ensuring safe distribution without server dependencies.