publish

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

45|11|Updated Mar 17, 2026

Search Tags:#html #publishing #security #encryption #privacy #knowledge-sharing

Ready to run

npx skills add https://github.com/beyonai/ByClaw --skill publish-beyonai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/beyonai/ByClaw/tree/main/middleware/openclaw/skills/gbrain/references/publish
Command: npx skills add https://github.com/beyonai/ByClaw --skill publish-beyonai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the challenge of sharing internal knowledge base content with external parties without exposing sensitive metadata, internal links, or requiring the recipient to have access to your internal systems.

Core Features & Use Cases

Self-Contained HTML Generation: Converts markdown pages into beautiful, standalone HTML files that require no external dependencies or servers.
Client-Side Encryption: Protects shared content using AES-256-GCM encryption, ensuring that sensitive information remains private even when hosted on third-party platforms.
Automatic Sanitization: Automatically strips internal metadata, source citations, and private cross-links before publishing to prevent accidental data leakage.

Quick Start

Use the publish skill to create a password-protected shareable link for the brain page located at brain/companies/acme.md.

Frequently Asked Questions about publish

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

FAQPage Schema

How do I securely share markdown brain pages as encrypted HTML?▼

The publish skill generates self-contained, password-protected HTML documents from internal markdown pages. It uses AES-256-GCM encryption and strips sensitive metadata and cross-links to ensure secure external sharing without server-side authentication.

How does client-side AES-256-GCM encryption work for HTML publishing?▼

AES-256-GCM encryption secures shared content directly within the generated HTML file. Recipients must enter a password to decrypt and view the data, ensuring privacy without requiring server-side authentication or external database access.

Can I share internal knowledge base content without exposing private cross-links?▼

Yes, the publish skill automatically sanitizes content by stripping internal metadata, source citations, and private cross-links before generating the HTML. This prevents accidental data leakage when sharing internal knowledge base content externally.

Does the recipient need an internal account to view a shared encrypted HTML file?▼

No, recipients do not need an internal account or server-side authentication to view the shared HTML file. The generated document is completely self-contained, requiring no external dependencies, servers, or database access for the recipient to view it.

What is stripped out during automatic sanitization for external knowledge sharing?▼

During automatic sanitization, internal metadata, source citations, and private cross-links are stripped from the markdown content. This prevents accidental data leakage when converting internal brain pages into standalone HTML files for external sharing.