wrighter-offline-html-sealed

Create sealed Wrighter HTML artifacts with per-principal access control and delivery manifests.

7|12|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/borealBytes/my-farm-advisor --skill wrighter-offline-html-sealed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrighter-offline-html-sealed
Source: https://github.com/borealBytes/my-farm-advisor/tree/main/skills/superior-byte-works-wrighter/delivery/offline-html-sealed
Command: npx skills add https://github.com/borealBytes/my-farm-advisor --skill wrighter-offline-html-sealed

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Fingerprinted, sealed delivery of Wrighter HTML artifacts enables per-recipient attribution, offline distribution, and controlled access.

Core Features & Use Cases

  • Frontmatter-driven configuration supports delivery_id, fingerprint_id, principals, and protection levels
  • Seamless integration with offline-html-open to produce a sealed HTML artifact with a delivery manifest
  • Optional passphrase-based unlocking and principal-based exposure for secure workflows

Quick Start

Create a sealed offline HTML artifact from a Wrighter payload using the build process.

Frequently Asked Questions about wrighter-offline-html-sealed

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

FAQPage Schema
How do I fingerprint offline HTML artifacts for per-recipient attribution?

You can configure sealed offline HTML delivery using frontmatter fields such as delivery_id, fingerprint_id, principals, and protection levels to enforce per-principal access control.

What's the best way to configure per-principal access control for offline HTML delivery?

You can configure sealed offline HTML delivery using frontmatter fields such as delivery_id, fingerprint_id, principals, and protection levels to enforce per-principal access control.

Can I use passphrase-based unlocking for offline HTML content distribution?

You can create a sealed offline HTML artifact from a Wrighter payload by using the build process to integrate with offline-html-open and produce a delivery manifest.

How do I create a sealed offline HTML artifact from a Wrighter payload?

You can create a sealed offline HTML artifact from a Wrighter payload by using the build process to integrate with offline-html-open and produce a delivery manifest.

Does offline HTML sealed delivery work without an active internet connection?

Offline HTML sealed delivery is designed for offline operation, allowing you to distribute fingerprinted Wrighter artifacts to targeted recipients without requiring an active internet connection.

When do I need per-principal fingerprinting for offline HTML workflows?

You need per-principal fingerprinting for offline HTML workflows when distributing Wrighter content requires individual recipient attribution, auditability across channels, and strict controlled access.