publish

Convert Markdown brain pages into password-protected HTML documents with AES-256-GCM encryption.

2|1|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/bish-x/bx-gbrain --skill publish-bish-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/bish-x/bx-gbrain/tree/main/skills/publish
Command: npx skills add https://github.com/bish-x/bx-gbrain --skill publish-bish-x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the problem of securely sharing brain pages, allowing users to convert their brain pages into password-protected HTML documents without any server-side involvement or language model calls.

Core Features & Use Cases

  • Password-Protected Sharing: Convert brain pages into self-contained HTML documents with optional password protection.
  • Serverless Operation: No server needed, all operations are performed locally.
  • Use Case: Ideal for sharing sensitive information, such as deal memos, briefings, or research notes with external parties, ensuring privacy and control over access.

Quick Start

To publish a brain page as a password-protected HTML document, use the command: gbrain publish brain/path/to/page.md --password "yourPassword"

Frequently Asked Questions about publish

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

FAQPage Schema
How do I convert Markdown brain pages to password-protected HTML?

To convert Markdown brain pages to password-protected HTML, use the publish command with a specified password. This generates self-contained HTML documents secured with client-side AES-256-GCM encryption for safe sharing.

Can I securely share Markdown documents without a server?

You can securely share Markdown documents without a server by converting them into self-contained HTML files. All operations are performed locally using client-side encryption, eliminating external server dependencies.

What is client-side HTML encryption for secure document sharing?

Client-side HTML encryption secures your documents by applying AES-256-GCM encryption locally before generating a self-contained HTML file. This ensures sensitive information remains protected without requiring server-side processing.

Does AES-256-GCM encryption work for sharing sensitive research notes?

AES-256-GCM encryption works effectively for sharing sensitive research notes by embedding the encryption directly within the generated HTML document. Recipients must enter the correct password to decrypt and view the content locally.

Do I need external dependencies to encrypt Markdown as HTML?

No external dependencies are needed to encrypt Markdown as HTML. The process requires only local execution, converting brain pages into encrypted HTML documents entirely on your machine without server-side processing.

What are the limitations of serverless HTML encryption for brain pages?

The main limitation of serverless HTML encryption is that it requires local execution to convert Markdown brain pages into secured HTML documents. Additionally, recipients must manually enter the password to access the encrypted content.