publish

Converts brain pages into self-contained password-protected HTML files with AES-256-GCM encryption.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill publish-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/plugin/skills/publish
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill publish-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sharing private knowledge-base pages with external people normally risks leaking internal metadata, source citations, and cross-links. This Skill publishes brain pages as self-contained HTML documents with all private data stripped and optional client-side encryption, so content can leave the brain safely. ## Core Features & Use Cases - Privacy-Stripped HTML Export: Automatically removes YAML frontmatter, source citations, confirmation numbers, internal cross-links, and timeline sections before publishing. - Client-Side Encryption: Protects pages with AES-256-GCM and PBKDF2 key derivation, decrypted in the browser via the Web Crypto API with no server required. - Flexible Sharing Workflows: Share the HTML file directly, upload to cloud storage with expiring signed URLs, or host on static platforms like Netlify, S3, or GitHub Pages. - Use Case: You need to send a deal memo on a company to an external investor. Publish the page with an auto-generated password, share the HTML file over email, and send the password through a separate channel. ## Quick Start Ask the agent to publish a brain page as a password-protected shareable HTML file, for example by saying "publish the Acme deal analysis page with a password so I can share it externally".

Frequently Asked Questions about publish

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

FAQPage Schema
How do I share a brain page as a password-protected HTML file?

Run gbrain publish with the page path and the --password flag to generate an encrypted, self-contained HTML file. If no password is given, one is auto-generated; share the file and password through separate channels.

What private data gets stripped when publishing a page?

The publish command removes YAML frontmatter, source citations, confirmation numbers, internal brain cross-links, timeline sections, and see-also lines. External https URLs and all other content are preserved in the output.

How does the password protection work without a server?

Encryption uses AES-256-GCM with PBKDF2 key derivation at 100K iterations, and decryption happens entirely client-side in the browser via the Web Crypto API. The published HTML contains only ciphertext, so no server-side authentication is needed.

Can I host a published page on Netlify, S3, or GitHub Pages?

Yes, the output is a fully self-contained HTML file with no external dependencies, so it works on any static hosting service. Password-protected files decrypt client-side, and you can also upload to cloud storage and distribute expiring signed URLs.

How do I revoke access to a published page?

Delete the HTML file from wherever it is hosted. Signed URLs expire automatically after one hour, and for static hosting you simply remove the file from the host to cut off access.