contract-helper Checked

supplied target or a source-dated, jurisdiction/market-compatible anchor; otherwise the counter remains TBD/NEEDS_INPUT.

• Any WARM record is reference-only, and any signature request is either not sent or has its own exact authorization bound to the final recipient, document bytes, and channel.
• **Primary next skill**: brief-generator (../../target/brief-generator/SKILL.md) — after signature, create or finalize the creator-ready brief, then let the creator fulfill it. A signature alone is never enough to route to amplification.

### Handoff Summary

> Emit the standard shape from skill-contract.md §Handoff Summary Format (../../../references/skill-contract.md).

Data Sources

This family needs no live integrations (Tier 1). The skill works by asking you for the inputs directly: parties, deliverables, compensation, platform, and any incoming terms to review. Paste an agency's draft and it reviews against the checklist with zero setup.

Optional connectors that COULD speed up specific steps:

• ~~CRM / deal record — pull agreed scope and rate so you don't re-type them.
• ~~influencer database — resolve legal-name/entity inputs transiently from authorized party refs for the external execution copy; retain only opaque refs in WARM.
• ~~e-signature — hold the full execution copy outside WARM and route it only after the independent signature-send authorization below.

See CONNECTORS.md (../../../CONNECTORS.md) for the free/keyless recipe per category. None are required.

Instructions

When a user requests contract help:

1. **Gather contract parameters** — capture party_ref, contact_ref, address_ref, and signature_ref plus partnership details (campaign, duration, deliverables, compensation) and additional terms (usage rights, exclusivity, approval, platforms). Raw identity/contact/address/signature inputs stay transient. Use the gathering form in references/templates.md §1 (references/templates.md).

2. **Draft the agreement** — fill the 11-section framework (scope, compensation, usage rights, exclusivity, approval, compliance/FTC, warranties, confidentiality, indemnification, termination, miscellaneous + signatures). The reference-safe WARM summary and the external-only execution-copy template are separated in references/templates.md §2 (references/templates.md). Scale sections to deal size — drop whitelisting/broad-exclusivity blocks for small deals.

3. **Explain key clauses** — for each material clause give what it covers, why it matters, and what to watch for. Clause guide in references/templates.md §3 (references/templates.md).

4. **Review and flag** — for any incoming paper, run the checklist: essential terms present, red flags, and per-clause counters. Never use a built-in duration, revision count, turnaround time, or payment term as a default. A numerical counter must be user-supplied or tied to a source-dated, jurisdiction/market-compatible anchor; otherwise mark it TBD/NEEDS_INPUT. Checklist + tables in references/templates.md §4-5 (references/templates.md).

5. **Prepare and authorize e-sign execution** — keep the full executable agreement in the external e-sign/document system, compute the SHA-256 over the exact final document bytes, and show the exact recipient_ref, document hash, and delivery channel. Sending for signature is an external mutation and requires an independent exact authorization bound to that tuple; drafting, legal review, WARM save, HOT promotion, or a prior send approval does not cover it. Resolve the raw recipient/contact/address only inside the authorized provider call. If any document byte, recipient, or channel changes, discard the approval and request a new one. Do not upload, route, or send when the tuple or authorization is missing.

6. **Route after signature** — if no final creator-ready brief exists, hand off to brief-generator (../../target/brief-generator/SKILL.md). If the brief already exists, proceed with creator fulfillment; when a submission arrives, hand its frozen version to creator-content-auditor (../creator-content-auditor/SKILL.md) for revision/approval. Route an auditor-approved frozen asset to content-amplifier (../content-amplifier/SKILL.md) only when active rights cover the intended use; Spark/boost paths additionally require the matching live post, while a dark-post path does not. Do not skip fulfillment or the content gate merely because the agreement is signed.

Return the drafted agreement or review memo inline. Offer a reference-only terms summary at the exact WARM save path; never place the e-sign execution copy there. Ask separately before any HOT promotion. Once terms are signed, offer another exact authorization for a one-line operation: propose update (usage-rights window, exclusivity scope, final rate) through registry-events.py to memory/events/creators.ndjson for creator-registry (../../../protocol/creator-registry/SKILL.md) to reconcile. Drafting, signing, saving, and signature delivery are four distinct authorization surfaces; none authorizes another.

If an authorized lightweight campaign tracker already exists, offer to record stage: contracted with the signed agreement in evidence_refs; that WARM update needs its own exact save authorization and is not canonical. If the brief is already final, do not invoke another planning skill merely to extend the chain: hand the contracted brief t