What does this skill do, and when should you use it?
Contract Helper is for the paperwork stage of an influencer or creator partnership. It turns agreed campaign details into a structured agreement framework and reviews incoming agency or partner terms clause by clause. It covers commercial terms, rights, exclusivity, compliance, red flags, and negotiation ranges. The skill provides general guidance and templates, so legal counsel should review any contract before execution.
Reads a campaign brief, agreed deliverables, compensation, platform list, usage-rights and exclusivity requirements, and any pasted incoming agreement; gathers missing contract parameters; drafts an 11-section agreement framework covering scope, compensation, usage rights, exclusivity, approval, FTC compliance, warranties, confidentiality, indemnification, termination, miscellaneous terms, and signatures; explains material clauses; reviews incoming paper for missing essentials, red flags, and negotiation ranges; saves a draft or review memo under memory/influencer/contract-helper/ and submits signed usage-rights, exclusivity, and final-rate facts through the authorized creator-registry event flow.
- A brand has agreed in principle with a creator and needs to turn deliverables and compensation into a formal agreement.
- A marketing team receives an influencer-agency contract and wants to check payment, usage, exclusivity, approval, and termination terms.
- A brand plans to reuse creator content and needs a clear owned-channel usage-rights window.
- A marketing or procurement lead wants a reusable creator partnership template that can scale to different deal sizes.
- A deal is in contract-stage negotiation and the team needs open-term ranges and concession points.
How do you install this skill?
- This is general contract guidance and templating, not a substitute for counsel in the applicable jurisdiction.
- The template is strongly FTC/U.S.-oriented; mainland-China use requires additional local advertising, contract, tax, data, and platform-law review.
- Drafts and signed terms are written to runtime memory paths; verify host privacy, access-control, backup, and deletion practices before use.
- The shared security material lists 17.x as the current supported line while the target skill declares 18.0.0; confirm release and maintenance status.
- Shell / CLI
- Local filesystem
registry-events.py
For Claude Code, run /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, then /plugin install aaron-marketing@aaron. On a compatible Agent Skills host, run npx skills add aaron-he-zhu/aaron-marketing-skills -s contract-helper, or clone the repository with git clone https://github.com/aaron-he-zhu/aaron-marketing-skills.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/influencer/activate/contract-helper" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Prompt it with Draft an influencer agreement for [deliverables] with [compensation terms] or Review these contract terms from an influencer agency: [paste terms]. You can also provide a concrete deal, such as Draft a simple agreement for a micro-influencer to create 2 Instagram posts for $500.
What are this skill's strengths and limitations?
- Covers the main creator-contract areas, including deliverables, payment, usage rights, exclusivity, approval, FTC disclosure, and termination.
- Supports drafting, incoming-contract review, and reusable partnership templates.
- Produces clause explanations, red-flag findings, and a negotiation cheat sheet tied to open terms.
- Works at Tier 1 without live integrations when the user supplies the inputs.
- It provides general guidance and templates, not legal advice; counsel review is required before execution.
- The source does not provide evidence of full template contents, automated tests, or jurisdiction-specific legal adaptation.
- Drafts and signed-term promotion use local memory files and an authorized creator-registry workflow, requiring filesystem access and approved writes.
- It is not intended for outreach negotiation before a deal exists; that scope belongs to outreach-manager.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Creator Contract Helper this page | 58 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
| Creator Content Auditor | 56 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Audience Mapper | 53 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Influencer Fit Scorer | 52 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Content Amplifier | 50 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
Unlike outreach-manager, which handles outreach, follow-up, re-engagement, and rate negotiation before paperwork, Contract Helper handles drafting and reviewing the agreement once a partnership is agreed in principle. After signing, content-amplifier is the named next skill for extending licensed creator content.
How did FollowSkills review this skill?
The skill discloses its reads, writes, promotions, and registry-proposal flow, requires legal review, and needs no live connectors. However, it persists contract and signed-term data without skill-specific per-action confirmation, data minimization, or rollback guidance, so 7 points are deducted.
Inputs, outputs, done criteria, the 11-section template, review checklist, and TBD handling are reasonably coherent, making the happy path plausible. There are no skill-specific tests, abnormal-input procedures, or diagnosable failure messages, so the static score remains below the execution-based ceiling.
Triggers, argument hints, use cases, and the boundary against pre-deal outreach negotiation are clear. The materials are primarily English and FTC/U.S.-law oriented, with limited evidence for Chinese-language, mainland-China legal, or platform-environment fit, so 4 points are deducted.
Progressive disclosure is strong: quick starts, contract contract, templates, clause explanations, checklists, examples, dependency notes, Apache-2.0 licensing, and version metadata are present. Maintenance ownership, update path, and changelog evidence are incomplete; the repository security policy also lists 17.x as current while the skill is 18.0.0, so 4 points are deducted.
The skill supplies a complete agreement framework, clause review, red-flag checklist, negotiation ranges, and a small-deal example, so it plausibly completes the core task with an editable draft or memo. There is no third-party output verification, range substantiation is limited, and legal, jurisdictional, and industry review remains substantial; static score is 6/15.
The supplied skill materials are internally auditable and concrete. Repository tests cover architecture and audit-artifact validation rather than this contract workflow, and no third-party execution evidence or cross-source corroboration is provided, so only 4/10 is awarded.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →