Update to withPICA Directory

{
  "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.",
  "included_files": [],
  "name": "request-a-licence",
  "skill_md_contents": "---\nname: request-a-licence\ndescription: 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.\n---\n\n_Copyright (c) 2025-2026 Withpica Ltd. All rights reserved._\n\n# request-a-licence\n\nThe 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.\n\nThis sends a real message to a real person, so it is the one step in the directory you never take on your own.\n\n## Step 1 — Confirm the song\n\nYou 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.\n\nCheck `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.\n\nIt'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.\n\n## Step 2 — Gather the details (from the user, never invented)\n\nAsk for anything you don't already have, in one short message:\n\n**Required**\n- Their **name**\n- Their **email**. The owner will reply to it, and it is shared with them.\n- **Project type:** film, tv series, commercial, trailer, video game, podcast, social media, or other\n- **How the music would be used**, in their own words (scene, length, placement)\n\n**Optional (include only if the user says it)**\n- Company or production name\n- Territory (e.g. \"UK\", \"worldwide\")\n- Term (e.g. \"1 year\", \"in perpetuity\")\n- Budget: an amount and currency, or a note such as \"flexible\" or \"£2–5k\"\n\nNever fill in a name, email, budget or project detail the user hasn't given you.\n\n## Step 3 — Show it before sending\n\nSummarise exactly what will go to the owner:\n\n> I'll send this to the owner of **\"Linen Road\"**:\n> - From: Sam Jones (sam@example.com), Example Films\n> - Project: film. \"Opening credits of a short documentary, about 60 seconds.\"\n> - Territory: UK · Term: 2 years · Budget: £1,500\n>\n> They'll reply to your email. Shall I send it?\n\nWait for a clear yes.\n\n## Step 4 — Send\n\nCall `directory_send_licensing_enquiry` once, with `work_id` and the fields the user gave.\n\nRead the result honestly:\n\n- **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.\n- **403:** this owner isn't taking enquiries right now. Say so, and offer to look for similar songs.\n- **404:** the song isn't publicly listed any more.\n- **429 (too many requests):** wait a minute and offer to try again. Nothing was sent.\n- **Unknown outcome:** it may already have gone. **Do not resend** unless the user explicitly asks, to avoid a duplicate.\n\n## What not to do\n\n- Don't send without an explicit yes in this conversation.\n- Don't send the same enquiry twice.\n- Don't promise a price, a timeline or a yes. The owner decides.\n- Don't send enquiries for several songs in one go. Confirm each one separately.\n"
}