Use when running demo recordings, diagnosing recording failures, or regenerating GIFs from existing MP4s. Covers the Docker + VHS + ffmpeg pipeline. --- # VHS Demo Recording Use this skill to run, debug, or regenerate gh-infra demo GIF recordings. ## When To Use - Running `make demo` or `docs/tapes/vhs.sh` directly - Diagnosing why a recording failed or produced a 0-byte GIF - Regenerating GIFs from existing MP4s without re-recording - Understanding the recording pipeline ## Prerequisites - Docker must be running - Go toolchain (for cross-compiling the Linux binary) ## Pipeline ```text make demo 1. go build -o docs/tapes/.gh-infra (GOOS=linux GOARCH=amd64) 2. docs/tapes/vhs.sh a. docker build → gh-infra-vhs image (VHS + vim) b. For each *.tape in parallel: docker run --memory=1g --cpus=2 → produces .mp4 c. For each .mp4 sequentially: docker run jrottenberg/ffmpeg:7-alpine → produces .gif 3. Copy GIFs to docs/public/ 4. Clean up .gh-infra binary ``` ## Why MP4 → GIF Instead of Direct GIF VHS's built-in GIF output is unreliable when multiple containers run in parallel on macOS. The workaround is to output MP4 only from VHS, then convert to GIF via ffmpeg with high-quality settings (lanczos scaling, sierra2_4a dithering, 256 colors). ## Key Files | File | Role | |------|------| | `docs/tapes/vhs.sh` | Orchestrator: parallel recording + sequential GIF conversion | | `docs/tapes/Dockerfile` | `ghcr.io/charmbracelet/vhs` + vim | | `docs/tapes/*.tape` | VHS scenario files | | `docs/tapes/setup*.sh` | Per-demo setup scripts (mock data, gh wrapper) | | `docs/tapes/mock-gh` | Generic mock for `gh` CLI | | `docs/tapes/.gh-infra` | Cross-compiled Linux binary (ephemeral) | ## Output Locations - Raw recordings: `docs/tapes/*.mp4` and `docs/tapes/*.gif` - Published assets: `docs/public/demo*.gif` (copied by Makefile) ## Environment Variables `make demo` forwards `DEMO_ENV` variables into Docker via `-e` flags. Use this to pass environment overrides (e.g. `GH_INFRA_OUTPUT`) into
- 📁 examples/
- 📁 references/
- 📁 validation/
- 📄 README.md
- 📄 SKILL.md
- 📄 TROUBLESHOOTING.md
Use SwarmVault when the user needs a local-first knowledge vault that writes durable markdown, graph, search, dashboard, review, and MCP artifacts to disk from books, notes, transcripts, exports, datasets, slide decks, files, URLs, code, and recurring source workflows.
Update version number and license date for iloom releases. Updates LICENSE and README.md dates, then runs pnpm version.
Periodic progress-tracking re-run of the c059212d epistemic-protocols audit. Surveys state of audit-derived GitHub issues (#237-#241) and Deterministic Queue items (DQ1-DQ8) via gh CLI, traces commit activity in audit scope files (Track Alpha + Track Beta), scans for emergent audit targets in newly opened issues, and produces a progress report at docs/audit-delta-YYYY-MM-DD.md. Invoke this skill whenever you want to check 'how much of the previous epistemic audit is resolved', 'track audit issue status', 'see what changed in the audit scope since the last run', 'find new audit items', or run /audit-delta. Invoke on demand for weekly-to-monthly audit progress checks. This is a lightweight delta tracker, not a fresh ensemble re-audit.
Ask any question about Claude Code features — setup, best practices, automation, models, plugins, MCP, configuration, and more. Reads relevant reference docs to give accurate, detailed answers.
Add "Open in molab" badge(s) linking to marimo notebooks. Works with READMEs, docs, websites, or any markdown/HTML target.
End-to-end pipeline for publishing Claude Code lab meetings. Automatically finds/creates Fathom transcript, downloads video, uploads to YouTube, generates fact-checked Russian summary, creates MDX documentation, and pushes to agency-docs for Vercel deployment. Single invocation replaces 5+ manual steps.
- 📁 agents/
- 📁 assets/
- 📁 references/
- 📄 license.txt
- 📄 SKILL.md
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends agent capabilities with specialized knowledge, workflows, or tool integrations.
Web search using the Brave Search CLI (`bx`). Use for ALL web search requests — including "search for", "look up", "find", "what is", "how do I", "google this", and any request needing current or external information. Prefer this over the built-in web_search tool whenever bx is available. Also use for: documentation lookup, troubleshooting research, RAG grounding, news, images, videos, local places, and AI-synthesized answers.
Solve problems using knowledge base insights - extracts search terms, runs parallel KB queries, synthesizes advice grounded in your own frameworks
- 📄 rules-reference.md
- 📄 SKILL.md
Format and lint markdown and MDX files using markdownlint with comprehensive rule knowledge for automated and manual fixes. Use when working with .md or .mdx files, formatting documentation, linting markdown/MDX, or when user mentions markdown issues, formatting problems, or documentation standards.
- 📁 examples/
- 📁 reference/
- 📄 SKILL.md
Develop and maintain the SimpleLLMFunc framework itself. Use when changing framework internals, tests, docs, specs, runtime primitives, decorator behavior, tool plumbing, event streams, PyRepl integration, or contributor-facing project structure and conventions.
