agentleFS
LordVayronLordVayron/video-factory/.claude/skills/onboarding/SKILL.md

onboarding

Skill67 starsChanged 18 days agoMITView on GitHub

First-run setup conversation for a new creator of the AI Video Factory. Asks exactly five short questions (what to create, where it will be published, language and tone, own brand/product/characters, budget per video), writes studio.json, creates the first project, and explains how to start other formats in new conversations. Use right after installation, when studio.json does not exist, or when the user says "onboarding", "empecemos", "set me up", "configura la fábrica", "what can I make?".

  • Reads credentials

106 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use paywalls, popups and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 20 projects that use this

  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 19 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.

    Also in 13 projects that use this

  • roerohanSkill

    prospecting

    When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

    Also in 17 projects that use this

  • martinbattaglia-commitsSkill

    marketing-loops

    When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

    Also in 10 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 19 projects that use this

  • +6 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 90 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run npm run doctor. If anything fails, fix it first (see SETUP.md).

    line 11
  2. Distinctive:

    Ask them one at a time, each with numbered options so the user can answer with a number.

    line 16
  3. Very specific:

    If they have characters or a product, run the cast skill for them first (sheets and voices go in bible/).

    line 54
  4. Distinctive:

    Don't spend credits during onboarding.

    line 61
  5. Very specific:

    If the user is in a hurry ("just make something"), pick the format they named, assume the defaults in templates/studio.json, and go …

    line 62

“Common” is measured: kept by at least 6 in 10 of the 90 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Onboarding: five questions, then the first project

Goal: in under five minutes, the creator knows what the factory can make, has a studio.json profile, and has a first project ready for its script. Speak the user's language (detect it from their first message; Spanish and English are both first-class). Be warm and brief.

Before the questions

  1. Run npm run doctor. If anything fails, fix it first (see SETUP.md). Keys go in .env: ask the user to open .env and paste their KIE_API_TOKEN and ELEVENLABS_API_KEY themselves. Never print a key back, never put one in a command line, a commit or a URL.
  2. Then npm run doctor:online to confirm both accounts answer.
  3. Say in two lines what the factory is: "An AI video studio. I write and direct, Kie.ai renders images and video, ElevenLabs does the voices. You approve two things: the script and the budget. Nothing is spent without your OK."

The five questions

Ask them one at a time, each with numbered options so the user can answer with a number. Accept free text too. Never ask more than five; infer the rest and state your assumptions at the end.

1. What do you want to create first?

  1. UGC ad for a product (creator-style review, 15–30 s)
  2. Micro-drama / vertical novela series for TikTok or Reels (60–120 s episodes)
  3. Sitcom or comedy series with recurring characters
  4. Fantasy short (epic or cozy)
  5. Long meditation, sleep story or ambient video for YouTube (10–120 min)
  6. AI influencer or "clone me" talking-head videos
  7. Anime short
  8. Cinematic short or music-video-style piece
  9. Podcast clip
  10. Something else (describe it)

2. Where will it be published? TikTok · Instagram Reels · YouTube Shorts · YouTube (long) · Ads (Meta/TikTok) · Several. This sets the aspect ratio (9:16 vertical or 16:9) and the length.

3. Language and tone? For example "Spanish, funny" or "English, calm and warm". Offer 3–4 tone options that fit the format from question 1.

4. Do you have your own brand, product or characters?

  1. Yes, I have photos or a logo (ask for the file paths or to drop them in assets/)
  2. Yes, but only a description
  3. No, create original ones for me For "clone me": only the user's own face and voice, with their consent. Never real public figures, copyrighted characters or brands they don't own.

5. Budget per video? Show the typical costs so they can choose:

FormatTypical cost
UGC ad, 15–30 s$1–3
Micro-drama or sitcom episode, 60 s$2–5
Fantasy or cinematic short, 30–60 s$2–6
Meditation or ambient, 30 minabout $2 (the picture loops)

Kie credits: 1 credit = $0.005. ElevenLabs voices are billed by ElevenLabs in characters.

After the answers

  1. Write studio.json at the repo root (gitignored), following templates/studio.json: language, formats, platforms, aspect ratio, brand or characters, budget, and the creation date.
  2. Create the first project with the intake (studio skill, flow v5): the profile already answers the format, the platform and size, and the budget; ask only the rest, one at a time (single video or series, idea or from scratch, who is on screen, references). Then node engine/studio.mjs new <slug> --title "..." --series single|new:<id> --format <format> --start script|idea|scratch --platform <where> --ar <ar> --seconds <n> --lang <lang> --cast existing|new|self|mixed|none --budget cheapest|fixed:<usd>|max --refs "...", and from then on follow node engine/studio.mjs status <slug>. Formats: studio.mjs formats. Styles: ugc-phone, hyperreal, anime, podcast, retro-sitcom (or a new one with style.mjs new; pass --style to studio.mjs new).
    • If they have characters or a product, run the cast skill for them first (sheets and voices go in bible/).
    • Styles ship as draft. The first project in a style needs its look locked once: node engine/style.mjs northstar <style> "<a scene from their idea>" (one GPT Image 2.5 frame, about $0.05, ask first), show it, then node engine/style.mjs approve <style> --northstar <file>. Every later project in that style reuses it. Long-form projects skip this.
  3. Summarize in 4–6 lines: what you understood, the assumptions you made, the project you created, and the next step (the script, gate 1). Ask: "Do you want me to write the first script now?"
  4. Tell them how to make other things: "Every format lives in its own conversation. To make something different (another format, another series, another brand), open a new conversation in this folder and just say what you want, for example: 'hazme un video de meditación de 20 minutos para dormir', 'quiero una novela para TikTok sobre una heredera secreta', 'make a UGC ad for my coffee brand'. I'll read your profile and pick the right pipeline."

Rules

  • Five questions, maximum. No forms, no long explanations.
  • Don't spend credits during onboarding. The first paid step happens only after the user approves a script and a budget.
  • If the user is in a hurry ("just make something"), pick the format they named, assume the defaults in templates/studio.json, and go straight to the script.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.