📡 Spellbook

A curated library of agent “spells.” A static, offline, read-only reference of well-crafted prompt and workflow recipes you can browse, search, and copy.

Install & availability

Available now. Install from the Companion Hub App Store. Verified on the test fleet: the published image pulls, starts, serves its web UI, and survives a container restart.


Hub App Store	Search Spellbook → Install
Container image	`ghcr.io/companionintelligence/ci-spellbook:latest` (public)
Web UI port	`5500`
Architecture	`linux/amd64` and `linux/arm64` (multi-arch)
Network / auth / env	None — no outbound calls, no auth, no environment config

Overview

Spellbook is a static, read-only library of 13 curated “spell” cards — structured prompt and workflow recipes for getting consistent, high-quality outputs from local LLMs. Each card is authored in markdown and rendered in the browser. You can search the library with client-side fuzzy search and flip a card to expand its full content.

It is a reference you read and copy from, not a runtime. There is no backend, no scheduler, and no agent-execution engine in this app.

Current capabilities

What Spellbook does today, as shipped:

13 curated spell cards rendered from bundled markdown
Client-side fuzzy search across the library
Flip-to-expand cards to read the full recipe
Fully offline — no network calls, no auth, no environment variables

Strong privacy story: Spellbook makes zero outbound network calls and stores nothing. Everything is served as static content from the container. It is safe to run on a fully air-gapped Hub.

Spellbook does not run spells, schedule them, trigger on Hub events, expose MCP tools, or connect to an LLM. There is no trigger, cron, webhook, or MCP code and no backend in this app. The recipes are meant to be read and copied into whatever runtime you use.

Planned / roadmap

Described in the broader product vision but not part of this app today:

Executing spells directly against a connected LLM
Scheduling / triggering spells on a cron or Hub events
Exposing spells as MCP tools to connected agents
Importing community spells from the CI Marketplace
Per-spell version history with rollback

Use Cases

Browse vetted prompt recipes for briefings, research, meeting prep, and code review
Copy a structured prompt into your own agent or chat tool
Keep a consistent, offline reference of “how to ask” for common tasks

Spell Format

Each spell card is plain markdown. A typical card documents what the spell is for, the prompt or steps to use, and any variables to fill in. For example, a daily-briefing card might read:


# Daily Briefing
 
Summarize my notes from the past day, check today's tasks, and flag
anything that needs attention.
 
## Prompt
 
Given the following notes from the past {{days_back}} day(s):
{{notes}}
 
Write a concise briefing covering:
1. Key activities and conversations
2. Open tasks or follow-ups
3. Anything that needs attention today

You copy the recipe out and run it wherever you run your LLM.

Authoring new spells

Spellbook is built from bundled content, so adding a spell means rebuilding the image:

Add a markdown file

Place your new spell’s markdown under public/markdown/ in the Spellbook repository .

Register the card

Add an entry for your file in CARD_CONFIGS so it appears in the library.

Rebuild and install

Rebuild the container image and install your custom build on the Hub.

Setup

Install from Hub

Search for Spellbook in the Hub app store and install.

Open Spellbook

Navigate to http://spellbook.ci.localhost. The 13 spell cards load immediately — no configuration, login, or LLM connection required.

Usage

Browsing and Searching

The library opens to the full set of cards. Use the search box for client-side fuzzy search by title or content.

Reading a Spell

Click a card to flip it and reveal the full markdown recipe. Copy the prompt or steps into your own LLM tool.

Troubleshooting

Looking for a “Run” button Spellbook is a read-only library — it does not execute spells. Copy the recipe into your own agent or chat tool to run it.

Scheduled / triggered spells not firing There is no scheduler or trigger system in this app. Automation is on the roadmap, not in this build.