Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Convert client briefs into detailed motion design/VFX production plans, estimates, and invoice drafts with optional project folder setup and invoicing API in...
Convert client briefs into detailed motion design/VFX production plans, estimates, and invoice drafts with optional project folder setup and invoicing API in...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Ask for (or infer) the input brief: Paste text directly, or Provide a file path to a brief/email/thread export. Produce these outputs (always): docs/creative-ops/plan.md (client-ready) docs/creative-ops/estimate.json (structured line items) docs/creative-ops/invoice-draft.json (ready for API import later) If Chris wants it, also: Create a project folder skeleton (AE/C4D/Octane-friendly) with a docs/README.md. POST the invoice draft to the local invoicing API (only if base URL is configured and Chris says βpush itβ).
Project summary (one paragraph) Goals / Success criteria Deliverables (matrix) Format, duration, aspect ratios, versions, audio deliverables Workflow assumptions whatβs included, whatβs not, number of review rounds Open questions (what you still need answered) Production plan phases + milestones + review windows Risks / dependencies Estimate line items + hours + rate + subtotal + contingency Next actions
Prefer generating structured data first, then render it: Extract entities Client name Project name Deadline/date constraints Deliverables list Constraints (brand, legal, footage supply, approvals) Decide the production approach Template-driven vs bespoke 2D AE vs 3D C4D vs mixed Estimate with motion/VFX realism Prepro (briefing, styleframes, boards) Production (anim, 3D, comp) Audio/music/licensing (if applicable) Renders, exports, versioning PM/admin buffer
Use the bundled script to create consistent outputs: python skills/creative-ops-copilot/scripts/creative_ops_copilot.py --brief "<paste brief>" --out . If the brief is a file: python skills/creative-ops-copilot/scripts/creative_ops_copilot.py --brief-file "C:\path\to\brief.txt" --out . To also create a project skeleton: python skills/creative-ops-copilot/scripts/creative_ops_copilot.py --brief "..." --out . --skeleton To attempt pushing the invoice draft to your local invoicing API (only if configured): python skills/creative-ops-copilot/scripts/creative_ops_copilot.py --brief "..." --out . --push-invoice
Optional config file: skills/creative-ops-copilot/references/config.example.json Copy to: skills/creative-ops-copilot/references/config.json Then edit: invoicingApi.baseUrl invoicingApi.apiKey (if needed) rateCard defaults
Keep outputs concise, clean, and client-ready. When anything is missing/ambiguous, surface it under Open questions instead of guessing.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.