sissoko-ugc-farming
Design and review an always-on, performance-based UGC farming and clipping program using Wunni Sissoko and GATE STUDIOS public practices. Use for creator pools, dedicated-account distribution, creative iteration, acquisition economics, and scaling decisions.
- License 许可
- Apache-2.0
- 所属仓库
- getedgehq/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- sissoko-ugc-farming
- description
- Design and review an always-on, performance-based UGC farming and clipping program using Wunni Sissoko and GATE STUDIOS public practices. Use for creator pools, dedicated-account distribution, creative iteration, acquisition economics, and scaling decisions.
02 资源文件 7
- 参考文档checklists/review-checklist.md5.8 KB
- 参考文档DERIVATION.json2.4 KB
- 参考文档examples/worked-examples.md7.5 KB
- 许可证LICENSE10.5 KB
- 参考文档references/method.md14.9 KB
- 参考文档references/sources.md3.4 KB
- 参考文档templates/output-template.md7.1 KB
03 SKILL.md 正文
Sissoko UGC Farming
Based on Woundioun "Wunni" Sissoko's public method. Not affiliated with or endorsed by Woundioun "Wunni" Sissoko.
When to use
Use this skill to produce an actionable operating brief for a continuous creator-led distribution system, or to diagnose why an existing farm loses volume, quality, or acquisition efficiency. It fits consumer apps, gaming, commerce, and software with a demonstrated self-serve adoption path. The deliverable connects creator selection, production, dedicated accounts, clipping, measurement, compensation, and winner development.
The core public model uses 15 to 50 creators working in parallel. The farming article describes 30 videos per creator distributed on TikTok and Instagram, producing 60 postings per creator. These are published operating examples, not compulsory quotas. Reported EUR 1 to 3 CPMs and 100M+ monthly views describe claimed outcomes, not forecasts or guaranteed campaign results. Keep created videos, derivatives, postings, views, clicks, and activated users separate.
Read the method for the decisions relevant to the request, then fill the output template. Attribute agency publications to GATE STUDIOS rather than implying every article is personally authored by Sissoko. Source IDs resolve in the fetched-source register. Proposed safeguards, measurement definitions, and decision thresholds are package recommendations unless specifically sourced.
Procedure
-
Define the acquisition outcome. Read references/method.md, sections 1 and 8. Specify audience, product, geography, primary conversion event, acceptable acquisition cost, budget, and accountable owner. Identify whether the user wants a new farm, more pipeline capacity, or a repair of an existing operation.
-
Check product and channel readiness. Use section 2 of references/method.md. Validate the route from content to product adoption. For prosumer software, consider the published Phase 2 sequencing before committing to high-volume short-form. Mark missing evidence and scope a bounded learning phase.
-
Build the economic model. Complete the economics fields in templates/output-template.md. Show conservative, working, and upside assumptions. Include creator costs, clipping, account operations, review, and tracking. Calculate users through explicit funnel stages, never equating a click with an install.
-
Design the creator pool and sourcing surplus. Follow section 3 of references/method.md. Set a justified cohort size, scout beyond the slots needed, assess platform craft and category fit, and record real offers. Name the replacement owner and payment process before scaling.
-
Agree performance terms and account control. Use sections 4 and 8 of references/method.md. Define the payable event, verification window, attribution, exclusions, payout timing, caps, ownership, access, and reuse permissions. Leave unresolved terms visible rather than inventing an established Sissoko contract.
-
Brief distinct creative hypotheses. Apply section 5 of references/method.md. Combine creator voice with proven format structures and product evidence. Specify platform, audience objection, opening hook, payoff, CTA, and required footage. Consult examples/worked-examples.md for weak-to-strong transformations.
-
Set up continuous distribution. Follow section 4 of references/method.md. Assign dedicated brand-specific accounts, creator-operated cadences, account-health checks, batch deadlines, and central review. Separate original asset targets from platform postings and confirm that the roster can sustain both.
-
Add clipping as a second production stream. Follow section 6 of references/method.md. Inventory cleared source footage, identify useful standalone moments, produce differentiated hooks and platform cuts, and retain parent-to-variant identifiers. Set clipping capacity separately from creator filming capacity.
-
Read performance and develop winners. Apply section 7 of references/method.md. Review by creator, hook, format, platform, and downstream event weekly. Generate variations of qualified winners; revise or stop weak hypotheses. Record evidence and the next change rather than celebrating reach alone.
-
Reuse and scale selectively. Use sections 7 and 9 of references/method.md. Move cleared winners into paid placements or product pages when justified. Scale only with credible conversion economics and sufficient review, payment, and replacement capacity. Specify hold and stop conditions before the next budget release.
-
Deliver and review the operating brief. Fill every relevant field in templates/output-template.md. Run checklists/review-checklist.md, resolve failures, and label assumptions and unavailable data. Check attribution against references/sources.md before presenting the result.
Files in this skill
- SLUG.txt: Package identifier for naming and installation.
- SKILL.md: Entry point, usage boundaries, and execution procedure.
- references/method.md: Detailed principles, decision rules, evidence limits, and edge cases.
- references/sources.md: Numbered register of fetched public sources and their contributions.
- examples/worked-examples.md: Invented operating examples with weak drafts, improvements, and rule explanations.
- templates/output-template.md: Fill-in operating brief with guidance for every field.
- checklists/review-checklist.md: Pass/fail checks and fixes for common execution failures.
04 同仓库更多 Skills
zero-downtime-cloud-move
Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.
zayats-ceo-branding
Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.
yc-app-roast
YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
yc-app-review
YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
x-growth-playbook
X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.
workplan
Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.