Update to Higgsfield

{
  "description": "Write a complete YouTube script with a full spoken body in one of six genres: business/finance, tech review, commentary, documentary, true crime or explainer. Includes hook options, timestamps, production cues and a retention map. Use for full scripts, not hook-only requests, ad copy or finished video production; ai-host-video may call this skill for its script-writing stage.\n",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 265
    },
    {
      "relative_path": "references/business-finance-patterns.md",
      "size_in_bytes": 27933
    },
    {
      "relative_path": "references/business-finance.md",
      "size_in_bytes": 9017
    },
    {
      "relative_path": "references/commentary-patterns.md",
      "size_in_bytes": 27173
    },
    {
      "relative_path": "references/commentary.md",
      "size_in_bytes": 9998
    },
    {
      "relative_path": "references/explainer-patterns.md",
      "size_in_bytes": 27142
    },
    {
      "relative_path": "references/explainer.md",
      "size_in_bytes": 9321
    },
    {
      "relative_path": "references/storytelling-documentary-patterns.md",
      "size_in_bytes": 25126
    },
    {
      "relative_path": "references/storytelling-documentary.md",
      "size_in_bytes": 9367
    },
    {
      "relative_path": "references/tech-review-patterns.md",
      "size_in_bytes": 25841
    },
    {
      "relative_path": "references/tech-review.md",
      "size_in_bytes": 9559
    },
    {
      "relative_path": "references/true-crime-patterns.md",
      "size_in_bytes": 26066
    },
    {
      "relative_path": "references/true-crime.md",
      "size_in_bytes": 10284
    }
  ],
  "name": "youtube-script",
  "skill_md_contents": "---\nname: youtube-script\ndescription: >\n  Write a complete YouTube script with a full spoken body in one of six genres:\n  business/finance, tech review, commentary, documentary, true crime or explainer.\n  Includes hook options, timestamps, production cues and a retention map.\n  Use for full scripts, not hook-only requests, ad copy or finished video production;\n  ai-host-video may call this skill for its script-writing stage.\nmetadata:\n  source_revision: \"5073f3a09d3f6b0469db9ff7e8a9df0d339f743a\"\n---\n\n## Activation analytics\n\nWhen using this skill for a new user request, call `track_skill_activation` once with `{\"skill_name\":\"youtube-script\"}` at the earliest opportunity that preserves widget-first and exclusive-tool turns; defer to a later turn when required. Do not repeat for polling, retries, references, or continuation of the same request. If tracking is unavailable or fails, continue the task without retrying. Send only the skill name.\n\n\n# YouTube Script\n\nWrite a complete YouTube script by routing the request to exactly one genre guide.\nThis root router is mandatory: load and apply this file before opening any genre\nreference. Never open or apply a genre reference as a standalone skill.\n\n## Scope boundaries\n\nUse this skill for complete YouTube scripts, including the writing stage of an\nAI-hosted episode. Hook-only or retention-outline requests do not require the full\ngenre workflow. Ad/commercial scripts and cinematic scene writing are outside this\nskill's scope; do not assume an unavailable sibling skill is installed.\n\n## Shared truth policy\n\nNever invent first-person experience, tests, purchases or spending, revenue,\nconfessions, expertise, credentials, or audience/channel history. When genre craft\ncalls for personal proof, ask the user for receipts. If receipts are unavailable,\nuse named sourced evidence or neutral analyst framing and remove the unsupported\nfirst-person claim. Never turn illustrative formulas in the references into facts.\n\nFor factual subjects, distinguish verified facts from uncertainty. Use user-supplied\nsources or available read-only research tools; ask only when required evidence is\nunavailable. Attribute evidence by name and mark unverified details for confirmation.\nDo not invent dialogue, quotations, events, statistics, or interior thoughts.\n\n## Monetization policy\n\nNever invent a sponsor read, affiliate mention, product or course plug, merch beat,\nbrand integration, or other monetization. If the user explicitly requests a\nspecific monetization integration, honor it without fabricating claims and place it\nwhere it does not break the selected genre's story, test, reveal, or payoff.\n\n## Route to exactly one genre\n\nChoose one guide only. Do not blend genre guides. Route by the promised viewer\nexperience and the structure that carries it—not by topic nouns. A company, AI,\neconomics, work, money, history, or productivity topic can enter several genres.\n\nBefore choosing, diagnose these five fields:\n\n- **subject** — the person, product, event, artifact, case, or mechanism discussed;\n- **viewer promise** — what the viewer can understand, decide, feel, or do afterward;\n- **narrative engine** — advice, verdict, stance, chronology, case reveal, or causal\n  explanation;\n- **evidence spine** — receipts/framework, test/demo, concrete artifact, event\n  timeline, case record, or mechanism/analogy;\n- **host stance** — coach/operator, reviewer, critic, narrator, case guide, or teacher.\n\nThe narrative engine and evidence spine are decisive. Subject words are supporting\nevidence only.\n\n### Affirmative entry gates\n\nSelect a guide only when its complete entry gate is satisfied:\n\n- `references/business-finance.md` — the viewer promise is an actionable personal,\n  career, entrepreneurial, productivity, self-improvement, or financial outcome, and\n  the spine is advice, a framework, operator evidence, or a decision. Do not select it\n  merely because the subject mentions a company, AI, economics, work, productivity,\n  money, “lessons,” or “how to.” A company chronology is documentary; a product\n  verdict or tutorial is tech review; a system mechanism is explainer.\n- `references/tech-review.md` — a concrete product or tool is evaluated, tested,\n  compared, ranked, demonstrated, reported as news, or taught through product use.\n  The payoff is a verdict, purchasing/usage decision, observed result, or completed\n  product task—not general career or business advice.\n- `references/commentary.md` — a concrete artifact, work, creator output, claim, or\n  cultural trend is examined through an explicit host stance. The spine is reaction,\n  critique, satire, or close reading—not neutral mechanism teaching or chronology.\n- `references/storytelling-documentary.md` — verified real events, a challenge, or a\n  person/company/history arc unfolds through chronology, conflict, investigation, and\n  reveals. The payoff is what happened and why it mattered—not primarily a list of\n  takeaways.\n- `references/true-crime.md` — a specific crime, disappearance, interrogation,\n  court/bodycam record, scam case, or dark legal case is reconstructed with\n  case-specific evidence and ethical/legal discipline. General scam prevention or\n  fraud mechanics without a case belongs elsewhere.\n- `references/explainer.md` — one central how/why question is answered through a\n  causal mechanism, misconception correction, demonstration, or analogy. Science,\n  history, economics, geography, companies, and technology route here only when\n  understanding the mechanism is the payoff.\n\nNo guide is a fallback. In particular, `business-finance` is never the default for an\nunclear advice-shaped brief.\n\n### Resolve overlaps by outcome\n\nExplicit user intent and title-promise verbs override domain nouns:\n\n- “which should I use/buy?” or “I tested/compared” → tech review;\n- “what is wrong/brilliant about this?” → commentary;\n- “what happened next/how did they rise or fall?” → storytelling/documentary;\n- “how was this case solved?” → true crime;\n- “how/why does this work?” → explainer;\n- “what should I do to improve/earn/build/decide?” → business/finance.\n\nFor example, an AI subject routes to tech review for a tool comparison, business for\nan income method, explainer for model mechanics, commentary for a critique of an AI\ntrend, and documentary for a company chronology.\n\nIdentify the closest competing guide and state why its entry gate loses. If two entry\ngates remain genuinely satisfied and the run is interactive, ask one outcome question\nwith concrete choices, such as story versus mechanism versus operator takeaways.\nIf the caller explicitly authorizes autonomous resolution, infer from the requested\noutcome, title promise, available evidence, and intended payoff. Never resolve\nambiguity by defaulting to `business-finance`.\n\n## Loading order\n\n1. Apply this root router and its shared truth and monetization policies.\n2. Select exactly one genre.\n3. Read that genre guide in full.\n4. Read its paired `*-patterns.md` file only when deeper examples or pattern detail\n   are useful.\n5. Follow the genre guide, with this root policy taking precedence if wording\n   conflicts.\n\nCallers such as `ai-host-video` may override the presentation format, headings,\ncue syntax, or surrounding workflow contract. Preserve the selected genre's craft:\nhook logic, beat structure, voice, evidence discipline, retention devices, and\nending behavior.\n\n## Direct-use output contract\n\nWhen this skill is used directly and no caller supplies another presentation\ncontract, preserve the selected guide's output format:\n\n1. Three distinct hook options.\n2. One complete timestamped script with actionable production cues.\n3. One timestamped retention map.\n\nUse the requested language and target length. At roughly 140–150 spoken words per\nminute unless the selected guide specifies another pace, write to the runtime\nrather than merely describing it.\n"
}