withPICA Directory

View saved version →

---
name: find-music-for-sync-brief
description: Find music in the PICA public directory for a sync brief — translate a mood/vibe/scene description into audio search parameters, run the search, and return a rights-aware shortlist with credit details for licensing.
triggers:
  - find music for a sync brief
  - find me a track for a film scene
  - music for this brief
  - find an uplifting indie folk track
  - I need music that sounds like
audience: sync supervisor / music library / ad agency / film & TV music team
tools_required:
  - directory_search_recordings
  - directory_lookup_work
  - directory_lookup_person
output: A rights-aware shortlist — each result with title, artist, audio characteristics (BPM, key, energy), credits summary for licensing contact, and any flags (unattested credits, low registration score, missing ISRC).
---

_Copyright (c) 2025-2026 Withpica Ltd. All rights reserved._

# find-music-for-sync-brief

Help the user find music in PICA's public directory for a sync brief. Translate their description (mood, vibe, scene, era, vocal style) into search parameters, run the search, and return a shortlist that includes the information they need to license — not just the track.

This is a public skill — any AI agent connected to the directory MCP can use it. The directory only contains songs listed by their owner or a confirmed writer.

## Step 1 — Translate the brief

Most sync briefs are described in natural language. Translate before searching:

| User says | Search parameters |
|---|---|
| upbeat / uplifting / driving | `min_energy: 0.6`, `min_danceability: 0.5` |
| dark / moody / brooding | `max_energy: 0.4`, `key_mode: minor` |
| chill / ambient / background | `max_energy: 0.4`, `max_bpm: 100` |
| epic / cinematic | `min_energy: 0.7`, often longer durations |
| specific BPM ("around 120bpm") | `min_bpm: 115`, `max_bpm: 125` |
| acoustic / sparse | typically lower `danceability` and `energy` |
| vocal / instrumental | filter on `has_vocals` if available |

If the user gives an artist or song reference ("something like X"), look up that reference first via `directory_lookup_work` or `directory_search_recordings` by title — then mimic its audio profile in the new search.

## Step 2 — Search

Call `directory_search_recordings` with the parameters from step 1. Default limit is fine for an initial scan.

If the brief is vague, do two searches with slightly different parameters and compare. If too many results, narrow on BPM or key. If too few, widen the BPM range first, then drop key_mode.

## Step 3 — Lookup full details

For the top 5-10 promising results, call `directory_lookup_work` to get:

- **Who wrote it** — credits with IPI numbers (essential for the licensing contact path)
- **Whether credits are attested** — an unattested credit means the ownership claim hasn't been verified; flag this
- **DSP links** (Spotify, Apple Music) — the user wants to listen before shortlisting
- **Registration score** — higher score = cleaner rights chain = easier to license

For high-value matches where the user wants to know more about the creator, call `directory_lookup_person` with the IPI (or the credit's `global_creator_id`) to see how many of the writer's songs are listed and who they work with on them; `directory_list_works` with their name lists the songs themselves.

## Step 4 — Present the shortlist

Present each shortlisted track with:

- **Title, artist** — what the user listens for
- **Audio profile** — BPM, key, energy (one line, the supervisor's quick filter)
- **Credits summary** — writers with IPI, publisher if known (this is the licensing path)
- **DSP links** — so the user can listen
- **Flags** — unattested credits, low registration score, missing ISRC, multiple writers (= multi-party clearance needed)

If a track has all green flags (attested credits, high registration score, ISRC present, single or low-count writers), call it out as "clean to clear."

## Step 5 — If no results

If the search returns nothing, walk the user back through the brief:
- Widen the BPM range first (most supervisors don't actually mind ±10 BPM)
- Drop the key filter (key matching matters less than mood for most placements)
- Drop the energy bounds and search by genre/mood text only
- Suggest the user expand to adjacent moods ("uplifting" → also try "warm" or "hopeful")

Be honest if the directory is small for a specific style — PICA's directory grows as songs are listed; some niches are sparse.

An empty search comes back with a short note and a link for sharing PICA with the creators. Pass it on once in the conversation, in your own words. If the user knows who makes the music they're after, that link is how it ends up in the directory.

## What not to do

- Don't claim to license tracks — this skill returns a shortlist, not a license. When the user wants to approach an owner, offer `directory_send_licensing_enquiry`, and send it only once they say yes and give their own name, email and project description. Never invent those details.
- Don't speculate about pricing — sync fees are negotiated per-placement
- Don't return results from outside the directory (no general web search, no Spotify metadata directly) — the directory is the source of truth for this skill
- Don't return tracks with no attested credits without flagging them as "rights chain unverified"

## Follow-on skills

- `due-diligence-on-creator` (Stage 2 candidate) — for deeper research on a specific writer before reaching out

View saved version →

---
name: get-started
description: First time someone opens the withPICA Directory, or asks what it is or how to use it. Explain in two lines what the directory holds, show three things they can ask, and hand off to the right skill. Use when the first message names no specific song, person or code.
---

_Copyright (c) 2025-2026 Withpica Ltd. All rights reserved._

# get-started

The user has just connected the withPICA Directory, or asked what it does. Orient them in one short message, then let them choose.

## Say what it is (two lines, plain words)

> The withPICA Directory lets you search songs and their rights: who wrote and published a song, its codes (ISWC, ISRC, IPI), how confirmed each credit is, and how to ask the owner about licensing. Every song in it was listed by the people who own it.

## Offer three ways in

> You could ask:
> - **"Who owns [song]?"** I'll show the writers, publishers and how confirmed the credits are.
> - **"Find something upbeat, around 120bpm, for a car ad."** I'll search by sound and build a shortlist.
> - **"I want to license [song]."** I'll help you send the owner an enquiry.

Then stop and let them pick. Don't run a search they didn't ask for.

## Route to the right skill

| They want | Use |
|---|---|
| Who's behind a song, or a code lookup | `who-owns-this-song` |
| Music for a brief, mood or scene | `find-music-for-sync-brief` |
| To use a song | `request-a-licence` |

## Be honest about size

The directory grows as owners list their catalogues, so some searches come back empty. When that happens, say it isn't listed **yet** and pass on the directory's note once. Never suggest a song doesn't exist, and never fill a gap from memory.

View saved version →

---
name: request-a-licence
description: Help someone ask the owner of a song in PICA's public music directory about licensing it for a film, TV, ad, game, podcast or social project. Confirm the right song, gather the user's own details and project description, show them the enquiry before it goes, and send it only with their explicit go-ahead.
---

_Copyright (c) 2025-2026 Withpica Ltd. All rights reserved._

# request-a-licence

The user has found a song and wants to use it. This skill opens the conversation with the owner. **Nothing is agreed or priced here.** The enquiry simply reaches the owner, who replies to the user by email.

This sends a real message to a real person, so it is the one step in the directory you never take on your own.

## Step 1 — Confirm the song

You need the work's ID. If you don't have it yet, find the song with `directory_chain` (by title, ISWC or ISRC) or `directory_lookup_work`. Read the title and writers back to the user and confirm it's the right one. Many songs share a title.

Check `enquiries_open` in the `directory_lookup_work` result before asking for anything. If the owner isn't taking enquiries, say so now and offer to look for similar songs, so the user doesn't type their details for nothing.

It's worth mentioning whether the song is `ready_to_license` and whether its credits are confirmed, so the user knows what they're walking into.

## Step 2 — Gather the details (from the user, never invented)

Ask for anything you don't already have, in one short message:

**Required**
- Their **name**
- Their **email**. The owner will reply to it, and it is shared with them.
- **Project type:** film, tv series, commercial, trailer, video game, podcast, social media, or other
- **How the music would be used**, in their own words (scene, length, placement)

**Optional (include only if the user says it)**
- Company or production name
- Territory (e.g. "UK", "worldwide")
- Term (e.g. "1 year", "in perpetuity")
- Budget: an amount and currency, or a note such as "flexible" or "£2–5k"

Never fill in a name, email, budget or project detail the user hasn't given you.

## Step 3 — Show it before sending

Summarise exactly what will go to the owner:

> I'll send this to the owner of **"Linen Road"**:
> - From: Sam Jones (sam@example.com), Example Films
> - Project: film. "Opening credits of a short documentary, about 60 seconds."
> - Territory: UK · Term: 2 years · Budget: £1,500
>
> They'll reply to your email. Shall I send it?

Wait for a clear yes.

## Step 4 — Send

Call `directory_send_licensing_enquiry` once, with `work_id` and the fields the user gave.

Read the result honestly:

- **Sent:** tell them it's on its way and the owner will reply by email. A confirmation email to them usually follows but isn't guaranteed.
- **403:** this owner isn't taking enquiries right now. Say so, and offer to look for similar songs.
- **404:** the song isn't publicly listed any more.
- **429 (too many requests):** wait a minute and offer to try again. Nothing was sent.
- **Unknown outcome:** it may already have gone. **Do not resend** unless the user explicitly asks, to avoid a duplicate.

## What not to do

- Don't send without an explicit yes in this conversation.
- Don't send the same enquiry twice.
- Don't promise a price, a timeline or a yes. The owner decides.
- Don't send enquiries for several songs in one go. Confirm each one separately.

View saved version →

---
name: who-owns-this-song
description: Answer "who owns this song?" from PICA's public music directory. Start from a song title, artist, ISRC or ISWC, find the work, and show who wrote and published it, how confirmed those credits are, and whether it is ready to license. Use when someone needs to know who to talk to about a piece of music.
---

_Copyright (c) 2025-2026 Withpica Ltd. All rights reserved._

# who-owns-this-song

Someone has a song in mind and wants to know who is behind it: who wrote it, who publishes it, and whether the rights are clear enough to approach. Find the song in the directory and give them a plain answer they can act on.

The directory only holds songs whose owners have chosen to list them. If a song isn't there, say so plainly. Never fill the gap from memory or the web. The empty result carries a link for sharing PICA with the people who made the song. Offer it once; if they list their catalogue, the answer will be here next time.

## Step 1 — Find the song

Pick the lookup that matches what the user gave you:

| User gives | Call |
|---|---|
| An ISRC (e.g. `GBABC2400001`) | `directory_lookup_isrc` |
| An ISWC (e.g. `T-123.456.789-0`) | `directory_chain` with `identifier` |
| A title, with or without artist | `directory_chain` with `q` |
| Only a person's name | `directory_list_people` with `q`, then `directory_lookup_person` with the `global_creator_id` it returns |

`directory_chain` returns the work, its writers and publishers, the linked recording and its audio profile in one call. Start there whenever you can.

If several songs match a title, list them briefly (title, writers, year if shown) and ask which one. Don't guess.

## Step 2 — Get the detail

Call `directory_lookup_work` with the work's ISWC or ID. It adds:

- **Credits with IPI numbers.** IPIs are the identifiers collecting societies use, so they're the reliable way to name a writer.
- **Whether each credit is confirmed.** An unconfirmed credit means someone listed it but the owner hasn't verified it.
- **Recordings and ISRCs,** plus Spotify / Apple Music links so the user can listen.
- **Registration score.** Higher means the paperwork is more complete.

## Step 3 — Answer plainly

Lead with the answer, then the detail:

> **"Linen Road"** was written by A. Writer (IPI 00012345678) and B. Writer (IPI 00087654321), published by Example Music. Both credits are confirmed by the owners. It's ready to license: the song and a recording are confirmed, with an ISRC and an ISWC.

Then add any flags:

- **Unconfirmed credits:** "one credit hasn't been confirmed by its owner yet; treat it as a claim."
- **Several writers:** "three writers means three people to clear with."
- **Missing ISRC or ISWC:** "it hasn't been fully registered, so expect more back-and-forth."
- **`ready_to_license: true`:** the song and a recording are confirmed by every owner, with audio, an ISRC and an ISWC.
- **`programmable_since` present:** every owner has confirmed a locked split, so a fee can be paid to each without chasing sign-off. Only say the split is signed off when this is present.

## Step 4 — Offer the next step

If the user wants to use the song, offer to send a licensing enquiry to the owner (see the `request-a-licence` skill). Don't send anything until they ask.

## What not to do

- Don't state splits or percentages unless the directory returns them. The chain view deliberately leaves splits out.
- Don't give contact details the directory doesn't provide. The enquiry tool is the route to the owner.
- Don't present a credit as fact if it isn't confirmed.
- Don't answer from outside the directory. If it's not listed, say "it's not in the PICA directory" and stop there.