Sissoko Ugc Farming

---
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."
---

# 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

1. **Define the acquisition outcome.** Read [references/method.md](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.

2. **Check product and channel readiness.** Use section 2 of [references/method.md](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.

3. **Build the economic model.** Complete the economics fields in [templates/output-template.md](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.

4. **Design the creator pool and sourcing surplus.** Follow section 3 of [references/method.md](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.

5. **Agree performance terms and account control.** Use sections 4 and 8 of [references/method.md](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.

6. **Brief distinct creative hypotheses.** Apply section 5 of [references/method.md](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](examples/worked-examples.md) for weak-to-strong transformations.

7. **Set up continuous distribution.** Follow section 4 of [references/method.md](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.

8. **Add clipping as a second production stream.** Follow section 6 of [references/method.md](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.

9. **Read performance and develop winners.** Apply section 7 of [references/method.md](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.

10. **Reuse and scale selectively.** Use sections 7 and 9 of [references/method.md](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.

11. **Deliver and review the operating brief.** Fill every relevant field in [templates/output-template.md](templates/output-template.md). Run [checklists/review-checklist.md](checklists/review-checklist.md), resolve failures, and label assumptions and unavailable data. Check attribution against [references/sources.md](references/sources.md) before presenting the result.

## Files in this skill

- [SLUG.txt](SLUG.txt): Package identifier for naming and installation.
- [SKILL.md](SKILL.md): Entry point, usage boundaries, and execution procedure.
- [references/method.md](references/method.md): Detailed principles, decision rules, evidence limits, and edge cases.
- [references/sources.md](references/sources.md): Numbered register of fetched public sources and their contributions.
- [examples/worked-examples.md](examples/worked-examples.md): Invented operating examples with weak drafts, improvements, and rule explanations.
- [templates/output-template.md](templates/output-template.md): Fill-in operating brief with guidance for every field.
- [checklists/review-checklist.md](checklists/review-checklist.md): Pass/fail checks and fixes for common execution failures.