ketchup

Ketchup on Everything.
A Claude Code skill that generates in-depth technical research reports
shaped for your professional background.

Install · Quick Start · Flags · Plugins · Config

---

Install

Step 1: Add the marketplace (one-time setup):

/plugin marketplace add RCellar/ketchup

Step 2: Install the plugin:

/plugin install ketchup@rcellar-ketchup

Then run /reload-plugins to activate. Skills are namespaced as /ketchup:<skill>.

Quick Start

Set your perspective, then research anything:

# Tell ketchup who you are
/ketchup --occ "Windows Systems Engineer"

# Research a topic — shaped for you
/ketchup --tgt "SELinux Administration"

That's it. Ketchup decomposes the topic into facets, dispatches parallel research agents, and synthesizes an Obsidian-ready report that explains SELinux through the lens of Windows security concepts you already know — GPO, integrity levels, ACLs, Event Viewer, and more.

One-liner with everything:

/ketchup --occ "Windows Systems Engineer" --tgt "SELinux Administration" --plugin "Context7" --time 6

This tells ketchup: "I'm a Windows sysadmin who hasn't been deep in the weeds for 6 years. Use Context7 docs. Ketchup me on SELinux."

Flags

Flag	What it does	Example
--occ	Your occupation — shapes vocabulary, analogies, assumed knowledge	--occ "DBA"
--tgt	Topic to research	--tgt "Kubernetes"
--plugin	MCP data sources for pre-fetch (comma-separated)	--plugin "Context7"
--time	Years since your last deep engagement	--time 6
--registry	Manage plugins: list, add, remove	--registry list
--fmt	Output format: obsidian (default) or notebook	--fmt notebook
--kernel	Kernelspec for notebook code cells: python or bash	--kernel bash
--annotate	Reprocess a ketchup notebook for inline queries	--annotate ./report.ipynb

Jupyter Notebook Output

Ketchup can output directly to Jupyter notebooks with executable code cells — ideal for hands-on learning topics.

/ketchup --occ "Linux Enthusiast" --tgt "systemd Service Management" --fmt notebook --kernel bash

What changes from Obsidian output:

Obsidian	Notebook
YAML frontmatter	metadata.ketchup JSON namespace
> [!tip] callouts	HTML <div class="alert"> divs
[[wikilinks]]	Standard markdown links
Fenced code blocks	Executable code cells (when language matches --kernel)
Static document	Runnable, annotatable document

Annotating Notebooks

After generating a notebook, you can ask follow-up questions directly inside it. Add a markdown cell anywhere with %%ketchup on the first line:

%%ketchup
Expand on how SELinux booleans work — give me practical examples.

Then run:

/ketchup --annotate ./my-report.ipynb

Ketchup reads the perspective, plugins, and topic from the notebook's metadata (no need to re-specify --occ), dispatches a sonnet agent for each query, and inserts the response directly after the query cell.

Annotation index: Each processed query is replaced with a compact marker (*[Annotation #1](#ketchup-annotation-index)*) and the full query text is preserved in cell metadata. An annotation index table is appended to the end of the notebook, rebuilt on every --annotate run.

Idempotency: Answered queries are tagged ketchup:query-answered and skipped on re-runs. To re-ask, replace the marker with a new %%ketchup cell.

How It Works

/ketchup --occ "Frontend Dev" --tgt "PostgreSQL" --plugin "Context7"