publish

Publish brain pages as self-contained, password-protected HTML files.

Updated May 16, 2026
One-click install
npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill publish-morris-utrust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/Morris-UTRUST/GBrain-knowledge/tree/main/skills/publish
Command: npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill publish-morris-utrust

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publish brain pages as beautiful, self-contained HTML documents that can be shared without exposing internal brain data, with optional client-side password protection.

Core Features & Use Cases

  • Self-contained HTML output that requires no server.
  • Client-side AES-256-GCM encryption with PBKDF2 key derivation; default is encrypted.
  • Automatically strips private metadata, citations, and internal references before sharing.
  • Use Case: securely distribute a deal memo or team briefing to external collaborators.

Quick Start

Publish a brain page to produce a password-protected, self-contained HTML file.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I publish brain content as a standalone HTML file?

You can publish brain content as a self-contained HTML file by stripping private metadata and exporting the page, which requires no server to view. The output is a portable document for secure sharing.

Can I password-protect an HTML file using client-side AES-256-GCM encryption?

Yes, this HTML publishing process applies client-side AES-256-GCM encryption with PBKDF2 key derivation by default. It ensures your shared documents are password-protected and securely encrypted before distribution.

Does publishing brain pages remove private metadata and internal references?

Yes, the publishing mechanism automatically strips private metadata, citations, and internal references from brain pages. This prevents exposing internal brain data when sharing analyses or memos with external collaborators.

What is the best way to securely share a deal memo as an independent HTML document?

The best way to share a deal memo securely is to publish it as a self-contained, password-protected HTML file. This approach bundles the content and encryption into a single document requiring no server.

Do I need a server to view a password-protected HTML document generated from brain content?

No, you do not need a server to view the generated HTML document. The output is completely self-contained, utilizing client-side decryption so recipients can open and view the content directly in a browser.

When should I not use self-contained HTML for sharing brain content?

You should not use self-contained HTML if recipients lack the password or a modern browser for client-side AES-256-GCM decryption. The encrypted file requires correct credentials to access any of the embedded content.