Skills and plugin
Two Agent Skills teach an assistant Crossfeed’s flows through the MCP server: relaying the agent’s questions to you word for word, and leaving approval to the app. A Claude Code plugin installs both with the server.
The skills
| Skill | When an assistant uses it |
|---|---|
plan-launch-promosSKILL.md | Plan a podcast launch's promos across a network's own shows with Crossfeed's MCP tools, which rank the roster by listener overlap in Qloo and draft an insertion order that a member approves in the app. Use when the user wants to plan, run, or rerun a Crossfeed launch, pick which roster shows promote a new show and how many slots each gets, settle the roster for a launch, change a draft insertion order, understand why a show ranks where it does on a launch's chart, see which of the network's own shows share listeners with each other, or who the network's shows reach by age and gender. |
triage-guest-pitchesSKILL.md | Triage a podcast's guest pitches with Crossfeed's MCP tools, which read each pitch for the public work it promotes, rank those works against one of the network's shows by listener overlap in Qloo, and draft Book, Later, or Decline replies that a member approves in the app. Use when the user wants to sort, rank, or answer guest or booking pitches, load a day's pitches or an inbox export into Crossfeed, or decide which pitched guests a show should book. |
Each is written to the Agent Skills specification, with its fields only, so any client that reads skills can use it. Both hold the assistant to the same rules: put each of the agent’s questions to you exactly as it’s asked and answer with your words, never with its own; leave approval to a member, in the app, and give the page where it happens; keep guest names, email addresses, and sender details out of every field but the ones made for them, such as the pitches it loads; and explain a rank only from the Qloo evidence behind it.
The Claude Code plugin
The plugin, crossfeed, sits in the repo’s plugins/crossfeed, beside a marketplace file at the repo’s root. It holds both skills and this MCP server config:
plugins/crossfeed/.mcp.json{
"mcpServers": {
"crossfeed": {
"type": "http",
"url": "${CROSSFEED_URL:-https://crossfeed.m1kuorg.workers.dev}/mcp",
"headers": { "Authorization": "Bearer ${CROSSFEED_API_KEY}" }
}
}
}CROSSFEED_API_KEY is one of the network’s API keys. CROSSFEED_URL points it at another deployment, such as https://crossfeed.m1kuorg.workers.dev; without it, the plugin connects to https://crossfeed.m1kuorg.workers.dev. Set both in the environment Claude Code starts in.
Install it
It isn’t in a public marketplace yet. From a clone of the repo:
git clone https://github.com/m1kuorg/qloo.git
claude plugin marketplace add ./qloo
claude plugin install crossfeed@crossfeedThen start claude with one of the network’s API keys, from its settings, in CROSSFEED_API_KEY, and ask it to plan promos for your launch.
claude plugin marketplace add m1kuorg/qloo adds the same marketplace from GitHub for anyone who can read the repo.
Without the plugin
Connect the MCP server to Claude Code with one of the network’s API keys:
Put the key in your shell as
CROSSFEED_API_KEY: in bash or zsh, run this, paste the key, and press Return. Nothing shows as you paste, and the key stays out of your shell’s history. On Windows, run these steps in WSL or Git Bash: in PowerShell,$CROSSFEED_API_KEYis empty, andclaude mcp addwould save the header without the key.Shell read -rs CROSSFEED_API_KEY && export CROSSFEED_API_KEYAdd Crossfeed’s MCP server to Claude Code, in the folder you’ll use it from. Claude Code keeps the key from then on, in plain text in its own config file,
~/.claude.json.Shell claude mcp add --transport http crossfeed \ https://crossfeed.m1kuorg.workers.dev/mcp \ --header "Authorization: Bearer $CROSSFEED_API_KEY"Check it:
claude mcp listshould show it connected.Shell claude mcp listOutput crossfeed: https://crossfeed.m1kuorg.workers.dev/mcp (HTTP) - ✔ Connected
Then copy a skill’s directory from plugins/crossfeed/skills into ~/.claude/skills, or wherever your client reads skills from. Each skill’s text is also served here, at a stable URL: / and /.