agentleFS
Vishwajeetkumbhar379Vishwajeetkumbhar379/claude-skills/skills/creator-contract-review/SKILL.md

creator-contract-review

Skill0 starsChanged 42 days agoMITView on GitHub

Review an influencer or creator agreement for risky clauses (usage rights, exclusivity, payment terms, revisions, ownership, kill fee, disclosure) and draft a friendly negotiation email. Use when someone shares a creator contract or asks if a deal is fair.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask for the contract as text (copied out of the PDF) and which side the person is on: creator or brand.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Creator contract review

Clause detection is done by creator-contract-checker. This skill covers the review conversation.

1 · Get the text

Ask for the contract as text (copied out of the PDF) and which side the person is on: creator or brand.

2 · Run the checker

contract-check contract.txt --side creator (add --ai for rewrites and an email). Every finding quotes the exact sentence it came from.

3 · Prioritise

  • High: perpetual usage, ownership transfer, unlimited revisions, payment over 60 days, broad exclusivity without a fee. Fix before signing.
  • Medium: paid usage without a fee, a late payment trigger, no kill fee, raw footage, auto-renewal, no disclosure clause.
  • Low: approval deadlines, one-sided morality clause, governing law.

4 · Propose fair wording

Fair to both sides and realistic for the deal size. Typical asks: 6-12 months of usage on named channels, a paid-usage fee per month, exclusivity limited to named competitors for the campaign plus 30-90 days with a fee, net 30 from posting or invoice, two revision rounds, a 50% kill fee after the brief is accepted, and an explicit disclosure label for the market (Germany: "Werbung" or "Anzeige").

5 · Draft the email

Under 150 words, friendly, listing the 3-5 changes that matter most. Apply the application-humanizer rules.

Always

Say clearly that this is a commercial review, not legal advice, and suggest a lawyer for high-value or unusual agreements.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.