[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74F9ZGSZQKW2RCF2R4RSYRC":3,"skill-same:01M74F9ZGSZQKW2RCF2R4RSYRC":135},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":13,"repositoryHtmlUrl":68,"repositoryHomepageUrl":6,"ownerHtmlUrl":69,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":70,"install":71,"resources":84},"01M74F9ZGSZQKW2RCF2R4RSYRC","kanban-video-orchestrator",null,"Plan, set up, and monitor a multi-agent video production pipeline backed by Hermes Kanban. Use when the user wants to make ANY video — narrative film, product\u002Fmarketing, music video, explainer, ASCII\u002Fterminal art, abstract\u002Fgenerative loop, comic, 3D, real-time\u002Finstallation — and the work warrants decomposition into specialized profiles (writer, designer, animator, renderer, voice, editor, etc.) coordinated through a kanban board. Performs adaptive discovery to scope the brief, designs an appropriate team for the requested style, generates the setup script that creates Hermes profiles + initial kanban task, then helps monitor execution and intervene when tasks stall or fail. Routes scenes to whichever Hermes rendering \u002F audio \u002F design skill fits each beat (`ascii-video`, `manim-video`, `p5js`, `comfyui`, `touchdesigner-mcp`, `blender-mcp`, `pixel-art`, `baoyu-comic`, `claude-design`, `excalidraw`, `songsee`, `heartmula`, …) plus external APIs for TTS, image-gen, and image-to-video as needed.","lzy18001500226\u002FMoSim","lzy18001500226","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152623587?v=4","01M71ZMEX36NK05B642131DEEK","01M71ZMEXSMX72KPVNJ572G0CM",0,"MIT","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: kanban-video-orchestrator\ndescription: Plan, set up, and monitor a multi-agent video production pipeline backed by Hermes Kanban. Use when the user wants to make ANY video — narrative film, product\u002Fmarketing, music video, explainer, ASCII\u002Fterminal art, abstract\u002Fgenerative loop, comic, 3D, real-time\u002Finstallation — and the work warrants decomposition into specialized profiles (writer, designer, animator, renderer, voice, editor, etc.) coordinated through a kanban board. Performs adaptive discovery to scope the brief, designs an appropriate team for the requested style, generates the setup script that creates Hermes profiles + initial kanban task, then helps monitor execution and intervene when tasks stall or fail. Routes scenes to whichever Hermes rendering \u002F audio \u002F design skill fits each beat (`ascii-video`, `manim-video`, `p5js`, `comfyui`, `touchdesigner-mcp`, `blender-mcp`, `pixel-art`, `baoyu-comic`, `claude-design`, `excalidraw`, `songsee`, `heartmula`, …) plus external APIs for TTS, image-gen, and image-to-video as needed.\nversion: 1.0.0\nauthor: [SHL0MS, alt-glitch]\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [video, kanban, multi-agent, orchestration, production-pipeline]\n    related_skills: [kanban-orchestrator, kanban-worker, ascii-video, manim-video, p5js, comfyui, touchdesigner-mcp, blender-mcp, pixel-art, ascii-art, songwriting-and-ai-music, heartmula, songsee, spotify, youtube-content, claude-design, excalidraw, architecture-diagram, concept-diagrams, baoyu-comic, baoyu-infographic, humanizer, gif-search, meme-generation]\n    credits: |\n      The single-project workspace layout, profile-config patching pattern,\n      SOUL.md-per-profile model, TEAM.md task-graph convention, and\n      `--workspace dir:\u003Cpath>` discipline are adapted from alt-glitch's\n      original multi-agent video pipeline at\n      https:\u002F\u002Fgithub.com\u002FNousResearch\u002Fkanban-video-pipeline.\n---\n\n# Kanban Video Orchestrator\n\nWrap any video request — from a 15-second product teaser to a 5-minute narrative\nshort to a music video to an ASCII loop — in a Hermes Kanban pipeline that\ndecomposes the work to specialized agent profiles.\n\nThis skill does **not** render anything itself. It is a meta-pipeline that:\n\n1. **Scopes** the request through targeted discovery\n2. **Designs** an appropriate team (which roles, which tools per role) based on the style\n3. **Generates** a setup script that creates Hermes profiles, project workspace, and the initial kanban task\n4. **Hands off** to the director profile, which decomposes via the kanban\n5. **Monitors** execution, helps intervene when tasks stall or fail\n\nThe actual rendering happens inside the kanban once it's running, via whichever\nexisting skills + tools fit the scenes — `ascii-video`, `manim-video`, `p5js`,\n`comfyui`, `touchdesigner-mcp`, `blender-mcp`, `songwriting-and-ai-music`,\n`heartmula`, external APIs, or plain Python with PIL + ffmpeg.\n\n## When NOT to use this skill\n\n- The video is one continuous procedural project that needs no specialists. Just write the code directly.\n- The user wants a quick one-shot conversion (e.g. \"convert this mp4 to a GIF\") — use ffmpeg directly.\n- The output is a static image, GIF, or audio-only artifact — use the matching specific skill (`ascii-art`, `gifs`, `meme-generation`, `songwriting-and-ai-music`).\n- The work fits a single existing skill cleanly (e.g. a pure ASCII video — just use `ascii-video`).\n\n## Workflow\n\n```\nDISCOVER  →  BRIEF  →  TEAM DESIGN  →  SETUP  →  EXECUTE  →  MONITOR\n```\n\n### Step 1 — Discover (ask the right questions)\n\nThe discovery process is **adaptive**: ask only what is actually needed. Always\nstart with three questions to identify the broad shape:\n\n- **What is the video?** (one-sentence brief)\n- **How long?** (5-30s teaser \u002F 30-90s short \u002F 90s-3min explainer \u002F 3-10min film \u002F longer)\n- **What aspect ratio + target platform?** (1:1 \u002F 9:16 \u002F 16:9; X, IG, YouTube, internal, etc.)\n\nFrom the answer, classify the style category. The style determines which\nfollow-up questions to ask. **Do not ask all questions at once.** Ask 2-4 at a\ntime, listen, then proceed. Make reasonable assumptions whenever the user\nimplies an answer.\n\nFor complete intake patterns and per-style question banks, see\n**[references\u002Fintake.md](references\u002Fintake.md)**.\n\n### Step 2 — Brief\n\nOnce enough is known, produce a structured `brief.md` using the template in\n`assets\u002Fbrief.md.tmpl`. Stages:\n\n1. **Concept** — the one-sentence pitch + emotional north star\n2. **Scope** — duration, aspect, platform, deadline\n3. **Style** — visual references, brand constraints, tone\n4. **Scenes** — beat-by-beat breakdown (durations, content, target tool)\n5. **Audio** — narration \u002F music \u002F SFX \u002F silent (per scene if needed)\n6. **Deliverables** — file format, resolution, optional alternates (vertical cut, GIF, etc.)\n\nShow the brief to the user for confirmation before designing the team. **The\nbrief is the contract** — every downstream task references it.\n\n### Step 3 — Team design\n\nPick role archetypes from the library that fit this video. **Compose, don't\nclone.** Most videos need 4-7 profiles. The director is always present; the\nrest are picked by what the brief actually requires.\n\nFor the role library and per-style team compositions, see\n**[references\u002Frole-archetypes.md](references\u002Frole-archetypes.md)**.\n\nFor mapping role → which Hermes skills + toolsets it loads, see\n**[references\u002Ftool-matrix.md](references\u002Ftool-matrix.md)**.\n\n### Step 4 — Setup\n\nGenerate a setup script (`setup.sh`) and run it. The script:\n\n1. Creates the project workspace (`~\u002Fprojects\u002Fvideo-pipeline\u002F\u003Cslug>\u002F`)\n2. Copies any provided assets into `taste\u002F`, `audio\u002F`, `assets\u002F`\n3. Creates each Hermes profile via `hermes profile create --clone`\n4. Writes per-profile `SOUL.md` (personality + role definition)\n5. Configures profile YAML (toolsets, always_load skills, cwd)\n6. Writes `brief.md`, `TEAM.md`, and `taste\u002F` content\n7. Fires the initial `hermes kanban create` task assigned to the director\n\nUse `scripts\u002Fbootstrap_pipeline.py` to generate setup.sh from a brief +\nteam-design JSON. See **[references\u002Fkanban-setup.md](references\u002Fkanban-setup.md)**\nfor the setup script structure, profile config patterns, and the critical\n\"shared workspace\" rule.\n\n### Step 5 — Execute\n\nRun `setup.sh`. Then provide the user with monitoring commands:\n\n```bash\nhermes kanban watch --tenant \u003Cproject-tenant>     # live events\nhermes kanban list  --tenant \u003Cproject-tenant>     # board snapshot\nhermes dashboard                                   # visual board UI\n```\n\nThe director profile takes over from here, decomposing the work and routing\ntasks to specialist profiles via the kanban toolset.\n\n### Step 6 — Monitor and intervene\n\nStay engaged — the kanban runs autonomously but a stuck task or bad output\nneeds human (or AI) judgment.\n\nMonitoring patterns: poll `kanban list` periodically, inspect any RUNNING task\nthat exceeds its expected duration with `kanban show \u003Cid>`, and check\nheartbeats. When a worker's output fails review, the standard interventions are:\n\n1. Comment on the worker's task with specific feedback (`kanban_comment`)\n2. Create a re-run task with the original as parent\n3. Adjust the brief's scope and let the director re-decompose\n\nFor diagnostic patterns, intervention recipes, and the \"task is stuck\"\nplaybook, see **[references\u002Fmonitoring.md](references\u002Fmonitoring.md)**.\n\n## Reference: worked examples\n\nSix concrete pipelines covering very different video styles — narrative film,\nproduct\u002Fmarketing, music video, math\u002Falgorithm explainer, ASCII video, real-time\ninstallation — showing how the same workflow yields very different teams and\ntask graphs. See **[references\u002Fexamples.md](references\u002Fexamples.md)**.\n\n## Critical rules\n\n1. **Discovery before action.** Never start generating a brief or team without\n   asking at least the three baseline questions. A bad brief cascades through\n   the entire pipeline.\n\n2. **Match the team to the video.** Don't reuse the same 4-profile setup for\n   every job. A music video that doesn't have a beat-analysis profile will\n   misfire. A narrative film that doesn't have a writer profile will produce\n   incoherent scenes. See `references\u002Frole-archetypes.md`.\n\n3. **One workspace per project.** All profiles for a given video share the same\n   `dir:` workspace. Tasks pass artifacts via shared filesystem and structured\n   handoffs. **Every** `kanban_create` call passes\n   `workspace_kind=\"dir\"` + `workspace_path=\"\u003Cabsolute project path>\"`.\n\n4. **Tenant every project.** Use a project-specific tenant\n   (`--tenant \u003Cproject-slug>`). Keeps the dashboard scoped and prevents\n   cross-pollination with other ongoing kanbans.\n\n5. **Respect existing skills.** When a scene fits an existing skill, the\n   relevant renderer should load that skill via `--skill \u003Cname>` on its task\n   or `always_load` in its profile. Do not re-derive what a skill already\n   provides.\n\n6. **The director never executes.** Even with the full `kanban + terminal +\n   file` toolset, the director's `SOUL.md` rules forbid it from executing\n   work itself. It decomposes and routes only — every concrete task becomes\n   a `hermes kanban create` call to a specialist profile. The\n   `kanban-orchestrator` skill spells this out further.\n\n7. **Don't over-decompose.** A 30-second product video does NOT need 20 tasks.\n   Aim for the smallest task graph that still parallelizes well and exposes the\n   right human-review gates.\n\n8. **Verify API keys BEFORE firing.** External APIs (TTS, image-gen,\n   image-to-video) need keys in `~\u002F.hermes\u002F.env` or the user's secret store.\n   A worker that hits a missing-key error wastes a task slot. The setup\n   script's `check_key` helper aborts cleanly if a required key is missing.\n\n## File map\n\n```\nSKILL.md                            ← this file (workflow + rules)\nreferences\u002F\n  intake.md                         ← discovery question banks per style\n  role-archetypes.md                ← role library (writer, designer, animator, …)\n  tool-matrix.md                    ← skill + toolset mapping per role\n  kanban-setup.md                   ← setup script structure & profile config\n  monitoring.md                     ← watch + intervene patterns\n  examples.md                       ← six worked pipelines\nassets\u002F\n  brief.md.tmpl                     ← brief skeleton\n  setup.sh.tmpl                     ← setup script skeleton\n  soul.md.tmpl                      ← profile personality skeleton\nscripts\u002F\n  bootstrap_pipeline.py             ← generate setup.sh from brief + team JSON\n  monitor.py                        ← polling + intervention helpers\n```\n","# Kanban Video Orchestrator\n\nWrap any video request — from a 15-second product teaser to a 5-minute narrative\nshort to a music video to an ASCII loop — in a Hermes Kanban pipeline that\ndecomposes the work to specialized agent profiles.\n\nThis skill does **not** render anything itself. It is a meta-pipeline that:\n\n1. **Scopes** the request through targeted discovery\n2. **Designs** an appropriate team (which roles, which tools per role) based on the style\n3. **Generates** a setup script that creates Hermes profiles, project workspace, and the initial kanban task\n4. **Hands off** to the director profile, which decomposes via the kanban\n5. **Monitors** execution, helps intervene when tasks stall or fail\n\nThe actual rendering happens inside the kanban once it's running, via whichever\nexisting skills + tools fit the scenes — `ascii-video`, `manim-video`, `p5js`,\n`comfyui`, `touchdesigner-mcp`, `blender-mcp`, `songwriting-and-ai-music`,\n`heartmula`, external APIs, or plain Python with PIL + ffmpeg.\n\n## When NOT to use this skill\n\n- The video is one continuous procedural project that needs no specialists. Just write the code directly.\n- The user wants a quick one-shot conversion (e.g. \"convert this mp4 to a GIF\") — use ffmpeg directly.\n- The output is a static image, GIF, or audio-only artifact — use the matching specific skill (`ascii-art`, `gifs`, `meme-generation`, `songwriting-and-ai-music`).\n- The work fits a single existing skill cleanly (e.g. a pure ASCII video — just use `ascii-video`).\n\n## Workflow\n\n```\nDISCOVER  →  BRIEF  →  TEAM DESIGN  →  SETUP  →  EXECUTE  →  MONITOR\n```\n\n### Step 1 — Discover (ask the right questions)\n\nThe discovery process is **adaptive**: ask only what is actually needed. Always\nstart with three questions to identify the broad shape:\n\n- **What is the video?** (one-sentence brief)\n- **How long?** (5-30s teaser \u002F 30-90s short \u002F 90s-3min explainer \u002F 3-10min film \u002F longer)\n- **What aspect ratio + target platform?** (1:1 \u002F 9:16 \u002F 16:9; X, IG, YouTube, internal, etc.)\n\nFrom the answer, classify the style category. The style determines which\nfollow-up questions to ask. **Do not ask all questions at once.** Ask 2-4 at a\ntime, listen, then proceed. Make reasonable assumptions whenever the user\nimplies an answer.\n\nFor complete intake patterns and per-style question banks, see\n**[references\u002Fintake.md](references\u002Fintake.md)**.\n\n### Step 2 — Brief\n\nOnce enough is known, produce a structured `brief.md` using the template in\n`assets\u002Fbrief.md.tmpl`. Stages:\n\n1. **Concept** — the one-sentence pitch + emotional north star\n2. **Scope** — duration, aspect, platform, deadline\n3. **Style** — visual references, brand constraints, tone\n4. **Scenes** — beat-by-beat breakdown (durations, content, target tool)\n5. **Audio** — narration \u002F music \u002F SFX \u002F silent (per scene if needed)\n6. **Deliverables** — file format, resolution, optional alternates (vertical cut, GIF, etc.)\n\nShow the brief to the user for confirmation before designing the team. **The\nbrief is the contract** — every downstream task references it.\n\n### Step 3 — Team design\n\nPick role archetypes from the library that fit this video. **Compose, don't\nclone.** Most videos need 4-7 profiles. The director is always present; the\nrest are picked by what the brief actually requires.\n\nFor the role library and per-style team compositions, see\n**[references\u002Frole-archetypes.md](references\u002Frole-archetypes.md)**.\n\nFor mapping role → which Hermes skills + toolsets it loads, see\n**[references\u002Ftool-matrix.md](references\u002Ftool-matrix.md)**.\n\n### Step 4 — Setup\n\nGenerate a setup script (`setup.sh`) and run it. The script:\n\n1. Creates the project workspace (`~\u002Fprojects\u002Fvideo-pipeline\u002F\u003Cslug>\u002F`)\n2. Copies any provided assets into `taste\u002F`, `audio\u002F`, `assets\u002F`\n3. Creates each Hermes profile via `hermes profile create --clone`\n4. Writes per-profile `SOUL.md` (personality + role definition)\n5. Configures profile YAML (toolsets, always_load skills, cwd)\n6. Writes `brief.md`, `TEAM.md`, and `taste\u002F` content\n7. Fires the initial `hermes kanban create` task assigned to the director\n\nUse `scripts\u002Fbootstrap_pipeline.py` to generate setup.sh from a brief +\nteam-design JSON. See **[references\u002Fkanban-setup.md](references\u002Fkanban-setup.md)**\nfor the setup script structure, profile config patterns, and the critical\n\"shared workspace\" rule.\n\n### Step 5 — Execute\n\nRun `setup.sh`. Then provide the user with monitoring commands:\n\n```bash\nhermes kanban watch --tenant \u003Cproject-tenant>     # live events\nhermes kanban list  --tenant \u003Cproject-tenant>     # board snapshot\nhermes dashboard                                   # visual board UI\n```\n\nThe director profile takes over from here, decomposing the work and routing\ntasks to specialist profiles via the kanban toolset.\n\n### Step 6 — Monitor and intervene\n\nStay engaged — the kanban runs autonomously but a stuck task or bad output\nneeds human (or AI) judgment.\n\nMonitoring patterns: poll `kanban list` periodically, inspect any RUNNING task\nthat exceeds its expected duration with `kanban show \u003Cid>`, and check\nheartbeats. When a worker's output fails review, the standard interventions are:\n\n1. Comment on the worker's task with specific feedback (`kanban_comment`)\n2. Create a re-run task with the original as parent\n3. Adjust the brief's scope and let the director re-decompose\n\nFor diagnostic patterns, intervention recipes, and the \"task is stuck\"\nplaybook, see **[references\u002Fmonitoring.md](references\u002Fmonitoring.md)**.\n\n## Reference: worked examples\n\nSix concrete pipelines covering very different video styles — narrative film,\nproduct\u002Fmarketing, music video, math\u002Falgorithm explainer, ASCII video, real-time\ninstallation — showing how the same workflow yields very different teams and\ntask graphs. See **[references\u002Fexamples.md](references\u002Fexamples.md)**.\n\n## Critical rules\n\n1. **Discovery before action.** Never start generating a brief or team without\n   asking at least the three baseline questions. A bad brief cascades through\n   the entire pipeline.\n\n2. **Match the team to the video.** Don't reuse the same 4-profile setup for\n   every job. A music video that doesn't have a beat-analysis profile will\n   misfire. A narrative film that doesn't have a writer profile will produce\n   incoherent scenes. See `references\u002Frole-archetypes.md`.\n\n3. **One workspace per project.** All profiles for a given video share the same\n   `dir:` workspace. Tasks pass artifacts via shared filesystem and structured\n   handoffs. **Every** `kanban_create` call passes\n   `workspace_kind=\"dir\"` + `workspace_path=\"\u003Cabsolute project path>\"`.\n\n4. **Tenant every project.** Use a project-specific tenant\n   (`--tenant \u003Cproject-slug>`). Keeps the dashboard scoped and prevents\n   cross-pollination with other ongoing kanbans.\n\n5. **Respect existing skills.** When a scene fits an existing skill, the\n   relevant renderer should load that skill via `--skill \u003Cname>` on its task\n   or `always_load` in its profile. Do not re-derive what a skill already\n   provides.\n\n6. **The director never executes.** Even with the full `kanban + terminal +\n   file` toolset, the director's `SOUL.md` rules forbid it from executing\n   work itself. It decomposes and routes only — every concrete task becomes\n   a `hermes kanban create` call to a specialist profile. The\n   `kanban-orchestrator` skill spells this out further.\n\n7. **Don't over-decompose.** A 30-second product video does NOT need 20 tasks.\n   Aim for the smallest task graph that still parallelizes well and exposes the\n   right human-review gates.\n\n8. **Verify API keys BEFORE firing.** External APIs (TTS, image-gen,\n   image-to-video) need keys in `~\u002F.hermes\u002F.env` or the user's secret store.\n   A worker that hits a missing-key error wastes a task slot. The setup\n   script's `check_key` helper aborts cleanly if a required key is missing.\n\n## File map\n\n```\nSKILL.md                            ← this file (workflow + rules)\nreferences\u002F\n  intake.md                         ← discovery question banks per style\n  role-archetypes.md                ← role library (writer, designer, animator, …)\n  tool-matrix.md                    ← skill + toolset mapping per role\n  kanban-setup.md                   ← setup script structure & profile config\n  monitoring.md                     ← watch + intervene patterns\n  examples.md                       ← six worked pipelines\nassets\u002F\n  brief.md.tmpl                     ← brief skeleton\n  setup.sh.tmpl                     ← setup script skeleton\n  soul.md.tmpl                      ← profile personality skeleton\nscripts\u002F\n  bootstrap_pipeline.py             ← generate setup.sh from brief + team JSON\n  monitor.py                        ← polling + intervention helpers\n```\n",{"name":5,"author":23,"license":14,"version":26,"metadata":27,"platforms":61,"description":7},[24,25],"SHL0MS","alt-glitch","1.0.0",{"hermes":28},{"tags":29,"credits":35,"related_skills":36},[30,31,32,33,34],"video","kanban","multi-agent","orchestration","production-pipeline","The single-project workspace layout, profile-config patching pattern,\nSOUL.md-per-profile model, TEAM.md task-graph convention, and\n`--workspace dir:\u003Cpath>` discipline are adapted from alt-glitch's\noriginal multi-agent video pipeline at\nhttps:\u002F\u002Fgithub.com\u002FNousResearch\u002Fkanban-video-pipeline.",[37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60],"kanban-orchestrator","kanban-worker","ascii-video","manim-video","p5js","comfyui","touchdesigner-mcp","blender-mcp","pixel-art","ascii-art","songwriting-and-ai-music","heartmula","songsee","spotify","youtube-content","claude-design","excalidraw","architecture-diagram","concept-diagrams","baoyu-comic","baoyu-infographic","humanizer","gif-search","meme-generation",[62,63,64],"linux","macos","windows","main","e0ec177d00f087cb04e90206b2f7d3aa2f5a1350","References\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim","https:\u002F\u002Fgithub.com\u002Flzy18001500226","2026-08-31 23:29:00",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add lzy18001500226\u002FMoSim --skill kanban-video-orchestrator",{"tool":77,"command":78},"bunx","bunx skills add lzy18001500226\u002FMoSim --skill kanban-video-orchestrator",{"tool":80,"command":81},"pnpm","pnpm dlx skills add lzy18001500226\u002FMoSim --skill kanban-video-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002FSKILL.md",true,[85,91,95,99,105,109,113,117,121,125,131],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Fbrief.md.tmpl","ASSET","资产文件",2109,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Fassets\u002Fbrief.md.tmpl",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Fsetup.sh.tmpl",8255,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Fassets\u002Fsetup.sh.tmpl",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"assets\u002Fsoul.md.tmpl",631,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Fassets\u002Fsoul.md.tmpl",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fexamples.md","REFERENCE","参考文档",10285,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Fexamples.md",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fintake.md",7951,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Fintake.md",{"path":110,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fkanban-setup.md",11120,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Fkanban-setup.md",{"path":114,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fmonitoring.md",7463,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Fmonitoring.md",{"path":118,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Frole-archetypes.md",12344,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Frole-archetypes.md",{"path":122,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Ftool-matrix.md",14427,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Ftool-matrix.md",{"path":126,"resourceType":127,"resourceTypeDesc":128,"sizeBytes":129,"sourceHtmlUrl":130},"scripts\u002Fbootstrap_pipeline.py","SCRIPT","脚本",18736,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Fscripts\u002Fbootstrap_pipeline.py",{"path":132,"resourceType":127,"resourceTypeDesc":128,"sizeBytes":133,"sourceHtmlUrl":134},"scripts\u002Fmonitor.py",6644,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Fscripts\u002Fmonitor.py",[136,146,154,162,170,178],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":140,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":145},"01M78RK6JGRPTD3TDSMTQWDQ9P","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":140,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":145},"01M78RK29KVRDQXSMVZX1GQTJN","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":140,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":145},"01M78RJPF3210Y5DA9VJ6JMMG6","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":140,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":145},"01M78RJH7X67C5AY8ZVS7RQNWJ","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FSKILL.md",[],[],{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":140,"licenseFileUrl":174,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":145},"01M78RBBAYMJ6T3ZMAYHCFM6G7","skill-creator-cc","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FSKILL.md",[],[],{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":182,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":186},"01M76VV9V2R9FZTVGMJZV7Y996","prd-writing-guide","Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FSKILL.md",[],[],"2026-11-12 13:55:43"]