# Creator Deal Ops

> Run creator brand-deal operations from inbound brief to delivery and payment tracking. Use when the user needs sponsorship workflow support, deliverable scoping, revision control, pricing/terms checks, or payout follow-up structure.

- Skill: `leooooooow/creator-deal-ops` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add leooooooow/creator-deal-ops`
- Raw SKILL.md: https://api.skillmd.com/api/skills/leooooooow/creator-deal-ops/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Leooooooow (https://skillmd.com/u/leooooooow)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/leooooooow/creator-deal-ops

---


# Creator Deal Ops

## Skill Card

- **Category:** Operations
- **Core problem:** How to run creator sponsorships without chaos?
- **Best for:** Sponsor collaboration operations
- **Expected input:** Brand brief, deliverables, timeline, revision/payment rules
- **Expected output:** Deal plan, risk flags, revision/payment checklist
- **Creatop handoff:** Export checklist into team SOP / Notion / Feishu

## Overview

Run brand deals with clear scope, protected margin, and predictable payments.

## Workflow

### 1) Intake and qualification

Capture:
- brand/client
- campaign objective
- deliverables
- timeline
- usage rights + exclusivity
- budget/rate range

Flag incomplete briefs immediately.

### 2) Scope into delivery plan

Define in writing:
- exact deliverables (count/format)
- revision limit
- acceptance criteria
- milestone calendar

### 3) Risk and margin gate

Evaluate:
- scope creep risk
- timeline risk
- compliance risk
- margin sanity
- payment risk

Decision output:
- **Accept**
- **Negotiate**
- **Decline**

Non-negotiables (default redlines):
- unlimited revisions = not acceptable
- unclear usage rights = not acceptable
- missing due date/payment terms = not acceptable

### 4) Payment operations

Track:
- invoice sent date
- due date
- status
- next follow-up action

If overdue, send concise reminders with delivery proof.

## Output bundle

Return 4 blocks:
1. deal scorecard (accept/negotiate/decline)
2. redline terms list
3. delivery checklist
4. payment tracker row + follow-up cadence

## Quality rules

- Protect creator downside while preserving partner tone.
- Be explicit on rights, revisions, and payment terms.
- Prefer short, actionable language over legal fluff.
## License

Copyright (c) 2026 **Razestar**.

This skill is provided under **CC BY-NC-SA 4.0** for non-commercial use.
You may reuse and adapt it with attribution to Razestar, and share derivatives
under the same license.

Commercial use requires a separate paid commercial license from **Razestar**.
No trademark rights are granted.