Imported from recoupable/skills (
skills/recoup-catalog-explain-contract/SKILL.md). Install upstream withnpx skills add recoupable/skills --skill recoup-catalog-explain-contract. Copyright stays with the author.
Explain this music contract
Read references/music-business-records.md before starting; it defines supported
file-review and hosted-save routes, source handling and completion checks.
Result
Answer what this particular agreement says, what it asks each party to do and what needs clarification before the user relies on it.
Workflow
- Identify the user's question and role, the agreement/version, named parties and available schedules, exhibits, signatures and amendments. Read the complete supplied material with available file tools; label excerpts and missing pages explicitly. A filename or unsigned draft does not prove execution or current enforceability.
- Explain the covered recordings/compositions/products and the scope of granted rights, exclusivity, territory, term, renewal, termination and any post-term rights. Cite clause/page and source version for each consequential statement; flag undefined terms, conflicting clauses or omitted repertoire schedules rather than filling gaps.
- Extract money and operating terms: advances, payment rates/bases, recoupment, deductions, reserves, reporting/payment frequency, audit rights, approvals, delivery duties, warranties and indemnities when present. Retain conditions and exceptions. A rate without its definition of revenue is not a usable earnings calculation.
- Distinguish obligations triggered by signing, release, delivery, notice or another condition. Compute dates only with an evidenced trigger/date and applicable clause; otherwise show the trigger the user must confirm. Do not invent overdue balances.
- Return a plain-language summary, term table (what it says / practical effect / clause), each party's obligations and specific questions caused by missing or ambiguous text. Separate contractual wording from interpretation. Use a short quote only when needed, then paraphrase.
- If asked about enforceability, legal remedies or a jurisdiction-specific rule, verify current authoritative sources and mark the question for qualified legal review where appropriate; do not turn a document summary into a legal determination. Persist the summary privately through an available scoped operation or return a local report, identifying which material was actually inspected.
Handoff
Lead with the answer to the user's question, not a generic risk score. State whether this is a draft, apparently signed copy or unknown status based on inspected material. Do not negotiate, send notices, sign, register claims, change balances or treat contract language as permission to collect royalties. This is explanation of the supplied text, not a full catalog underwriting or royalty audit.
Example: “exclusive for three years after first commercial release” produces a conditional term explanation; without the release date, it does not produce an expiry date.
Reusable term schedule
Keep the standalone answer concise. When another stage needs the terms, populate
templates/term-schedule.json using references/term-extraction.md; each term has a
source version, clause, exact scope, conditions and separate interpretation status.
A contract term records evidence; it does not authorize a software operation.
Record missing signatures, exhibits, amendments, signed releases and termination proof
as individual dependencies. Another session can review the same clause and reproduce
what was known without relying on this chat.
