introduce

Automate EarlBear artifact catalog lifecycle from HTML import to GitHub Pages publishing.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/EarlBear/homebrew-tap --skill introduce-earlbear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: introduce
Source: https://github.com/EarlBear/homebrew-tap/tree/main/plugins-bundle/artifact-manager/skills/introduce
Command: npx skills add https://github.com/EarlBear/homebrew-tap --skill introduce-earlbear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The artifact-manager plugin streamlines the end-to-end lifecycle of the EarlBear sites catalog — importing HTML artifacts, managing Supabase previews, publishing the encrypted dist to GitHub Pages, and rotating the StatiCrypt password.

Core Features & Use Cases

  • Import artifacts into claude-artifacts/, create a Supabase catalog entry, and wire it into the make dist workflow.
  • Manage working-backwards previews (code/email/sequence/personas/catalog) in Supabase for each artifact.
  • Publish the encrypted distribution to GitHub Pages, including the full publish flow.
  • Rotate access credentials by cycling StatiCrypt passwords and rebroadcast to recipients.

Quick Start

Use the import-artifact flow to add a new artifact and wire it into the make dist and publish steps.

Frequently Asked Questions about introduce

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

FAQPage Schema
How do I automate artifact catalog lifecycle management for static sites?

Automating artifact catalog lifecycle management is handled by importing HTML artifacts, generating Supabase previews, encrypting the dist output with StatiCrypt, and publishing to GitHub Pages. Credentials are rotated across the workflow automatically.

How do I publish encrypted static HTML to GitHub Pages using StatiCrypt?

Publishing encrypted static HTML to GitHub Pages with StatiCrypt involves importing artifacts, building the dist output, applying password-based encryption, and pushing the encrypted distribution through the full publish flow.

Can I manage Supabase previews for HTML artifacts without manual database work?

Managing Supabase previews for HTML artifacts is automated by creating catalog entries and wiring working-backwards previews covering code, email, sequence, personas, and catalog data directly into the workflow.

What is the best way to rotate StatiCrypt passwords for published GitHub Pages sites?

Rotating StatiCrypt passwords for published GitHub Pages sites is accomplished by cycling the access credential and rebroadcasting the updated password to recipients as part of the automated artifact workflow.

Do I need Supabase and GitHub Pages configured before importing HTML artifacts?

Supabase and GitHub Pages are required to support the full artifact lifecycle, as the workflow creates Supabase catalog entries and publishes the encrypted distribution to GitHub Pages during the import process.