[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C3NPFX46NJWN2BJMCYZFW0":3,"skill-same:01M7C3NPFX46NJWN2BJMCYZFW0":131},{"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":61,"commitSha":62,"skillDirectory":63,"forksCount":13,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":66,"install":67,"resources":80},"01M7C3NPFX46NJWN2BJMCYZFW0","kanban-video-orchestrator",null,"Plan and run multi-agent video production pipelines.","fengwhang\u002Fmercury","fengwhang","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F325040254?v=4","01M7C3K54Y41KVGPHEMKEP9X70","01M7C3K55NTZ4B36YP2JY1NMJ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: kanban-video-orchestrator\ndescription: Plan and run multi-agent video production pipelines.\nversion: 1.0.0\nauthor: [SHL0MS, alt-glitch]\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  mercury:\n    tags: [video, kanban, multi-agent, orchestration, production-pipeline]\n    related_skills: [ascii-video, manim-video, p5js, comfyui, touchdesigner-mcp, pixel-art, ascii-art, songwriting-and-ai-music, heartmula, songsee, 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:\u002Fabs\u002Fpath` 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 Mercury 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`, `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 Mercury profile via `mercury 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 `mercury 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\nmercury kanban watch --tenant \u003Cproject-tenant>     # live events\nmercury kanban list  --tenant \u003Cproject-tenant>     # board snapshot\nmercury 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 `mercury kanban create` call to a specialist profile. The kanban\n   orchestration guidance auto-injected into every kanban worker's system\n   prompt 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 `$MERCURY_HOME\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 Mercury 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`, `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 Mercury profile via `mercury 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 `mercury 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\nmercury kanban watch --tenant \u003Cproject-tenant>     # live events\nmercury kanban list  --tenant \u003Cproject-tenant>     # board snapshot\nmercury 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 `mercury kanban create` call to a specialist profile. The kanban\n   orchestration guidance auto-injected into every kanban worker's system\n   prompt 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 `$MERCURY_HOME\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":57,"description":7},[24,25],"SHL0MS","alt-glitch","1.0.0",{"mercury":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:\u002Fabs\u002Fpath` 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],"ascii-video","manim-video","p5js","comfyui","touchdesigner-mcp","pixel-art","ascii-art","songwriting-and-ai-music","heartmula","songsee","youtube-content","claude-design","excalidraw","architecture-diagram","concept-diagrams","baoyu-comic","baoyu-infographic","humanizer","gif-search","meme-generation",[58,59,60],"linux","macos","windows","main","94a12cab2ce32e2020d179b5d579d0cbcbd0f206","hermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury","https:\u002F\u002Fgithub.com\u002Ffengwhang","2026-10-09 08:26:42",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add fengwhang\u002Fmercury --skill kanban-video-orchestrator",{"tool":73,"command":74},"bunx","bunx skills add fengwhang\u002Fmercury --skill kanban-video-orchestrator",{"tool":76,"command":77},"pnpm","pnpm dlx skills add fengwhang\u002Fmercury --skill kanban-video-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002FSKILL.md",true,[81,87,91,95,101,105,109,113,117,121,127],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"assets\u002Fbrief.md.tmpl","ASSET","资产文件",2109,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Fassets\u002Fbrief.md.tmpl",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Fsetup.sh.tmpl",8658,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Fassets\u002Fsetup.sh.tmpl",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Fsoul.md.tmpl",631,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Fassets\u002Fsoul.md.tmpl",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fexamples.md","REFERENCE","参考文档",10343,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Fexamples.md",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fintake.md",7951,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Fintake.md",{"path":106,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fkanban-setup.md",11446,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Fkanban-setup.md",{"path":110,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fmonitoring.md",7492,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Fmonitoring.md",{"path":114,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Frole-archetypes.md",12729,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Frole-archetypes.md",{"path":118,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Ftool-matrix.md",13624,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Freferences\u002Ftool-matrix.md",{"path":122,"resourceType":123,"resourceTypeDesc":124,"sizeBytes":125,"sourceHtmlUrl":126},"scripts\u002Fbootstrap_pipeline.py","SCRIPT","脚本",18740,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Fscripts\u002Fbootstrap_pipeline.py",{"path":128,"resourceType":123,"resourceTypeDesc":124,"sizeBytes":129,"sourceHtmlUrl":130},"scripts\u002Fmonitor.py",6890,"https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fcreative\u002Fkanban-video-orchestrator\u002Fscripts\u002Fmonitor.py",[132,139,146,153,159,166],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":18},"01M7C4BTY3ND38CN200ZCTH6NV","greet","A greeting skill for testing","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Fmarketplace\u002Ffixtures\u002Fvalid-marketplace\u002Fplugins\u002Fhello-plugin\u002Fskills\u002Fgreet\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":18},"01M7C4BSNZTPW8JR5NGCQXGSEZ","valid-skill","A valid skill for testing purposes.","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Ffixtures\u002Fskills\u002Fvalid-skill\u002FSKILL.md",[],[],{"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":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":18},"01M7C4BRA7J8C06KSVW100F1W1","unknown-field","A skill with an unknown frontmatter field.","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Ffixtures\u002Fskills\u002Funknown-field\u002FSKILL.md",[],[],{"skillNo":154,"name":155,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":18},"01M7C4BNB04KQGCJ835JE8AR13","no-frontmatter","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Ffixtures\u002Fskills\u002Fno-frontmatter\u002FSKILL.md",[],[],{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":18},"01M7C4BM38TZFYT1AJ6SKHPZZ2","child-skill","A nested skill in a subdirectory.","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Ffixtures\u002Fskills\u002Fnested\u002Fchild-skill\u002FSKILL.md",[],[],{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":18},"01M7C4BJDN7RFFCM28CGX15Q97","different-name","A skill with a name that doesn't match the directory.","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Ffixtures\u002Fskills\u002Fname-mismatch\u002FSKILL.md",[],[]]