[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEBWGPSPRVQ91380C81EDK":3,"skill-same:01M7AEBWGPSPRVQ91380C81EDK":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7AEBWGPSPRVQ91380C81EDK","contract-helper",null,"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. 达人合同\u002F合作协议条款审查","iamwaqargulzar\u002FMarketing-Agent-OS","iamwaqargulzar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96654715?v=4","01M7ACMBN0TACNXY53QYG8KDF6","Waqar Gulzar","01M7ACMBNP5ZX60H8CD3JK0633",8,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Factivate\u002Fcontract-helper\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: contract-helper\nslug: contract-helper\ndisplayName: \"Contract Helper · 合作合同助手\"\nsummary: \"红人合作协议要点:交付物、授权、独家与披露条款清单及谈判要点\"\ndescription: '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. 达人合同\u002F合作协议条款审查'\nversion: \"20.1.0\"\nlicense: Apache-2.0\ncompatibility: \"Claude Code and compatible agent-skill hosts\"\nhomepage: \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills\"\nwhen_to_use: \"Use when drafting a new influencer or creator agreement, reviewing an incoming contract or agency paper, negotiating terms such as usage rights or exclusivity, explaining standard clauses, or building a reusable partnership template. Auto-activate once a partnership is agreed in principle and the deal needs paperwork.\"\nargument-hint: \"\u003Cdeliverables and compensation> [platform] | review \u003Cpasted terms>\"\nmetadata: {\"author\": \"aaron-he-zhu\", \"version\": \"20.1.0\", \"discipline\": \"influencer\", \"phase\": \"activate\", \"geo-relevance\": \"low\", \"hermes\": {\"tags\": [\"marketing\", \"influencer\", \"activate\"], \"category\": \"influencer\"}, \"openclaw\": {\"emoji\": \"📣\", \"homepage\": \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills\"}}\n---\n\n# Contract Helper\n\nCreate and review influencer partnership agreements. Clear contracts protect both brand and creator and set expectations for the collaboration.\n\n⚠️ This skill provides general guidance and templates. Always have contracts reviewed by legal counsel before execution.\n\n## Quick Start\n\n```\nDraft an influencer agreement for [deliverables] with [compensation terms]\n```\n```\nReview these contract terms from an influencer agency: [paste terms]\n```\n\n## Skill Contract\n\n- **Reads**: campaign brief, agreed deliverables, compensation figure, platform list, usage-rights and exclusivity needs, any pasted incoming agreement, and stable `party_ref`, `contact_ref`, `address_ref`, and `signature_ref` values when available. Raw legal names, entity identifiers, emails, phones, postal addresses, payment details, and signatures are transient execution inputs only. If `memory-management` is active, prior outreach terms and budget caps load from the hot cache. For a rostered creator, resolve the carried opaque `creator_ref` through its authorized artifact or verified registry link, then read `memory\u002Fcreators\u002F\u003Caggregate-id>.md` — the [creator-registry](..\u002F..\u002F..\u002Fprotocol\u002Fcreator-registry\u002FSKILL.md) projection — for existing exclusivity windows, contract status, usage-rights history, and standard-range anchors before drafting or reviewing. Never derive the path from a raw handle.\n- **Writes**: return the drafted agreement or review memo inline by default. With exact WARM-save authorization, `memory\u002Finfluencer\u002Fcontract-helper\u002FYYYY-MM-DD-\u003Ctopic>.md` stores only `party_ref`, `contact_ref`, `address_ref`, `signature_ref`, and a non-PII terms summary; it never stores raw party\u002Fcontact\u002Faddress\u002Fsignature values, payment details, or the executable\u002Fsigned document bytes. The e-sign execution copy remains in the authorized external document\u002Fe-sign system. Each signed-term update requires a separate exact authorization for an `operation: propose` request through `registry-events.py` to `memory\u002Fevents\u002Fcreators.ndjson`; only `creator-registry` writes canonical roster records.\n- **Promotes**: only with separate exact authorization, promote durable signed terms (usage-rights window, exclusivity scope, payment schedule) to `memory\u002Fhot-cache.md`.\n- **Done when**:\n  - Every required term is filled or explicitly marked TBD (parties, deliverables, compensation, payment timeline, usage rights, exclusivity, termination).\n  - Red flags are listed for any review, and a legal-counsel review note is attached before execution.\n  - A negotiation cheat sheet maps each open term only to a user-supplied target or a source-dated, jurisdiction\u002Fmarket-compatible anchor; otherwise the counter remains `TBD\u002FNEEDS_INPUT`.\n  - 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.\n- **Primary next skill**: [brief-generator](..\u002F..\u002Ftarget\u002Fbrief-generator\u002FSKILL.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.\n\n### Handoff Summary\n\n> Emit the standard shape from [skill-contract.md §Handoff Summary Format](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md).\n\n## Data Sources\n\nThis 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.\n\nOptional connectors that COULD speed up specific steps:\n\n- `~~CRM` \u002F deal record — pull agreed scope and rate so you don't re-type them.\n- `~~influencer database` — resolve legal-name\u002Fentity inputs transiently from authorized party refs for the external execution copy; retain only opaque refs in WARM.\n- `~~e-signature` — hold the full execution copy outside WARM and route it only after the independent signature-send authorization below.\n\nSee [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) for the free\u002Fkeyless recipe per category. None are required.\n\n## Instructions\n\nWhen a user requests contract help:\n\n1. **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\u002Fcontact\u002Faddress\u002Fsignature inputs stay transient. Use the gathering form in [references\u002Ftemplates.md §1](references\u002Ftemplates.md).\n2. **Draft the agreement** — fill the 11-section framework (scope, compensation, usage rights, exclusivity, approval, compliance\u002FFTC, warranties, confidentiality, indemnification, termination, miscellaneous + signatures). The reference-safe WARM summary and the external-only execution-copy template are separated in [references\u002Ftemplates.md §2](references\u002Ftemplates.md). Scale sections to deal size — drop whitelisting\u002Fbroad-exclusivity blocks for small deals.\n3. **Explain key clauses** — for each material clause give what it covers, why it matters, and what to watch for. Clause guide in [references\u002Ftemplates.md §3](references\u002Ftemplates.md).\n4. **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\u002Fmarket-compatible anchor; otherwise mark it `TBD\u002FNEEDS_INPUT`. Checklist + tables in [references\u002Ftemplates.md §4-5](references\u002Ftemplates.md).\n5. **Prepare and authorize e-sign execution** — keep the full executable agreement in the external e-sign\u002Fdocument 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\u002Fcontact\u002Faddress 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.\n6. **Route after signature** — if no final creator-ready brief exists, hand off to [brief-generator](..\u002F..\u002Ftarget\u002Fbrief-generator\u002FSKILL.md). If the brief already exists, proceed with creator fulfillment; when a submission arrives, hand its frozen version to [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) for revision\u002Fapproval. Route an auditor-approved frozen asset to [content-amplifier](..\u002Fcontent-amplifier\u002FSKILL.md) only when active rights cover the intended use; Spark\u002Fboost 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.\n\nReturn 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\u002Fevents\u002Fcreators.ndjson` for [creator-registry](..\u002F..\u002F..\u002Fprotocol\u002Fcreator-registry\u002FSKILL.md) to reconcile. Drafting, signing, saving, and signature delivery are four distinct authorization surfaces; none authorizes another.\n\nIf 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 to the creator for fulfillment, record later submissions when authorized, and invoke the auditor only after content is submitted.\n\n## Example\n\n**User**: \"Draft a simple agreement for 2 Instagram posts at $500, Net 30 after acceptance, two revision rounds, non-exclusive 12-month owned-channel rights in the US, draft due 15 Sep and go-live 22 Sep.\"\n\n**Output**: a simplified agreement scoped to those supplied terms — 2 IG posts, $500 Net 30, two revision rounds, non-exclusive 12-month US owned-channel rights, the supplied dates, and #ad disclosure. Heavier sections outside the deal are omitted or marked TBD, not invented. Any authorized WARM save is the reference-only term summary; the executable agreement stays in the external e-sign system and is not sent without the separately approved `recipient_ref` + document SHA-256 + channel tuple. See [references\u002Ftemplates.md §7](references\u002Ftemplates.md) for the worked walkthrough.\n\n## Reference Materials\n\n- [references\u002Ftemplates.md](references\u002Ftemplates.md) — gathering form, full 11-section agreement template, clause explanations, review checklist, negotiation tables, tips, worked example.\n- [skill-contract.md](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md) — shared contract and Handoff Summary format.\n- [state-model.md](..\u002F..\u002F..\u002Freferences\u002Fstate-model.md) — memory tiers and save-path convention.\n- [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) — free\u002Fkeyless connector recipes per category.\n- Sibling skills: [outreach-manager](..\u002Foutreach-manager\u002FSKILL.md) (negotiate before contract), [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) (execute the approval clause), [budget-optimizer](..\u002F..\u002Ftarget\u002Fbudget-optimizer\u002FSKILL.md) (set compensation), [brief-generator](..\u002F..\u002Ftarget\u002Fbrief-generator\u002FSKILL.md) (attach the brief as an exhibit).\n\n## Next Best Skill\n\n**Primary**: [brief-generator](..\u002F..\u002Ftarget\u002Fbrief-generator\u002FSKILL.md) — create or finalize the creator-ready brief after signature.\n\n**Conditional next steps**:\n- **Brief already final**: proceed with creator fulfillment; when content is submitted, use [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) to run the approval workflow the contract defines.\n- **Asset approved for reuse**: use [content-amplifier](..\u002Fcontent-amplifier\u002FSKILL.md) only after confirming the frozen asset is auditor-approved and covered by active rights for the intended use; require a matching live post only for Spark\u002Fboost or another existing-post method.\n- [outreach-manager](..\u002Foutreach-manager\u002FSKILL.md) — if terms stall, return to negotiation before re-drafting.\n\n**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.\n\n## Related Skills\n\n- [outreach-manager](..\u002Foutreach-manager\u002FSKILL.md) - Negotiate before contract\n- [brief-generator](..\u002F..\u002Ftarget\u002Fbrief-generator\u002FSKILL.md) - Attach brief as exhibit\n- [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) - Execute approval process\n- [budget-optimizer](..\u002F..\u002Ftarget\u002Fbudget-optimizer\u002FSKILL.md) - Set compensation terms\n","# Contract Helper\n\nCreate and review influencer partnership agreements. Clear contracts protect both brand and creator and set expectations for the collaboration.\n\n⚠️ This skill provides general guidance and templates. Always have contracts reviewed by legal counsel before execution.\n\n## Quick Start\n\n```\nDraft an influencer agreement for [deliverables] with [compensation terms]\n```\n```\nReview these contract terms from an influencer agency: [paste terms]\n```\n\n## Skill Contract\n\n- **Reads**: campaign brief, agreed deliverables, compensation figure, platform list, usage-rights and exclusivity needs, any pasted incoming agreement, and stable `party_ref`, `contact_ref`, `address_ref`, and `signature_ref` values when available. Raw legal names, entity identifiers, emails, phones, postal addresses, payment details, and signatures are transient execution inputs only. If `memory-management` is active, prior outreach terms and budget caps load from the hot cache. For a rostered creator, resolve the carried opaque `creator_ref` through its authorized artifact or verified registry link, then read `memory\u002Fcreators\u002F\u003Caggregate-id>.md` — the [creator-registry](..\u002F..\u002F..\u002Fprotocol\u002Fcreator-registry\u002FSKILL.md) projection — for existing exclusivity windows, contract status, usage-rights history, and standard-range anchors before drafting or reviewing. Never derive the path from a raw handle.\n- **Writes**: return the drafted agreement or review memo inline by default. With exact WARM-save authorization, `memory\u002Finfluencer\u002Fcontract-helper\u002FYYYY-MM-DD-\u003Ctopic>.md` stores only `party_ref`, `contact_ref`, `address_ref`, `signature_ref`, and a non-PII terms summary; it never stores raw party\u002Fcontact\u002Faddress\u002Fsignature values, payment details, or the executable\u002Fsigned document bytes. The e-sign execution copy remains in the authorized external document\u002Fe-sign system. Each signed-term update requires a separate exact authorization for an `operation: propose` request through `registry-events.py` to `memory\u002Fevents\u002Fcreators.ndjson`; only `creator-registry` writes canonical roster records.\n- **Promotes**: only with separate exact authorization, promote durable signed terms (usage-rights window, exclusivity scope, payment schedule) to `memory\u002Fhot-cache.md`.\n- **Done when**:\n  - Every required term is filled or explicitly marked TBD (parties, deliverables, compensation, payment timeline, usage rights, exclusivity, termination).\n  - Red flags are listed for any review, and a legal-counsel review note is attached before execution.\n  - A negotiation cheat sheet maps each open term only to a user-supplied target or a source-dated, jurisdiction\u002Fmarket-compatible anchor; otherwise the counter remains `TBD\u002FNEEDS_INPUT`.\n  - 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.\n- **Primary next skill**: [brief-generator](..\u002F..\u002Ftarget\u002Fbrief-generator\u002FSKILL.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.\n\n### Handoff Summary\n\n> Emit the standard shape from [skill-contract.md §Handoff Summary Format](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md).\n\n## Data Sources\n\nThis 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.\n\nOptional connectors that COULD speed up specific steps:\n\n- `~~CRM` \u002F deal record — pull agreed scope and rate so you don't re-type them.\n- `~~influencer database` — resolve legal-name\u002Fentity inputs transiently from authorized party refs for the external execution copy; retain only opaque refs in WARM.\n- `~~e-signature` — hold the full execution copy outside WARM and route it only after the independent signature-send authorization below.\n\nSee [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) for the free\u002Fkeyless recipe per category. None are required.\n\n## Instructions\n\nWhen a user requests contract help:\n\n1. **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\u002Fcontact\u002Faddress\u002Fsignature inputs stay transient. Use the gathering form in [references\u002Ftemplates.md §1](references\u002Ftemplates.md).\n2. **Draft the agreement** — fill the 11-section framework (scope, compensation, usage rights, exclusivity, approval, compliance\u002FFTC, warranties, confidentiality, indemnification, termination, miscellaneous + signatures). The reference-safe WARM summary and the external-only execution-copy template are separated in [references\u002Ftemplates.md §2](references\u002Ftemplates.md). Scale sections to deal size — drop whitelisting\u002Fbroad-exclusivity blocks for small deals.\n3. **Explain key clauses** — for each material clause give what it covers, why it matters, and what to watch for. Clause guide in [references\u002Ftemplates.md §3](references\u002Ftemplates.md).\n4. **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\u002Fmarket-compatible anchor; otherwise mark it `TBD\u002FNEEDS_INPUT`. Checklist + tables in [references\u002Ftemplates.md §4-5](references\u002Ftemplates.md).\n5. **Prepare and authorize e-sign execution** — keep the full executable agreement in the external e-sign\u002Fdocument 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\u002Fcontact\u002Faddress 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.\n6. **Route after signature** — if no final creator-ready brief exists, hand off to [brief-generator](..\u002F..\u002Ftarget\u002Fbrief-generator\u002FSKILL.md). If the brief already exists, proceed with creator fulfillment; when a submission arrives, hand its frozen version to [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) for revision\u002Fapproval. Route an auditor-approved frozen asset to [content-amplifier](..\u002Fcontent-amplifier\u002FSKILL.md) only when active rights cover the intended use; Spark\u002Fboost 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.\n\nReturn 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\u002Fevents\u002Fcreators.ndjson` for [creator-registry](..\u002F..\u002F..\u002Fprotocol\u002Fcreator-registry\u002FSKILL.md) to reconcile. Drafting, signing, saving, and signature delivery are four distinct authorization surfaces; none authorizes another.\n\nIf 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 to the creator for fulfillment, record later submissions when authorized, and invoke the auditor only after content is submitted.\n\n## Example\n\n**User**: \"Draft a simple agreement for 2 Instagram posts at $500, Net 30 after acceptance, two revision rounds, non-exclusive 12-month owned-channel rights in the US, draft due 15 Sep and go-live 22 Sep.\"\n\n**Output**: a simplified agreement scoped to those supplied terms — 2 IG posts, $500 Net 30, two revision rounds, non-exclusive 12-month US owned-channel rights, the supplied dates, and #ad disclosure. Heavier sections outside the deal are omitted or marked TBD, not invented. Any authorized WARM save is the reference-only term summary; the executable agreement stays in the external e-sign system and is not sent without the separately approved `recipient_ref` + document SHA-256 + channel tuple. See [references\u002Ftemplates.md §7](references\u002Ftemplates.md) for the worked walkthrough.\n\n## Reference Materials\n\n- [references\u002Ftemplates.md](references\u002Ftemplates.md) — gathering form, full 11-section agreement template, clause explanations, review checklist, negotiation tables, tips, worked example.\n- [skill-contract.md](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md) — shared contract and Handoff Summary format.\n- [state-model.md](..\u002F..\u002F..\u002Freferences\u002Fstate-model.md) — memory tiers and save-path convention.\n- [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) — free\u002Fkeyless connector recipes per category.\n- Sibling skills: [outreach-manager](..\u002Foutreach-manager\u002FSKILL.md) (negotiate before contract), [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) (execute the approval clause), [budget-optimizer](..\u002F..\u002Ftarget\u002Fbudget-optimizer\u002FSKILL.md) (set compensation), [brief-generator](..\u002F..\u002Ftarget\u002Fbrief-generator\u002FSKILL.md) (attach the brief as an exhibit).\n\n## Next Best Skill\n\n**Primary**: [brief-generator](..\u002F..\u002Ftarget\u002Fbrief-generator\u002FSKILL.md) — create or finalize the creator-ready brief after signature.\n\n**Conditional next steps**:\n- **Brief already final**: proceed with creator fulfillment; when content is submitted, use [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) to run the approval workflow the contract defines.\n- **Asset approved for reuse**: use [content-amplifier](..\u002Fcontent-amplifier\u002FSKILL.md) only after confirming the frozen asset is auditor-approved and covered by active rights for the intended use; require a matching live post only for Spark\u002Fboost or another existing-post method.\n- [outreach-manager](..\u002Foutreach-manager\u002FSKILL.md) — if terms stall, return to negotiation before re-drafting.\n\n**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.\n\n## Related Skills\n\n- [outreach-manager](..\u002Foutreach-manager\u002FSKILL.md) - Negotiate before contract\n- [brief-generator](..\u002F..\u002Ftarget\u002Fbrief-generator\u002FSKILL.md) - Attach brief as exhibit\n- [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) - Execute approval process\n- [budget-optimizer](..\u002F..\u002Ftarget\u002Fbudget-optimizer\u002FSKILL.md) - Set compensation terms\n",{"name":5,"slug":5,"license":15,"summary":24,"version":25,"homepage":26,"metadata":27,"description":7,"displayName":37,"when_to_use":38,"argument-hint":39,"compatibility":40},"红人合作协议要点:交付物、授权、独家与披露条款清单及谈判要点","20.1.0","https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills",{"phase":28,"author":29,"hermes":30,"version":25,"openclaw":34,"discipline":33,"geo-relevance":36},"activate","aaron-he-zhu",{"tags":31,"category":33},[32,33,28],"marketing","influencer",{"emoji":35,"homepage":26},"📣","low","Contract Helper · 合作合同助手","Use when drafting a new influencer or creator agreement, reviewing an incoming contract or agency paper, negotiating terms such as usage rights or exclusivity, explaining standard clauses, or building a reusable partnership template. Auto-activate once a partnership is agreed in principle and the deal needs paperwork.","\u003Cdeliverables and compensation> [platform] | review \u003Cpasted terms>","Claude Code and compatible agent-skill hosts","main","ad108f7eb3f6764136d02fb875772ebb34f54078","upstreams\u002Fsource-a\u002Finfluencer\u002Factivate\u002Fcontract-helper",2,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar","iamwaqargulzar.com","2026-11-03 21:14:34",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill contract-helper",{"tool":55,"command":56},"bunx","bunx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill contract-helper",{"tool":58,"command":59},"pnpm","pnpm dlx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill contract-helper","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Factivate\u002Fcontract-helper\u002FSKILL.md",true,[63],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Ftemplates.md","REFERENCE","参考文档",19078,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Factivate\u002Fcontract-helper\u002Freferences\u002Ftemplates.md",[70,77,84,91,98,105],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AG5VYEX7J2R2AAD54A7YT7","video","When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'record a product demo,' 'feature demo video,' 'in-app demo,' 'video pipeline,' 'copy this edit,' 'match this video style,' 'reverse-engineer this video,' 'edit like this reference,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AG5FMXWA33FQDNS9PS1TE6","social","When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter\u002FX, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' 'create a reel,' 'social listening,' 'brand mentions,' 'competitor monitoring,' 'top posts to comment on,' 'find people asking for,' 'carousel,' 'slide-by-slide,' or 'document post.' Use this for social content, repurposing, scheduling, video scripts, and listening. Posts avoid AI tells like 'it's not X, it's Y' reveals and broetry. For broader content strategy, see content-strategy. For paid ads, see ad-creative. For earned media, see public-relations.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsocial\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AG559W96W3DGE31KXYY78S","sms","When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional\u002Fauth SMS. Also use when the user mentions \"SMS marketing,\" \"text message campaigns,\" \"SMS sequence,\" \"SMS automation,\" \"abandoned cart text,\" \"post-purchase SMS,\" \"Klaviyo SMS,\" \"Postscript,\" \"Attentive,\" \"Twilio,\" \"A2P 10DLC,\" \"TCPA,\" \"SMS compliance,\" \"short code,\" \"toll-free SMS,\" \"MMS campaign,\" \"should I do SMS,\" \"SMS vs email,\" \"WhatsApp marketing,\" \"WhatsApp Business API,\" \"WhatsApp templates,\" or \"click-to-WhatsApp.\" For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsms\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AG4WJ9EDSECNTQN0FEAYCQ","site-architecture","When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions \"sitemap,\" \"site map,\" \"visual sitemap,\" \"site structure,\" \"page hierarchy,\" \"information architecture,\" \"IA,\" \"navigation design,\" \"URL structure,\" \"breadcrumbs,\" \"internal linking strategy,\" \"website planning,\" \"what pages do I need,\" \"how should I organize my site,\" \"site navigation,\" \"which website builder should I use,\" \"migrate my website,\" or \"add a blog to my existing site.\" Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsite-architecture\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7AG4MH58GRMSHC0TADAWQ69","signup","When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup form optimization,\" \"free trial signup,\" \"reduce signup dropoff,\" \"account creation flow,\" \"people aren't signing up,\" \"signup abandonment,\" \"trial conversion rate,\" \"nobody completes registration,\" \"too many steps to sign up,\" or \"simplify our signup.\" Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsignup\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7AG4CGGH35KYDFHYSS1BQZ5","seo-audit","When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" \"SEO health check,\" \"my traffic dropped,\" \"lost rankings,\" \"not showing up in Google,\" \"site isn't ranking,\" \"Google update hit me,\" \"page speed,\" \"core web vitals,\" \"crawl errors,\" \"indexing issues,\" \"stuck on page 2,\" \"striking distance keywords,\" \"title tag rewrite,\" \"low CTR,\" \"local SEO,\" \"Google Business Profile,\" or \"map pack.\" Use this even if the user just says something vague like \"my SEO is bad\" or \"help with SEO\" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fseo-audit\u002FSKILL.md",[],[]]