Cue for AI

The cue-pitch skill.

One downloadable skill that teaches your AI to build a press kit from your Cue catalog — research the artist with receipts, fill the EPK, write the record page with the music on it — and leave the sending to you.

What it is

cue-pitch is an Agent Skill — a single SKILL.md you load into your own AI (claude.ai, Claude Code, or any agent that reads skills). It carries the press-kit playbook: how to ground itself in your catalog, how to research an artist without inventing a word, how to fill the EPK and build a record page through Cue's MCP tools — in your workspace's voice, read live at runtime. One skill, every workspace; nothing to fork or configure.

The division of labor is the whole idea: the record is Cue's; the pitch is yours. Your AI and Cue make a page worth sending. You send it from your own mail, with your own publicist or your own AI — Cue has no mail, no contact list, and never writes to a writer.

Get it

  • claude.ai — Settings → Capabilities → Skills → upload cue-pitch.zip.
  • Claude Code — unzip into ~/.claude/skills/ so you have ~/.claude/skills/cue-pitch/SKILL.md.
  • Anything else — it's plain markdown with frontmatter; paste it wherever your agent takes standing instructions.

Then connect the Cue MCP server (see Cue speaks MCP) and ask your AI to build the press kit for a record.

Better: download it from inside Cue. The "your AI" button on your records and artist pages hands you this same skill personalized to your workspace — your release ids, record ids, what each EPK is still missing — so your AI skips the warm-up questions. The download above is the generic edition.

What your AI learns

  • Ground itself in your press kit and catalog before writing a word — your voice, not its own.
  • Research with receipts: credits and dates from the artist's own public pages, verified where-to-listen links, an honest fans-of line.
  • Fill the EPK once — the durable facts every record page backfills from.
  • Build the record page: hook, press release, credits, every track playing inline — then read it back and check every name against the kit.
  • Hand you the link, and an email body if you want one — fifty to a hundred and fifty words, one ask, the link once.
  • Read the analytics back as facts: what was opened, what was played, what was downloaded.

The rules it carries

Some of these Cue enforces in code — unconfirmed rights render as "contact to confirm", kit-only credits stay off the public page, master downloads follow the artist's own switch. The rest the skill imposes on your AI as standing rules:

  • No fabricated quotes, press, or numbers — every claim traces to the kit, the artist's public pages, or you.
  • Money, rights, and clearance answers are always yours — the AI drafts, you commit.
  • It never sends. The deliverable is the page link; the email is yours to paste.
  • A live page is public. Nothing private goes on it.
The cue-pitch skill. · Cue docs