Use when the user asks to "draft an influencer contract", "review these agreement terms", or "build a partnership template"; produces a full influencer agreement framework (scope, compensation, usage rights, exclusivity, FTC disclosure), a clause-by-clause review with red flags, and a negotiation cheat sheet. Not for outreach negotiation before a deal exists — use outreach-manager. 达人合同/合作协议条款审查
73
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Create and review influencer partnership agreements. Clear contracts protect both brand and creator and set expectations for the collaboration.
⚠️ This skill provides general guidance and templates. Always have contracts reviewed by legal counsel before execution.
Draft an influencer agreement for [deliverables] with [compensation terms]Review these contract terms from an influencer agency: [paste terms]memory-management is active, prior outreach terms and budget caps load from the hot cache. For rostered creators, read memory/creators/<handle-slug>.md — the creator-registry roster record — for existing exclusivity windows, contract status, usage-rights history, and standard-range anchors before drafting or reviewing.memory/influencer/contract-helper/YYYY-MM-DD-<topic>.md. Signed terms (usage-rights window, exclusivity scope, final rate) also go as a one-line update to memory/events/creators.ndjson via an authorized operation: propose request to registry-events.py — only creator-registry writes canonical roster records.memory/hot-cache.md.Emit the standard shape from skill-contract.md §Handoff Summary Format.
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 — confirm the creator's legal name, entity, and audience-authenticity signals for the warranties section.~~e-signature — route the finished agreement for signing.See CONNECTORS.md for the free/keyless recipe per category. None are required.
When a user requests contract help:
Save the drafted agreement or review memo to memory/influencer/contract-helper/YYYY-MM-DD-<topic>.md, and promote durable signed terms to the hot cache. Once terms are signed, also submit them (usage-rights window, exclusivity scope, final rate) as a one-line update to memory/events/creators.ndjson via an authorized operation: propose request to registry-events.py for creator-registry to reconcile into the roster record.
User: "Draft a simple agreement for a micro-influencer to create 2 Instagram posts for $500"
Output: a simplified agreement scoped to the deal — 2 IG posts, $500 with a payment schedule, non-exclusive 12-month usage on owned channels, #ad disclosure, and a short timeline. Heavier sections (whitelisting, broad exclusivity, multi-round approval) are dropped. See references/templates.md §7 for the worked walkthrough.
Primary: content-amplifier — once the agreement is signed and usage rights are locked, amplify the licensed content into paid and owned channels.
Alternates (same Activate family):
Termination: keep a visited-set for this session. If a skill above has already been invoked, stop and report chain-complete rather than re-running it. Max chain depth is 3 hops; once reached, summarize and hand back to the user.
4a77c48
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.