[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M9EQMH2VMKN9FV3R8M4EJ2":3,"skill-same:01M6M9EQMH2VMKN9FV3R8M4EJ2":120},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M6M9EQMH2VMKN9FV3R8M4EJ2","suede-video",null,"Plan or produce marketing video with scripts, storyboards, shot and asset lists, consent-aware AI or avatar choices, programmatic rendering, edit decisions, pacing, export specs, and video-search metadata. Use when asked to \"turn this demo into a short video\" or build a repeatable production pipeline. NOT FOR: social calendars (use suede-social), clip-to-guide bridges (use suede-clip-to-guide), paid ad concepts (use suede-ad-creative), still images (use suede-image), or unapproved publishing.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-video\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"suede video","Video","images","ai video","for","marketing video","programmatic","concepts","rendering","ad","asset","scripts","avatar","short video","with scripts","social","build","image","publishing","clip","export","use","guide","edit","short","decisions","marketing","plan","pipeline","demo","search","2026-11-10 10:12:30",false,"---\nname: suede-video\ndescription: \"Plan or produce marketing video with scripts, storyboards, shot and asset lists, consent-aware AI or avatar choices, programmatic rendering, edit decisions, pacing, export specs, and video-search metadata. Use when asked to \\\"turn this demo into a short video\\\" or build a repeatable production pipeline. NOT FOR: social calendars (use suede-social), clip-to-guide bridges (use suede-clip-to-guide), paid ad concepts (use suede-ad-creative), still images (use suede-image), or unapproved publishing.\"\nmetadata:\n  display-name: \"Suede AI Video Skills\"\n  version: 2.2.1\n---\n\n# Suede AI Video Skills\n\n## Compatibility\n\nPlanning works from supplied media and product evidence. Rendering, generation, avatars, and frame inspection depend on discovered authorized tools; otherwise return the documented manual editor handoff.\n\nFor a concrete input, expected handoff, and failure check, read\n[the worked handoff](references\u002Fworked-handoff.md).\n\nThis skill turns an approved message and rights-cleared source material into\nscripts, storyboards, generation plans, edit systems, and reusable production\npipelines. It keeps likeness, licensing, brand assets, render cost, and\npublishing as explicit gates rather than assumptions.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nGather this context (ask if not provided):\n\n### 1. Video Goal\n- What type of video? (Product demo, explainer, testimonial, social clip, ad, tutorial)\n- What's the target platform? (YouTube, TikTok\u002FReels\u002FShorts, website, ads, sales deck)\n- What's the desired length?\n\n### 2. Production Approach\n- Do you need a human presenter? (AI avatar vs. voiceover vs. screen recording)\n- Do you have existing footage or assets? (Screenshots, logos, product UI)\n- Do you need generated footage? (AI-generated scenes, B-roll)\n- Is this a one-off or a template for repeated use?\n\n### 3. Technical Context\n- What's your tech stack? (Node.js, Python, etc.)\n- Do you have API keys for any video tools?\n- Budget constraints? (Some tools charge per minute of video)\n\n---\n\n## Choosing Your Approach\n\nChoose the production method from the job, available evidence, rights, and\ncurrently callable tools:\n\n| Approach | Candidate fit | Tools to evaluate | Use when |\n|----------|---------------|-------------------|----------|\n| **Programmatic** | Templated, data-driven, batch video | An installed HTML\u002FCSS or React renderer | The format repeats and deterministic output matters |\n| **AI generation** | Original footage from text\u002Fimage prompts | Any currently authorized generation model | The scene cannot be filmed practically and output rights are verified |\n| **AI avatars** | Approved presenter without filming | Any currently authorized avatar platform | Consent, likeness, voice, localization, and output rights are documented |\n| **Editing\u002Frepurposing** | Cutting long-form into short clips | Any installed transcript or timeline editor | Source media and derivative-use rights are available |\n\n---\n\n## Programmatic Video\n\nProgrammatic video is a candidate for repeatable, templated, or data-driven\nwork; verify fit against the current stack, edit needs, cost, and review burden.\n\n### HTML\u002FCSS renderer candidate\n\nHyperframes, from HeyGen, may fit an HTML\u002FCSS workflow. Docs:\n[hyperframes.heygen.com](https:\u002F\u002Fhyperframes.heygen.com\u002Fintroduction). First\ncheck whether it is installed.\nIf it is, read the installed version's documentation, inspect its license, and\nconfirm the renderer and export path. If it is not installed, use a\nrenderer-neutral handoff or request explicit installation authorization after\nshowing the current package source, version, lockfile impact, and cost. The\nfollowing commands must not run without that authorization:\n\n```bash\nnpx hyperframes init my-video && cd my-video\nnpx hyperframes preview               # live preview\nnpx hyperframes render -o output.mp4  # render index.html\n```\n\n**Key concept:** A composition is plain HTML, CSS, and JS. Timing is declared in\nthe markup, and the renderer seeks a paused animation timeline frame by frame.\nConfirm the current composition syntax and any programmatic render API in the\ninstalled version's docs before writing code against it.\n\n**Candidate fit:** Product announcements, changelogs, data-driven reports, and\napproved personalized outreach videos. Verify determinism with a repeat-render\ntest instead of assuming it.\n\n### React renderer candidate\n\nRemotion may fit a React-based workflow. Docs:\n[remotion.dev](https:\u002F\u002Fwww.remotion.dev\u002Fdocs). It is source-available, not open\nsource, so check its license terms. Verify the installed or callable version,\ncurrent documentation, license, rendering path, and hosting cost. The\nscaffold command may install packages or create files; run it only with explicit\nauthorization for that change, otherwise provide a renderer-neutral plan:\n\n```bash\nnpx create-video@latest\n```\n\n**Key concept to verify:** a composition is a React component that reads the\ncurrent frame number and returns what is on screen; props drive content. Confirm\nwhether rendering is local or uses an authorized hosted renderer.\n\nRead\n[references\u002Fprogrammatic-renderers.md](references\u002Fprogrammatic-renderers.md)\nwhen the repo already uses React, or when the choice between the HTML\u002FCSS and\nReact paths has to be justified: it carries the React component sample and the\nrenderer selection table. Neither framework is the more powerful one. Both\nrender web pages to video in a headless browser; the difference is what the\nteam writes.\n\n---\n\n## AI Video Generation\n\nGenerate original footage from text or image prompts. Use for B-roll, hero visuals, and scenes you can't practically film.\n\n### Model comparison\n\nDiscover currently callable and authorized models before recommending one. Read\ncurrent official documentation and run a bounded test on the actual account.\nCompare:\n\n| Criterion | Evidence to capture |\n|-----------|---------------------|\n| Output fit | Resolution, duration, audio, motion, and consistency from current docs plus a test clip |\n| Control | Reference-image, camera, edit, seed, and storyboard controls actually exposed |\n| Operations | Queue time, failure rate, export path, and repeatability |\n| Rights | Input rights, output rights, model restrictions, consent, and provenance |\n| Economics | Current plan, per-generation cost, failed-generation treatment, and budget cap |\n\nIf no model is callable and authorized, return a shot list, prompt set,\nreference-frame brief, and manual vendor-evaluation checklist.\n\n### Prompting for Video Models\n\nGood video prompts specify: **subject + action + camera + style + mood**\n\n```\nA close-up shot of hands typing on a laptop keyboard,\nshallow depth of field, warm office lighting,\ncamera slowly pulls back to reveal a modern workspace,\ncinematic color grading, 4K\n```\n\n**Common mistakes:**\n- Too vague (\"a person working\"): add specifics\n- Ignoring camera movement: specify dolly, pan, static\n- Forgetting style: \"cinematic,\" \"documentary,\" \"commercial\"\n- Requesting text in video: AI models struggle with readable text\n\n**For detailed prompting guides**: See [references\u002Fai-video-prompting.md](references\u002Fai-video-prompting.md)\n\n### AI Generation vs. Stock Evaluation\n\n| Use Case | Generation evidence to test | Stock\u002Foriginal evidence to test |\n|----------|-----------------------------|---------------------------------|\n| Specific scene | Prompt control, continuity, review burden | Search coverage, license, edit fit |\n| Style continuity | Cross-clip consistency in a bounded test | Match quality across licensed clips |\n| Real location | Factual accuracy and disclosure risk | Provenance and location release |\n| Product\u002Fbrand | UI and mark fidelity; avoid fabricated product claims | Approved real captures or assets |\n| B-roll | Queue time, failure rate, cost | Search and licensing time |\n\n---\n\n## AI Avatars\n\nCreate talking-head videos without filming. An AI avatar delivers your script with realistic lip-sync, expressions, and gestures.\n\n### Avatar tool evaluation\n\nHeyGen is one possible avatar platform, not a guaranteed or preferred\nintegration. Before naming it or another vendor, verify current official\ndocumentation, authenticated access, callable API or connector availability,\nplan limits, price, output rights, body-motion and script-ingestion controls,\nlocalization and export requirements, and the consent requirements for every\nvoice or likeness involved.\n\nIf no avatar tool is currently callable and authorized, provide a manual\nvendor-neutral workflow: approved script, consent record, user-operated upload,\nexport checklist, and a real-camera or voiceover fallback.\n\n**Possible fit to test:** product explainers, feature announcements,\nmultilingual versions, and approved personalized outreach.\n\n### Avatar vs. Other-Approach Test\n\n| Scenario | Avatar evidence to verify | Alternative to compare |\n|----------|---------------------------|------------------------|\n| Recurring content | Consent, repeatability, audience response | Recorded presenter or voiceover |\n| Multilingual versions | Translation, pronunciation, disclosure | Human localization |\n| Personalized outreach | Consent, claim review, cost, reply quality | Approved text or recorded template |\n| Founder message | Trust and disclosure response | Direct recording |\n| Product UI walkthrough | Presenter value around real captures | Screen recording |\n| Creative\u002Fartistic video | Control, originality, rights | Original footage or generated scenes |\n\n---\n\n## Editing & Repurposing Tools\n\nTurn existing content into multiple video formats.\n\nTreat the named products as candidates. Discover what is currently installed or\ncallable, verify the user's account and rights, then map the workflow to the\navailable tool. If none is available, return an edit decision list, clip\ntimestamps, captions, and export settings for manual execution.\n\n| Candidate capability | What to verify | Candidate fit |\n|----------------------|----------------|---------------|\n| Transcript editor | Speaker accuracy, cut control, export, privacy | Interviews, podcasts, webinars |\n| Clip assistant | Selection controls, provenance, false-positive rate | Long-form to short-form review |\n| Timeline editor | Caption, effect, audio-rights, and export controls | Platform-specific finishing |\n| Accessibility assistant | Caption accuracy, eye-contact disclosure, dubbing consent | Approved talking-head content |\n\n### Repurposing Workflow\n\n```\nLong-form content (podcast, webinar, demo)\n    ↓\nTranscript edit: Clean up, remove filler, polish\n    ↓\nClip review: Propose moments with source timestamps\n    ↓\nTimeline edit: Add reviewed captions, effects, and platform styling\n    ↓\nDistribute: TikTok, Reels, Shorts, LinkedIn\n```\n\n### Reverse-Engineer a Viral Edit\n\nTo study the style of a reference edit, first discover whether an authorized\nmedia-inspection, browser, or local-file viewer is currently callable. If one is\navailable, inspect the actual frames and timing. Otherwise ask the user to\nattach the media, screenshots, or a timecoded export and provide a manual\nframe-sampling checklist. Then extract a reusable beat sheet plus the 3–5\nsignature moves. Review it before execution in any currently available editor.\nCopy the editing grammar, never the reference's footage, script, voice, or\nmusic. Full method: [references\u002Fedit-anatomy.md](references\u002Fedit-anatomy.md).\n\n---\n\n## Video Production Workflows\n\n### Product Demo Video\n\n1. **Script** the key features and value props (use suede-copy skill)\n2. **Screen record** the product flow\n3. **Programmatic overlay**: use an available authorized renderer for titles,\n   callouts, and transitions, or provide manual editor instructions\n4. **AI B-roll**: only with a discovered authorized generator and verified\n   rights; otherwise use licensed stock or original footage\n5. **Voiceover**: record yourself or use AI avatar for narration\n6. **Export** at platform-appropriate specs\n\n### Explainer Video\n\n1. **Script** the problem → solution → CTA arc\n2. **Choose presenter**: an approved avatar workflow when available, or\n   recorded voiceover plus visuals\n3. **Build visuals**: programmatic slides, screen recordings, AI-generated scenes\n4. **Add captions** as an accessibility default and verify their accuracy\n5. **Export** only after checking current destination requirements and previewing\n   the authenticated composer; do not assume a universal orientation\n\n### Batch Social Clips\n\n1. **Create master template** in an available authorized renderer or a manual\n   editor project\n2. **Feed data**: product features, testimonials, stats\n3. **Render batch**: one template, many variations\n4. **Add platform-specific captions** with an available editor\n5. **Return approved export candidates** to `suede-social` for channel strategy;\n   scheduling remains a separate explicit action\n\n### Personalized Video per Account\n\nA tailored product film for each target account, built by agents. One-off\nprompting reaches a decent film after 15 to 20 minutes of back-and-forth.\nHundreds of films need the foundation built first.\n\n1. **Product component library**: agents walk the app and rebuild key screens\n   as reusable components, one source of truth every film pulls from instead of\n   redrawing.\n2. **Motion primitives**: reusable animated parts (camera pushes, screen\n   handoffs, click rhythm, product moves). Fix one and every film inherits the\n   fix.\n3. **A menu of demo flows**: company-agnostic moments buyers ask to see, each a\n   short list of beats.\n4. **Per-account script**: an agent drafts it from call notes, CRM win\u002Floss\n   data, and account research, with a fictional company on screen. A cloned\n   narrator voice requires that narrator's documented consent.\n5. **A render engine**: code that turns a beat list into a film, covering\n   camera, transitions, captions, pointer timing, and end card.\n6. **Automated QA**: render contact sheets and flag clipped text, small type,\n   and stray pointers before a person watches.\n7. **One tracker**: a row per film (account, flow, status, links) that agents\n   update as they build, export, and deliver.\n\nStoryboard the first film before production; it sits between the brief and the\nrender the way a spec sits between an idea and code. Expect tool limits at\nvolume (one agent per file, daily API caps), so run films in parallel lanes and\nbatch overnight. Any authorized programmatic renderer (Hyperframes, Remotion) or\na design tool with agent access can carry it; none is the default. Rendering,\nvoice cloning, and delivery each stay separate approvals under the Halt\nContract.\n\nSource: adapted from Harvey's write-up of its agent-built launch and\nper-account films (Shawn Farsai and Gabe Pereyra, October 2026).\n\n---\n\n## Tool-Aware Video Pipeline\n\nUse automation only after discovering currently callable, authenticated, and\nauthorized tools. Otherwise produce the same artifacts as a manual handoff.\n\n```\nApproved script (from product context)\n    ↓\nAvailable renderer\u002Favatar\u002Fgenerator, if authorized\n    or manual editor with timecoded instructions\n    ↓\nReview cut, rights, captions, and brand assets\n    ↓\nOutput: Approved export candidate, not automatically published\n```\n\nWhen no production tool is available, return the script, shot list, asset\nmanifest, beat sheet, captions, edit decision list, and export settings so the\nuser can execute the cut manually, in these exact headings:\n\n```markdown\n## Script\n\u003Cscene or beat> | on-camera or VO line | duration target\n\n## Shot List\nShot # | source (screen capture \u002F owned footage \u002F licensed \u002F generated) | framing | notes\n\n## Asset Manifest\nAsset | origin | rights basis and holder | expiry or attribution required | file path\n\n## Beat Sheet\nUse the row schema in references\u002Fedit-anatomy.md (Beat | Time | Shot |\nOn-screen text | Caption style | Transition\u002Fmotion | Audio) plus its style\nsummary. Do not invent a second beat-sheet format.\n\n## Captions\nFull caption text with timecodes; state the accuracy check performed.\n\n## Edit Decision List\nClip # | source file | in TC | out TC | placement | transition | audio bed\n\n## Export Settings\nDestination | ratio | resolution | frame rate | codec | max duration | verified\nagainst (current spec source + date)\n\n## Open Gates\n\u003Cmissing rights, consent, cost approval, or brand asset; use the halt contract>\n```\n\nFor the beat sheet and its style summary, read\n[references\u002Fedit-anatomy.md](references\u002Fedit-anatomy.md) before writing the\nhandoff: it owns that row schema.\n\n---\n\n## Export Specs and Video Search\n\nVerified platform facts (October 2026):\n\n| Destination | Fact | Source |\n|---|---|---|\n| YouTube Shorts | Up to 3 minutes for square or vertical uploads made on or after Oct 15, 2024. Over 1 minute with an active Content ID claim, the Short is blocked worldwide. | https:\u002F\u002Fsupport.google.com\u002Fyoutube\u002Fanswer\u002F15424877 |\n| Instagram Reels | Up to 3 minutes; profile grid previews crop to 3:4, so keep the subject inside a 3:4 safe area of the 9:16 frame | Instagram announcement, January 2025 |\n| Performance Max | Supply your own 16:9, 1:1, and 9:16 videos of 10 seconds or more, or Google may auto-generate one | https:\u002F\u002Fsupport.google.com\u002Fgoogle-ads\u002Fanswer\u002F17091269 |\n\nFor other destinations, read the current upload spec and preview the\nauthenticated composer before choosing ratio, resolution, or duration.\n\n**Make the video findable.** A video that answers a question people search can\nearn views for years on YouTube and in Google's video results. For any video\nmeant to be found:\n\n1. **Title:** the search phrase and the promise, phrase first, under about 70\n   characters so it is not truncated in results.\n2. **Description:** the first two lines restate the answer in plain words; the\n   rest adds links and context.\n3. **Chapters:** timestamps starting at 0:00 with descriptive names, which\n   Google can show as key moments.\n4. **Captions and transcript:** upload accurate captions instead of relying on\n   auto-captions, and publish the transcript on the page that embeds the video.\n5. **Embed on an owned page** with `VideoObject` JSON-LD (name, description,\n   thumbnailUrl, uploadDate, duration, contentUrl or embedUrl) and the video\n   visible on load, so the page itself can rank and be cited in AI answers.\n6. **Thumbnail:** one readable idea at small size; real product UI, never a\n   fabricated one.\n\nWhen the video must lead viewers to a written guide, route to\n`suede-clip-to-guide`. For site-level video indexing and schema audits, route to\n`suede-seo-audit`.\n\n---\n\n## Common Mistakes\n\n1. **Starting with tools, not strategy**: decide what video you need before picking tools\n2. **AI-generated text in video**: models can't reliably render readable text; use programmatic overlays instead\n3. **Unverified avatar quality**: test a short consented sample before paying\n   for or producing a batch\n4. **Inaccessible cut**: provide accurate captions without asserting a\n   universal sound-off viewing rate\n5. **Unverified export spec**: read current destination requirements and\n   preview the actual composer before choosing ratio, resolution, or duration\n6. **Unsupported production-style claim**: compare polished and informal\n   treatments on the current account instead of claiming one universally wins\n\n---\n\n## Halt Contract\n\nUse this exact format when tool authorization, cost approval, rights, consent,\nor an approved brand asset blocks the requested result, including the install\nand scaffold gates above and the brand-mark gate in Boundaries:\n\n```text\nHALT: \u003Cone-line blocker>\nWhy it blocks: \u003Cspecific missing authority or evidence>\nResolve with:\n1. \u003Coption>\n2. \u003Coption>\n3. \u003Coption, when useful>\nWaiting for: \u003Cthe exact item or approval>\n```\n\nContinue with the manual-handoff artifacts above only when they remain useful\nand do not imply the blocker was resolved or that a render occurred.\n\n---\n\n## Boundaries\n\n- Do not generate, render, purchase, upload, or publish media without approval\n  of scope, tool cost, rights, and destination.\n- Do not clone a real person's voice or likeness, use unlicensed source media,\n  or promise an exact copy of a reference style or edit.\n- For Suede-branded visuals, use only the approved transparent Suede S asset at\n  `JasonColapietro\u002Fsuede-creator-skills\u002Fdocs\u002Fassets\u002Fsuede-ai-logo-transparent.png`\n  with SHA-256\n  `83a7ee0317e4debe2e7b076c20ba067feb76a587f9e829dc6310ae4be4b44dfa`;\n  if it is missing or changed, omit the mark and halt for the approved file.\n\n## Routing\n\n- Use `suede-social` to choose channel strategy, cadence, and distribution.\n- Use `suede-clip-to-guide` when a clip has to bridge to an article, newsletter,\n  or guide.\n- Use `suede-ad-creative` for paid video ad concepts and variants.\n- Use `suede-image` for still-image generation and editing.\n- Use `suede-copy` for source-verified script and messaging polish.\n","# Suede AI Video Skills\n\n## Compatibility\n\nPlanning works from supplied media and product evidence. Rendering, generation, avatars, and frame inspection depend on discovered authorized tools; otherwise return the documented manual editor handoff.\n\nFor a concrete input, expected handoff, and failure check, read\n[the worked handoff](references\u002Fworked-handoff.md).\n\nThis skill turns an approved message and rights-cleared source material into\nscripts, storyboards, generation plans, edit systems, and reusable production\npipelines. It keeps likeness, licensing, brand assets, render cost, and\npublishing as explicit gates rather than assumptions.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nGather this context (ask if not provided):\n\n### 1. Video Goal\n- What type of video? (Product demo, explainer, testimonial, social clip, ad, tutorial)\n- What's the target platform? (YouTube, TikTok\u002FReels\u002FShorts, website, ads, sales deck)\n- What's the desired length?\n\n### 2. Production Approach\n- Do you need a human presenter? (AI avatar vs. voiceover vs. screen recording)\n- Do you have existing footage or assets? (Screenshots, logos, product UI)\n- Do you need generated footage? (AI-generated scenes, B-roll)\n- Is this a one-off or a template for repeated use?\n\n### 3. Technical Context\n- What's your tech stack? (Node.js, Python, etc.)\n- Do you have API keys for any video tools?\n- Budget constraints? (Some tools charge per minute of video)\n\n---\n\n## Choosing Your Approach\n\nChoose the production method from the job, available evidence, rights, and\ncurrently callable tools:\n\n| Approach | Candidate fit | Tools to evaluate | Use when |\n|----------|---------------|-------------------|----------|\n| **Programmatic** | Templated, data-driven, batch video | An installed HTML\u002FCSS or React renderer | The format repeats and deterministic output matters |\n| **AI generation** | Original footage from text\u002Fimage prompts | Any currently authorized generation model | The scene cannot be filmed practically and output rights are verified |\n| **AI avatars** | Approved presenter without filming | Any currently authorized avatar platform | Consent, likeness, voice, localization, and output rights are documented |\n| **Editing\u002Frepurposing** | Cutting long-form into short clips | Any installed transcript or timeline editor | Source media and derivative-use rights are available |\n\n---\n\n## Programmatic Video\n\nProgrammatic video is a candidate for repeatable, templated, or data-driven\nwork; verify fit against the current stack, edit needs, cost, and review burden.\n\n### HTML\u002FCSS renderer candidate\n\nHyperframes, from HeyGen, may fit an HTML\u002FCSS workflow. Docs:\n[hyperframes.heygen.com](https:\u002F\u002Fhyperframes.heygen.com\u002Fintroduction). First\ncheck whether it is installed.\nIf it is, read the installed version's documentation, inspect its license, and\nconfirm the renderer and export path. If it is not installed, use a\nrenderer-neutral handoff or request explicit installation authorization after\nshowing the current package source, version, lockfile impact, and cost. The\nfollowing commands must not run without that authorization:\n\n```bash\nnpx hyperframes init my-video && cd my-video\nnpx hyperframes preview               # live preview\nnpx hyperframes render -o output.mp4  # render index.html\n```\n\n**Key concept:** A composition is plain HTML, CSS, and JS. Timing is declared in\nthe markup, and the renderer seeks a paused animation timeline frame by frame.\nConfirm the current composition syntax and any programmatic render API in the\ninstalled version's docs before writing code against it.\n\n**Candidate fit:** Product announcements, changelogs, data-driven reports, and\napproved personalized outreach videos. Verify determinism with a repeat-render\ntest instead of assuming it.\n\n### React renderer candidate\n\nRemotion may fit a React-based workflow. Docs:\n[remotion.dev](https:\u002F\u002Fwww.remotion.dev\u002Fdocs). It is source-available, not open\nsource, so check its license terms. Verify the installed or callable version,\ncurrent documentation, license, rendering path, and hosting cost. The\nscaffold command may install packages or create files; run it only with explicit\nauthorization for that change, otherwise provide a renderer-neutral plan:\n\n```bash\nnpx create-video@latest\n```\n\n**Key concept to verify:** a composition is a React component that reads the\ncurrent frame number and returns what is on screen; props drive content. Confirm\nwhether rendering is local or uses an authorized hosted renderer.\n\nRead\n[references\u002Fprogrammatic-renderers.md](references\u002Fprogrammatic-renderers.md)\nwhen the repo already uses React, or when the choice between the HTML\u002FCSS and\nReact paths has to be justified: it carries the React component sample and the\nrenderer selection table. Neither framework is the more powerful one. Both\nrender web pages to video in a headless browser; the difference is what the\nteam writes.\n\n---\n\n## AI Video Generation\n\nGenerate original footage from text or image prompts. Use for B-roll, hero visuals, and scenes you can't practically film.\n\n### Model comparison\n\nDiscover currently callable and authorized models before recommending one. Read\ncurrent official documentation and run a bounded test on the actual account.\nCompare:\n\n| Criterion | Evidence to capture |\n|-----------|---------------------|\n| Output fit | Resolution, duration, audio, motion, and consistency from current docs plus a test clip |\n| Control | Reference-image, camera, edit, seed, and storyboard controls actually exposed |\n| Operations | Queue time, failure rate, export path, and repeatability |\n| Rights | Input rights, output rights, model restrictions, consent, and provenance |\n| Economics | Current plan, per-generation cost, failed-generation treatment, and budget cap |\n\nIf no model is callable and authorized, return a shot list, prompt set,\nreference-frame brief, and manual vendor-evaluation checklist.\n\n### Prompting for Video Models\n\nGood video prompts specify: **subject + action + camera + style + mood**\n\n```\nA close-up shot of hands typing on a laptop keyboard,\nshallow depth of field, warm office lighting,\ncamera slowly pulls back to reveal a modern workspace,\ncinematic color grading, 4K\n```\n\n**Common mistakes:**\n- Too vague (\"a person working\"): add specifics\n- Ignoring camera movement: specify dolly, pan, static\n- Forgetting style: \"cinematic,\" \"documentary,\" \"commercial\"\n- Requesting text in video: AI models struggle with readable text\n\n**For detailed prompting guides**: See [references\u002Fai-video-prompting.md](references\u002Fai-video-prompting.md)\n\n### AI Generation vs. Stock Evaluation\n\n| Use Case | Generation evidence to test | Stock\u002Foriginal evidence to test |\n|----------|-----------------------------|---------------------------------|\n| Specific scene | Prompt control, continuity, review burden | Search coverage, license, edit fit |\n| Style continuity | Cross-clip consistency in a bounded test | Match quality across licensed clips |\n| Real location | Factual accuracy and disclosure risk | Provenance and location release |\n| Product\u002Fbrand | UI and mark fidelity; avoid fabricated product claims | Approved real captures or assets |\n| B-roll | Queue time, failure rate, cost | Search and licensing time |\n\n---\n\n## AI Avatars\n\nCreate talking-head videos without filming. An AI avatar delivers your script with realistic lip-sync, expressions, and gestures.\n\n### Avatar tool evaluation\n\nHeyGen is one possible avatar platform, not a guaranteed or preferred\nintegration. Before naming it or another vendor, verify current official\ndocumentation, authenticated access, callable API or connector availability,\nplan limits, price, output rights, body-motion and script-ingestion controls,\nlocalization and export requirements, and the consent requirements for every\nvoice or likeness involved.\n\nIf no avatar tool is currently callable and authorized, provide a manual\nvendor-neutral workflow: approved script, consent record, user-operated upload,\nexport checklist, and a real-camera or voiceover fallback.\n\n**Possible fit to test:** product explainers, feature announcements,\nmultilingual versions, and approved personalized outreach.\n\n### Avatar vs. Other-Approach Test\n\n| Scenario | Avatar evidence to verify | Alternative to compare |\n|----------|---------------------------|------------------------|\n| Recurring content | Consent, repeatability, audience response | Recorded presenter or voiceover |\n| Multilingual versions | Translation, pronunciation, disclosure | Human localization |\n| Personalized outreach | Consent, claim review, cost, reply quality | Approved text or recorded template |\n| Founder message | Trust and disclosure response | Direct recording |\n| Product UI walkthrough | Presenter value around real captures | Screen recording |\n| Creative\u002Fartistic video | Control, originality, rights | Original footage or generated scenes |\n\n---\n\n## Editing & Repurposing Tools\n\nTurn existing content into multiple video formats.\n\nTreat the named products as candidates. Discover what is currently installed or\ncallable, verify the user's account and rights, then map the workflow to the\navailable tool. If none is available, return an edit decision list, clip\ntimestamps, captions, and export settings for manual execution.\n\n| Candidate capability | What to verify | Candidate fit |\n|----------------------|----------------|---------------|\n| Transcript editor | Speaker accuracy, cut control, export, privacy | Interviews, podcasts, webinars |\n| Clip assistant | Selection controls, provenance, false-positive rate | Long-form to short-form review |\n| Timeline editor | Caption, effect, audio-rights, and export controls | Platform-specific finishing |\n| Accessibility assistant | Caption accuracy, eye-contact disclosure, dubbing consent | Approved talking-head content |\n\n### Repurposing Workflow\n\n```\nLong-form content (podcast, webinar, demo)\n    ↓\nTranscript edit: Clean up, remove filler, polish\n    ↓\nClip review: Propose moments with source timestamps\n    ↓\nTimeline edit: Add reviewed captions, effects, and platform styling\n    ↓\nDistribute: TikTok, Reels, Shorts, LinkedIn\n```\n\n### Reverse-Engineer a Viral Edit\n\nTo study the style of a reference edit, first discover whether an authorized\nmedia-inspection, browser, or local-file viewer is currently callable. If one is\navailable, inspect the actual frames and timing. Otherwise ask the user to\nattach the media, screenshots, or a timecoded export and provide a manual\nframe-sampling checklist. Then extract a reusable beat sheet plus the 3–5\nsignature moves. Review it before execution in any currently available editor.\nCopy the editing grammar, never the reference's footage, script, voice, or\nmusic. Full method: [references\u002Fedit-anatomy.md](references\u002Fedit-anatomy.md).\n\n---\n\n## Video Production Workflows\n\n### Product Demo Video\n\n1. **Script** the key features and value props (use suede-copy skill)\n2. **Screen record** the product flow\n3. **Programmatic overlay**: use an available authorized renderer for titles,\n   callouts, and transitions, or provide manual editor instructions\n4. **AI B-roll**: only with a discovered authorized generator and verified\n   rights; otherwise use licensed stock or original footage\n5. **Voiceover**: record yourself or use AI avatar for narration\n6. **Export** at platform-appropriate specs\n\n### Explainer Video\n\n1. **Script** the problem → solution → CTA arc\n2. **Choose presenter**: an approved avatar workflow when available, or\n   recorded voiceover plus visuals\n3. **Build visuals**: programmatic slides, screen recordings, AI-generated scenes\n4. **Add captions** as an accessibility default and verify their accuracy\n5. **Export** only after checking current destination requirements and previewing\n   the authenticated composer; do not assume a universal orientation\n\n### Batch Social Clips\n\n1. **Create master template** in an available authorized renderer or a manual\n   editor project\n2. **Feed data**: product features, testimonials, stats\n3. **Render batch**: one template, many variations\n4. **Add platform-specific captions** with an available editor\n5. **Return approved export candidates** to `suede-social` for channel strategy;\n   scheduling remains a separate explicit action\n\n### Personalized Video per Account\n\nA tailored product film for each target account, built by agents. One-off\nprompting reaches a decent film after 15 to 20 minutes of back-and-forth.\nHundreds of films need the foundation built first.\n\n1. **Product component library**: agents walk the app and rebuild key screens\n   as reusable components, one source of truth every film pulls from instead of\n   redrawing.\n2. **Motion primitives**: reusable animated parts (camera pushes, screen\n   handoffs, click rhythm, product moves). Fix one and every film inherits the\n   fix.\n3. **A menu of demo flows**: company-agnostic moments buyers ask to see, each a\n   short list of beats.\n4. **Per-account script**: an agent drafts it from call notes, CRM win\u002Floss\n   data, and account research, with a fictional company on screen. A cloned\n   narrator voice requires that narrator's documented consent.\n5. **A render engine**: code that turns a beat list into a film, covering\n   camera, transitions, captions, pointer timing, and end card.\n6. **Automated QA**: render contact sheets and flag clipped text, small type,\n   and stray pointers before a person watches.\n7. **One tracker**: a row per film (account, flow, status, links) that agents\n   update as they build, export, and deliver.\n\nStoryboard the first film before production; it sits between the brief and the\nrender the way a spec sits between an idea and code. Expect tool limits at\nvolume (one agent per file, daily API caps), so run films in parallel lanes and\nbatch overnight. Any authorized programmatic renderer (Hyperframes, Remotion) or\na design tool with agent access can carry it; none is the default. Rendering,\nvoice cloning, and delivery each stay separate approvals under the Halt\nContract.\n\nSource: adapted from Harvey's write-up of its agent-built launch and\nper-account films (Shawn Farsai and Gabe Pereyra, October 2026).\n\n---\n\n## Tool-Aware Video Pipeline\n\nUse automation only after discovering currently callable, authenticated, and\nauthorized tools. Otherwise produce the same artifacts as a manual handoff.\n\n```\nApproved script (from product context)\n    ↓\nAvailable renderer\u002Favatar\u002Fgenerator, if authorized\n    or manual editor with timecoded instructions\n    ↓\nReview cut, rights, captions, and brand assets\n    ↓\nOutput: Approved export candidate, not automatically published\n```\n\nWhen no production tool is available, return the script, shot list, asset\nmanifest, beat sheet, captions, edit decision list, and export settings so the\nuser can execute the cut manually, in these exact headings:\n\n```markdown\n## Script\n\u003Cscene or beat> | on-camera or VO line | duration target\n\n## Shot List\nShot # | source (screen capture \u002F owned footage \u002F licensed \u002F generated) | framing | notes\n\n## Asset Manifest\nAsset | origin | rights basis and holder | expiry or attribution required | file path\n\n## Beat Sheet\nUse the row schema in references\u002Fedit-anatomy.md (Beat | Time | Shot |\nOn-screen text | Caption style | Transition\u002Fmotion | Audio) plus its style\nsummary. Do not invent a second beat-sheet format.\n\n## Captions\nFull caption text with timecodes; state the accuracy check performed.\n\n## Edit Decision List\nClip # | source file | in TC | out TC | placement | transition | audio bed\n\n## Export Settings\nDestination | ratio | resolution | frame rate | codec | max duration | verified\nagainst (current spec source + date)\n\n## Open Gates\n\u003Cmissing rights, consent, cost approval, or brand asset; use the halt contract>\n```\n\nFor the beat sheet and its style summary, read\n[references\u002Fedit-anatomy.md](references\u002Fedit-anatomy.md) before writing the\nhandoff: it owns that row schema.\n\n---\n\n## Export Specs and Video Search\n\nVerified platform facts (October 2026):\n\n| Destination | Fact | Source |\n|---|---|---|\n| YouTube Shorts | Up to 3 minutes for square or vertical uploads made on or after Oct 15, 2024. Over 1 minute with an active Content ID claim, the Short is blocked worldwide. | https:\u002F\u002Fsupport.google.com\u002Fyoutube\u002Fanswer\u002F15424877 |\n| Instagram Reels | Up to 3 minutes; profile grid previews crop to 3:4, so keep the subject inside a 3:4 safe area of the 9:16 frame | Instagram announcement, January 2025 |\n| Performance Max | Supply your own 16:9, 1:1, and 9:16 videos of 10 seconds or more, or Google may auto-generate one | https:\u002F\u002Fsupport.google.com\u002Fgoogle-ads\u002Fanswer\u002F17091269 |\n\nFor other destinations, read the current upload spec and preview the\nauthenticated composer before choosing ratio, resolution, or duration.\n\n**Make the video findable.** A video that answers a question people search can\nearn views for years on YouTube and in Google's video results. For any video\nmeant to be found:\n\n1. **Title:** the search phrase and the promise, phrase first, under about 70\n   characters so it is not truncated in results.\n2. **Description:** the first two lines restate the answer in plain words; the\n   rest adds links and context.\n3. **Chapters:** timestamps starting at 0:00 with descriptive names, which\n   Google can show as key moments.\n4. **Captions and transcript:** upload accurate captions instead of relying on\n   auto-captions, and publish the transcript on the page that embeds the video.\n5. **Embed on an owned page** with `VideoObject` JSON-LD (name, description,\n   thumbnailUrl, uploadDate, duration, contentUrl or embedUrl) and the video\n   visible on load, so the page itself can rank and be cited in AI answers.\n6. **Thumbnail:** one readable idea at small size; real product UI, never a\n   fabricated one.\n\nWhen the video must lead viewers to a written guide, route to\n`suede-clip-to-guide`. For site-level video indexing and schema audits, route to\n`suede-seo-audit`.\n\n---\n\n## Common Mistakes\n\n1. **Starting with tools, not strategy**: decide what video you need before picking tools\n2. **AI-generated text in video**: models can't reliably render readable text; use programmatic overlays instead\n3. **Unverified avatar quality**: test a short consented sample before paying\n   for or producing a batch\n4. **Inaccessible cut**: provide accurate captions without asserting a\n   universal sound-off viewing rate\n5. **Unverified export spec**: read current destination requirements and\n   preview the actual composer before choosing ratio, resolution, or duration\n6. **Unsupported production-style claim**: compare polished and informal\n   treatments on the current account instead of claiming one universally wins\n\n---\n\n## Halt Contract\n\nUse this exact format when tool authorization, cost approval, rights, consent,\nor an approved brand asset blocks the requested result, including the install\nand scaffold gates above and the brand-mark gate in Boundaries:\n\n```text\nHALT: \u003Cone-line blocker>\nWhy it blocks: \u003Cspecific missing authority or evidence>\nResolve with:\n1. \u003Coption>\n2. \u003Coption>\n3. \u003Coption, when useful>\nWaiting for: \u003Cthe exact item or approval>\n```\n\nContinue with the manual-handoff artifacts above only when they remain useful\nand do not imply the blocker was resolved or that a render occurred.\n\n---\n\n## Boundaries\n\n- Do not generate, render, purchase, upload, or publish media without approval\n  of scope, tool cost, rights, and destination.\n- Do not clone a real person's voice or likeness, use unlicensed source media,\n  or promise an exact copy of a reference style or edit.\n- For Suede-branded visuals, use only the approved transparent Suede S asset at\n  `JasonColapietro\u002Fsuede-creator-skills\u002Fdocs\u002Fassets\u002Fsuede-ai-logo-transparent.png`\n  with SHA-256\n  `83a7ee0317e4debe2e7b076c20ba067feb76a587f9e829dc6310ae4be4b44dfa`;\n  if it is missing or changed, omit the mark and halt for the approved file.\n\n## Routing\n\n- Use `suede-social` to choose channel strategy, cadence, and distribution.\n- Use `suede-clip-to-guide` when a clip has to bridge to an article, newsletter,\n  or guide.\n- Use `suede-ad-creative` for paid video ad concepts and variants.\n- Use `suede-image` for still-image generation and editing.\n- Use `suede-copy` for source-verified script and messaging polish.\n",{"name":5,"metadata":63,"description":7},{"version":64,"display-name":65},"2.2.1","Suede AI Video Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-video",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-video",{"tool":82,"command":83},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-video",{"tool":85,"command":86},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-video","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-video\u002FSKILL.md",true,[90,96,100,104,108,112,116],{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"agents\u002Fopenai.yaml","REFERENCE","参考文档",548,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-video\u002Fagents\u002Fopenai.yaml",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"CARD.md",4542,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-video\u002FCARD.md",{"path":101,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":102,"sourceHtmlUrl":103},"evals\u002Fevals.json",11253,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-video\u002Fevals\u002Fevals.json",{"path":105,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fai-video-prompting.md",5638,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-video\u002Freferences\u002Fai-video-prompting.md",{"path":109,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fedit-anatomy.md",7254,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-video\u002Freferences\u002Fedit-anatomy.md",{"path":113,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fprogrammatic-renderers.md",2807,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-video\u002Freferences\u002Fprogrammatic-renderers.md",{"path":117,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Fworked-handoff.md",1663,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-video\u002Freferences\u002Fworked-handoff.md",[121,131,139,147,155,163],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":130},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":130},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":130},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":151,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":130},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":130},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":130},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]