Jacob's plugin marketplace
Claude plugin marketplace for the team. Current plugins:
| Plugin | What it does |
|---|---|
content-engine | Unified LinkedIn content engine — one pipeline for ABM, TOFU, MOFU, and BOFU posts. Picks viral formats from a selectable library (Virio corpus or Millie's curated list), builds client context, proposes ranked angles, drafts de-slopped QA-gated candidates. Requires the Virio MCP connector. |
copy-post | Example-driven drafting: reverse-engineer any LinkedIn post into a style spec, then draft a style-matched, funnel-classified, ICP-personalized post. Use when you have a post to imitate; use content-engine when you want a format from the library. |
watt | Watt voice + brand + signal stories. /watt:post drafts in the founder voice and de-slops; /watt:deslop strips AI tells from any copy; design skill applies the Watt design system; signal-story turns Watt audience data into branded PDF reports. Merges the former watt-voice / watt-design / watt-signal-story. |
gtm-strategy-suite | Client-ready GTM strategy docs: 16-section template with specialist skills for segmentation, pricing economics, sales-motion math, conjoint analysis, and sourced benchmarks (deterministic Python calculators, stdlib only). |
dm-master | LinkedIn outreach ghostwriting — profile analysis, tone read, register-matched connection notes / DMs / follow-ups / call asks. Never invents a profile detail. No dependencies. |
lets-get-curious | Ideation: turns a topic you don't care about into an angle worth writing, via 11 curiosity lenses + verified surprising facts. Hands off to watt or dm-master. Needs only web search. |
content-interview | Client content-intake pipeline: run the interview → build a deep emotional ICP avatar → mine the transcript into 20+ tagged post concepts → draft to hook-lever writing standards. Feeds content-engine. No dependencies. |
linkedin-strategy | LinkedIn performance advisor grounded in research on 226K posts — performance states, image/timing strategy, reaction mechanics, topic selection, 2026 feed mechanics. Answers "why is my engagement down" with findings, not vibes. |
wartime-advisor | Strategic work + leadership advisor grounded in Horowitz's Peacetime/Wartime CEO and Grove's inflection points, plus a talent 2x2. Direct, diagnoses before advising. No dependencies. |
systems-thinking | Systemic root-cause analysis via the Questions of a Systems Thinker and Causal Loop Diagrams. By Agile Pain Relief (CC BY-SA 4.0). |
Retired:
abm-engineandfunnel-enginewere folded intocontent-engine. If you have either installed, remove it and installcontent-engine.
Install in Cowork (Claude desktop app) — once
- Open the Claude desktop app → Cowork tab
- Open Customize → Plugins tab
- Under Personal plugins, click + → Add marketplace → Add from a repository
- Paste:
https://github.com/jslizar/marketplace - Find content-engine in the new marketplace → click Install
- Check Customize → Connectors — the Virio connector must be enabled (required)
- Optional: connect HubSpot/Attio for richer client context
Install in Claude Code (CLI / web) — once
- Run:
/plugin marketplace add jslizar/marketplace - Run:
/plugin install content-engine@jslizar-marketplace - Had
abm-engineorfunnel-engine? Remove them — content-engine replaces both - Enable the Virio MCP connector (claude.ai → Settings → Connectors) — required
Use
- Pick a working folder and use the same folder every time — the plugin keeps your clients, format library, and drafts there
- Type /content-engine and hit enter with your ask — or just ask in plain words: "TOFU post for Acme"
- Shortcuts:
/content-engine:abmruns the ABM pipeline directly;/content-engine:funnelthe TOFU/MOFU/BOFU one (typing/abmor/funnelautocompletes to them) - The pipeline pauses for your pick at each step:
- Post type — abm / tofu / mofu / bofu
- Library — Virio (corpus-mined) or Millie's list (curated)
- Format — 3 best-fit format cards, each with a real viral example
- Client — loads or builds the client's context file
- Angles — ranked format × subject × why-now options
- Drafts — 2–3 de-slopped, QA-gated candidates
- Skip steps by naming them up front: "MOFU gated-playbook post for Acme from Millie's list" jumps straight to drafting
- First run seeds
content-library/andclients/into your working folder — yours to keep and edit - Updates: update the plugin (Cowork: Customize → Plugins); new library releases trigger a one-time merge offer — your edits and pins are never touched
Format libraries
plugins/content-engine/library/ ships two libraries, seeded into a content-library/ folder in your working directory on first run:
- virio/ — corpus-mined specs (tofu, mofu, bofu, abm), refreshed on Jacob's machine by a scheduled task.
- millies/ — curated from Millie's viral content bank; updated only when a new bank ships. No BOFU lane by design (her BOFU tab is all ABM-style posts).
Each lane folder has a config.md (lane directive + admission test) and an index.md.
Library updates reach you through plugin updates: library/VERSION is stamped per
release, and on each run the engine compares it with your seeded content-library/
copy and offers a non-destructive merge (your pinned examples and edits are never
touched). Update the plugin to pick up new library releases. Do not edit the bundled
library in this repo directly — file an issue or ask Jacob.
Adding a plugin
Drop it under plugins/<name>/ and add an entry to .claude-plugin/marketplace.json.
Versioning
Plugin behavior changes bump the version in the plugin's .claude-plugin/plugin.json.
Library content updates are just commits — no version bump needed.