<aside> 🚀

🚀 FREE STRATEGY CALL

Want to grow your product through viral reach?

We help teams across iGaming, mobile apps, AI products, and SaaS build creator-led organic distribution generating tens of millions of views at CPMs starting from $0.03.

<aside> 🚀

Book a free strategy call

</aside>

On the call you'll receive:

Viral-reach gap analysis for your product
Creator-led formats already working in your niche
Estimated install / brand-lift potential at scale </aside>

50 installable Claude Skills that carry short form video from audience evidence to a published, measured asset, without inventing a single fact along the way.

What is inside

This hub is the control room. The 50 skills live on ten child pages, five to a page. Each skill carries its purpose, when to use it, its required inputs, a step by step workflow, a master instruction, three task prompts, an output schema, a human approval point, its failure modes, its handoff and a fictional example. No two skills do the same job. Every skill has one job and refuses the rest.

The hub holds what the folders share. One brief that every skill reads. Five workflows that chain skills into a sequence. Twelve named outputs and the skill that owns each one. Two worked examples. One completion checklist. Read this page before installing anything. Then work from the folders.

Layer	Count	Where it lives
Skills	50	Ten folder pages, five to a page
Task prompts	150	Inside each skill, three per skill
Templates	30	Inside the skills that own a named output
Skill folders	10	Child pages of this hub
Workflows	5	This page
Shared brief	1	This page, filled in once
Named outputs	12	Named here, produced in the folders
Worked examples	2	This page, both invented

How to install and run these skills

Six steps. Do them in order.

Install a skill. Open the folder page that holds it. Copy the master instruction in full. Paste it into a Claude Project, a new chat, or a saved skill in your workspace. Give it the name printed on the folder page. The skill is live. Nothing else is required, and no external tool is needed.
Complete the shared brief. Fill in the short form brief below once, before any skill runs. Every skill on every folder page reads from it. A skill running without the brief will guess at your audience, your claims and your limits. Guessing is the failure this collection exists to remove.
Select the first ten skills. Do not install all 50 on day one. Take one skill from each folder and run a single cycle from research to result. The gaps you feel during that cycle name the skills to install next. Depth is earned after the loop closes once.
Run the workflows. The five workflows below chain skills into an order that produces something. Start with the workflow that matches the problem in front of you today. A skill run on its own answers a question. A workflow run in order moves an asset forward.
Approve outputs. Every skill stops at a named human approval point. Read the output. Check each claim against the approved claim list in the brief. Mark anything unsupported as UNKNOWN and send it back with the reason. Approval before production and approval before publishing are both mandatory.
Maintain the collection. Run CollectionMaintainer once a month. Retire the skills nobody runs. Update the brief when a claim changes or a source expires. Record what the last cycle taught. A collection nobody prunes turns into a search problem.

An installed skill running on a stale brief is worse than no skill at all.

<aside> ⚠️

This collection never invents audience research, trends, product claims, creators or performance results. Every skill works only from what you supply, and marks everything else UNKNOWN. No skill here films, publishes, schedules or contacts anyone. A human approves every script before production and every asset before publishing. Platform policies change. Check the current rules of each platform, including disclosure requirements for paid creator work, before you post.

</aside>

The shared short form brief