跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

contract-helper

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. 达人合同/合作协议条款审查

aaron-he-zhu · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add aaron-he-zhu/aaron-marketing-skills --skill contract-helper

技能说明


name: contract-helper slug: contract-helper displayName: "Contract Helper · 合作合同助手" summary: "红人合作协议要点:交付物、授权、独家与披露条款清单及谈判要点" description: '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. 达人合同/合作协议条款审查' version: "20.1.0" license: Apache-2.0 compatibility: "Claude Code and compatible agent-skill hosts" homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills" when_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." argument-hint: " [platform] | review " metadata: {"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://github.com/aaron-he-zhu/aaron-marketing-skills"}}

Contract Helper

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.

Quick Start

Draft an influencer agreement for [deliverables] with [compensation terms]
Review these contract terms from an influencer agency: [paste terms]

Skill Contract

  • 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/creators/<aggregate-id>.md — the creator-registry 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.
  • Writes: return the drafted agreement or review memo inline by default. With exact WARM-save authorization, memory/influencer/contract-helper/YYYY-MM-DD-<topic>.md stores only party_ref, contact_ref, address_ref, signature_ref, and a non-PII terms summary; it never stores raw party/contact/address/signature values, payment details, or the executable/signed document bytes. The e-sign execution copy remains in the authorized external document/e-sign system. Each signed-term update requires a separate exact authorization for an operation: propose request through registry-events.py to memory/events/creators.ndjson; only creator-registry writes canonical roster records.
  • Promotes: only with separate exact authorization, promote durable signed terms (usage-rights window, exclusivity scope, payment schedule) to memory/hot-cache.md.
  • Done when:
    • Every required term is filled or explicitly marked TBD (parties, deliverables, compensation, payment timeline, usage rights, exclusivity, termination).
    • Red flags are listed for any review, and a legal-counsel review note is attached before execution.
    • A negotiation cheat sheet maps each open term only to a user-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 — 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.

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 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/templa
阅读完整来源 ↗