[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVPHM7PV8XHVB6YFV47RDF":3,"skill-same:01M6JVPHM7PV8XHVB6YFV47RDF":65},{"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":18,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6JVPHM7PV8XHVB6YFV47RDF","dispatching-parallel-agents",null,"Use when facing 2+ independent tasks without a written plan, with no conflicting shared mutable state or sequential dependencies, where parallel delegation beats inline cost; otherwise inline. Planned tasks use subagent-driven-development.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fdispatching-parallel-agents\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"dispatching parallel agents","parallel agents","parallel","when","tasks","inline","with","driven","shared","dependencies","cost","use","subagent","plan","delegation","state","development","2026-11-10 10:12:30",false,"---\nname: dispatching-parallel-agents\ndescription: \"Use when facing 2+ independent tasks without a written plan, with no conflicting shared mutable state or sequential dependencies, where parallel delegation beats inline cost; otherwise inline. Planned tasks use subagent-driven-development.\"\n---\n\n# Dispatching Parallel Agents\n\n## Purpose\n\nUse parallel children for two or more ad-hoc, bounded tasks only when their\nindependence is already credible and concurrency is worth the coordination.\nParallelism changes elapsed time; it does not relax evidence, ownership, or\ncompletion requirements.\n\n## Dispatch Gate\n\nDispatch only when all are true:\n\n- there are `2+` distinct tasks or evidence questions;\n- one task's result is not needed to define or start another;\n- the tasks do not require overlapping writes or the same mutable resource;\n- a shared root cause is unlikely based on current evidence;\n- each result can be returned with bounded evidence and unresolved unknowns;\n- available concurrency and expected work justify coordination cost.\n\nKeep work inline when decomposition is still exploratory, failures may share a\nroot cause, full-system context is required, or tasks are too small to repay the\nhandoff. A written implementation plan routes to\n`aegis:subagent-driven-development`, not this ad-hoc workflow.\n\n## Context And Ownership\n\nChoose the live host's context inheritance mode deliberately. Give each child\nthe minimum sufficient instructions and evidence; do not rely on accidental\ninheritance or assume that context must never be inherited.\n\nEach task packet states:\n\n- goal and question to resolve;\n- allowed files, systems, and side effects;\n- known facts and evidence locations;\n- constraints, non-goals, and stop condition;\n- expected result shape, including unknowns and verification refs.\n\nIsolated model context does not imply an isolated filesystem, process, Git\nrepository, credential, rate limit, or external service. Prefer read-only\ninvestigation. If children may edit, assign disjoint write ownership explicitly.\nThe coordinator owns staging, commits, branches, worktrees, integration, and other Git lifecycle mutations.\n\n## Execution\n\n1. Establish the minimum common baseline and record evidence for the task split.\n2. Dispatch one bounded task per independent domain, within host concurrency\n   limits.\n3. Optionally continue coordinator work that does not race child reads or writes.\n4. On return, check evidence freshness, unknowns, overlapping assumptions, and\n   visible workspace changes.\n5. Synthesize disagreements before acting. If results reveal coupling, stop\n   parallel mutation and return the work to one owner.\n6. For edits, run integrated verification after accepted changes are combined.\n   For read-only work, validate the synthesis against the cited sources.\n\nThe coordinator owns the concurrency budget. Children do not delegate\nrecursively unless their packet explicitly permits it. A failed, cancelled, or\ntimed-out child contributes any available partial evidence; otherwise record no\nresult and the unresolved unknowns. Retry only with a materially different\npacket or serialize the task.\n\nChild output is evidence or a proposal, not a `GateDecision`, completion authority, or permission for external action.\n\n## Common Failure Modes\n\n- Separate files are treated as proof of separate root causes.\n- Children receive broad conversation history instead of bounded task context.\n- Multiple children edit the same owner or mutate shared services concurrently.\n- A child report is accepted without inspecting evidence or current files.\n- Parallel work is used for a written plan and bypasses its review checkpoints.\n- The coordinator verifies each result alone but never checks the integrated\n  state.\n\nWhen any of these appears, narrow the packets, serialize the shared portion, or\nreturn to the owning debugging or plan workflow.\n","# Dispatching Parallel Agents\n\n## Purpose\n\nUse parallel children for two or more ad-hoc, bounded tasks only when their\nindependence is already credible and concurrency is worth the coordination.\nParallelism changes elapsed time; it does not relax evidence, ownership, or\ncompletion requirements.\n\n## Dispatch Gate\n\nDispatch only when all are true:\n\n- there are `2+` distinct tasks or evidence questions;\n- one task's result is not needed to define or start another;\n- the tasks do not require overlapping writes or the same mutable resource;\n- a shared root cause is unlikely based on current evidence;\n- each result can be returned with bounded evidence and unresolved unknowns;\n- available concurrency and expected work justify coordination cost.\n\nKeep work inline when decomposition is still exploratory, failures may share a\nroot cause, full-system context is required, or tasks are too small to repay the\nhandoff. A written implementation plan routes to\n`aegis:subagent-driven-development`, not this ad-hoc workflow.\n\n## Context And Ownership\n\nChoose the live host's context inheritance mode deliberately. Give each child\nthe minimum sufficient instructions and evidence; do not rely on accidental\ninheritance or assume that context must never be inherited.\n\nEach task packet states:\n\n- goal and question to resolve;\n- allowed files, systems, and side effects;\n- known facts and evidence locations;\n- constraints, non-goals, and stop condition;\n- expected result shape, including unknowns and verification refs.\n\nIsolated model context does not imply an isolated filesystem, process, Git\nrepository, credential, rate limit, or external service. Prefer read-only\ninvestigation. If children may edit, assign disjoint write ownership explicitly.\nThe coordinator owns staging, commits, branches, worktrees, integration, and other Git lifecycle mutations.\n\n## Execution\n\n1. Establish the minimum common baseline and record evidence for the task split.\n2. Dispatch one bounded task per independent domain, within host concurrency\n   limits.\n3. Optionally continue coordinator work that does not race child reads or writes.\n4. On return, check evidence freshness, unknowns, overlapping assumptions, and\n   visible workspace changes.\n5. Synthesize disagreements before acting. If results reveal coupling, stop\n   parallel mutation and return the work to one owner.\n6. For edits, run integrated verification after accepted changes are combined.\n   For read-only work, validate the synthesis against the cited sources.\n\nThe coordinator owns the concurrency budget. Children do not delegate\nrecursively unless their packet explicitly permits it. A failed, cancelled, or\ntimed-out child contributes any available partial evidence; otherwise record no\nresult and the unresolved unknowns. Retry only with a materially different\npacket or serialize the task.\n\nChild output is evidence or a proposal, not a `GateDecision`, completion authority, or permission for external action.\n\n## Common Failure Modes\n\n- Separate files are treated as proof of separate root causes.\n- Children receive broad conversation history instead of bounded task context.\n- Multiple children edit the same owner or mutate shared services concurrently.\n- A child report is accepted without inspecting evidence or current files.\n- Parallel work is used for a written plan and bypasses its review checkpoints.\n- The coordinator verifies each result alone but never checks the integrated\n  state.\n\nWhen any of these appears, narrow the packets, serialize the shared portion, or\nreturn to the owning debugging or plan workflow.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fdispatching-parallel-agents",483,"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-13 02:16:32",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dispatching-parallel-agents",{"tool":57,"command":58},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dispatching-parallel-agents",{"tool":60,"command":61},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dispatching-parallel-agents","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fdispatching-parallel-agents\u002FSKILL.md",true,[],[66,74,81,88,114,138],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":73},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":73},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":73},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":36},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[95,96,97,98,99,100,101,102,103,104,105,22,106,107,108,109,110,111,112,113],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":36},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[121,122,123,109,25,124,125,126,127,128,129,130,131,132,100,133,134,135,136,137],"deja reflect","reflect","review","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":155,"publishedAt":36},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[144,149,152],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":150,"categoryName":151,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":153,"categoryName":154,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000010","后端与接口",[140,156,157,158,159,160,161,134,162,101,163,164,165,166,22,167,168,169,170,171],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]