[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJGWFTHCTTKXW1YGV7TS0P":3,"skill-same:01M6MJGWFTHCTTKXW1YGV7TS0P":93},{"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":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MJGWFTHCTTKXW1YGV7TS0P","solve-task",null,"Gather disciplined context for solving a task, then hand off to development. Use when the user asks to solve\u002Fimplement a task (\"solve PRI-4\", \"rag-reviewer:solve-task \u003Ckey or description>\", \"реши задачу X\"). Reads a keyed task from the reviewer store, pulls related\u002Fsimilar tasks and relevant code, distills a brief, and enters brainstorming. Requires the reviewer MCP server.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"solve task","task","solve","user","when","gather","for","hand","relevant","store","use","MCP","reviewer","brief","server","code","development","tasks","rag","brainstorming","implement","mcp server","2026-11-10 10:12:30",false,"---\nname: solve-task\ndescription: Gather disciplined context for solving a task, then hand off to development. Use when the user asks to solve\u002Fimplement a task (\"solve PRI-4\", \"rag-reviewer:solve-task \u003Ckey or description>\", \"реши задачу X\"). Reads a keyed task from the reviewer store, pulls related\u002Fsimilar tasks and relevant code, distills a brief, and enters brainstorming. Requires the reviewer MCP server.\n---\n\n# Solve Task\n\nGather the right context for a task, distill it into a brief, then enter the normal development\nworkflow. This skill does NOT plan or implement — it disciplines context-gathering and hands the\nbrief to `superpowers:brainstorming` (which leads to writing-plans → subagent-driven-development,\nor the execution strategy chosen in the startup survey (inline \u002F subagent \u002F lite)).\n\n## Inputs\n\n`$ARGUMENTS` is either:\n- a task key (e.g. `PRI-4`, matching the board's `key_pattern`), or\n- a free-text description (e.g. \"add a logout endpoint\").\n\n## Pipeline\n\n0. **Startup: survey + Preflight (index freshness + task-corpus warm-up).** Run this BEFORE anything else.\n   First resolve, once, the repo path (`git rev-parse --show-toplevel`) and the working branch\n   (`git branch --show-current`; if it is in `REVIEW_BRANCHES` use it, else the primary branch) —\n   step 3 reuses the same branch for `search_codebase`.\n\n   **Resolve `task_board` exactly once before any board call.** Read the repo `.review.yml` block:\n   its `task_board` mapping has priority; an absent block falls back to `get_board_config()`;\n   an explicit empty `task_board:` disables board work for this run. Keep the resolved\n   `{type, project, key_pattern, create_target, done_target, options}` value and **reuse this resolved value** in Step 1 and every board operation. Never call the deploy fallback when the\n   repo explicitly disables the board.\n\n   **Call `prepare_task_context(repo, key, branch, warm_board=True)` once here** — pass the\n   resolved `key` when `$ARGUMENTS` matches `key_pattern`, else board-less: pass the user's\n   formulation verbatim as `key` (the tool's `key` parameter is required and accepts free text\n   when no board key matches). It folds\n   the manual round trips below into one deterministic call and returns a single payload:\n   `preflight` (branch, indexed_sha, drift, summaries, chunks, graph_nodes — feeds Step 0.1\u002F0.4\n   below), `task_board`\u002F`task` (feeds Step 2), `related`\u002F`subsystems`\u002F`code`\u002F`test_exemplars`\n   (feeds Step 3), `gaps` (a list of `{section, reason, cause, cause_detail, remedy}` — branch on whether\n   `cause` is `unknown`, not on one non-`unknown` value; the classes are `storage_unavailable` |\n   `embedder_unavailable`, and `cause_detail` refines `storage_unavailable` only (`auth_failed` |\n   `missing_database` | `pool_exhausted` | `null`); copy every entry into **Constraints \u002F open questions**\n   in the Step 4 brief verbatim) and `warnings` (surface to the user). No source failure raises — a failed\n   section just adds a `gaps` entry, so the steps below stay fail-open.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fpreflight.md -->\n\n1. **Config.** Reuse the resolved value from preflight; do not read `.review.yml` or call\n   `get_board_config()` again. If no board resolved, continue board-less. For incomplete metadata\n   call `get_board_targets(board_type=\u003Ctask_board.type>,\n   project=\u003Ctask_board.project>, provider_options=\u003Ctask_board.options or {}>)`: select from\n   `targets` by `label`, and use option `required_for` \u002F `choices` to ask for missing `options`.\n   Never guess a target or an option and never branch on a board type.\n\n**Brief-building unit (Steps 2–4) runs on the chosen model.** Steps 2–4 (identify → gather → distill\n→ persist) are non-interactive; run them on the model chosen in the Step 0 startup survey. Dispatch\na subagent on the chosen model when a per-subagent model override is available (session-less tools +\n`Read`\u002F`Bash`\u002F`Glob`\u002F`Write` to persist the brief), passing the Step 0 `prepare_task_context` payload\ninto its dispatch prompt so it does not re-call `prepare_task_context` or the tools it already\nreplaced; otherwise build the brief inline. Details, the existing-artifacts pre-dispatch warn, the\n`Собран на:` marker line and the fail-open fallback are in `references\u002Fbrief-format.md` below.\n\n2. **Identify the task.**\n   - If `$ARGUMENTS` matches the board's `key_pattern`:\n     1. **Store-first.** Use `payload.task` from the Step 0 `prepare_task_context` call — it already\n        carries the task's own normalized content (`{key, aliases[], title, description, criteria[],\n        status, url}`) from the reviewer store, refreshed by that call's board warm-up. Call reviewer\n        `get_task(key, project=\u003Ctask_board.project>)` directly only as a fallback: when\n        `payload.task` is empty without a matching `gaps` entry explaining why, or when\n        `prepare_task_context` itself is unavailable — it returns the same normalized shape.\n        - **Hit** (a task object with a `key`, from `payload.task` or the fallback `get_task` call):\n          use it directly as the `TaskBrief`. The task is\n          already indexed (the preflight sync persisted it) — do NOT call `index_task`. Note in the\n          brief that the task data came from the reviewer store (after sync).\n          - **Thin criteria (optional, fail-open).** The store can return `criteria=[]`; requirements\n            normally live in `description`. If it has NO heading matching\n            `(?i)(критери|приёмк|acceptance)`, leave `criteria` empty and record the gap. Do NOT call `index_task`.\n        - **Miss** (`null` \u002F no `key`) AND a board is resolved: call generic incremental\n          `sync_board(board=\u003Ctask_board.project or null>, board_type=\u003Ctask_board.type>,\n          provider_options=\u003Ctask_board.options or {}>, limit=null, purge_orphaned=false)`, then\n          retry `get_task(key, project=\u003Ctask_board.project>)` once. Error or second miss →\n          board-less: treat `$ARGUMENTS` as the task description and record the gap.\n        - **Miss** AND no board: board-less — treat `$ARGUMENTS` as the task description.\n   - Otherwise: treat `$ARGUMENTS` as the task description; do not perform external task reads.\n\n   Store-first cuts the double-fetch: `prepare_task_context`'s board warm-up already pulled the whole\n   board into the reviewer store, and a miss gets one generic incremental sync\u002Fretry (fewer LLM\n   tokens and no provider-specific client dependency).\n\n3. **Gather context (best-effort, fail-open).** Any tool returning a \"(… unavailable)\" \u002F \"(ничего не\n   найдено)\" note or an error is non-fatal — continue. Details (subsystem prior, project scope,\n   related-task lookups, `search_codebase`, graph deepening, test exemplars, lazy expansion\u002FPR diff)\n   are in `references\u002Fcontext-gathering.md` below.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fcontext-gathering.md -->\n\n\u003C!-- include: _common\u002Ftool-usage.md -->\nUse the session-less tools above.\n\n   **Branch selection for `search_codebase`.**\n\n\u003C!-- include: _common\u002Fbranch-selection.md -->\n\n4. **Distill the solution brief.** Write a structured markdown brief whose only job is to seed\n   `brainstorming` — compact, scannable, nothing the implementer won't act on.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fbrief-format.md -->\n\n\u003C!-- include: solve-task\u002Freferences\u002Fmodes.md -->\n\n## Failure handling (fail-open)\n\n- No configured `task_board` \u002F failed generic sync \u002F task not found → board-less: build the brief\n  from `search_tasks` (if the corpus is warm) + `search_codebase` + the user's formulation; note\n  the missing task context.\n- Neo4j down → `get_task_context` \u002F `index_task` graph parts degrade (empty + warning); build the\n  brief from `search_tasks` + `search_codebase`.\n- Empty task corpus (no prior `rag-reviewer:sync-tasks` or reviews) → `search_tasks` is empty; use\n  `search_codebase` + the user's formulation and note the missing task context.\n- Postgres down → `search_codebase` \u002F `search_tasks` return empty; build the brief from the user's\n  formulation alone and note the missing task context; still hand off to brainstorming.\n- Never abort: with any gap, distill what you have, note the deficit in the brief, and still hand off\n  to brainstorming.\n- This skill reads task data only through the reviewer store and generic `sync_board`\u002Fretry. It\n  writes exactly two files: the brief under `docs\u002Fsuperpowers\u002Fbriefs\u002F` and the git-ignored\n  run-state file under `.superpowers\u002Fsolve-task\u002F`; nothing else in the repository.\n\n## Reporting a reviewer defect\n\n\u003C!-- include: _common\u002Fbug-reporting.md -->\n","# Solve Task\n\nGather the right context for a task, distill it into a brief, then enter the normal development\nworkflow. This skill does NOT plan or implement — it disciplines context-gathering and hands the\nbrief to `superpowers:brainstorming` (which leads to writing-plans → subagent-driven-development,\nor the execution strategy chosen in the startup survey (inline \u002F subagent \u002F lite)).\n\n## Inputs\n\n`$ARGUMENTS` is either:\n- a task key (e.g. `PRI-4`, matching the board's `key_pattern`), or\n- a free-text description (e.g. \"add a logout endpoint\").\n\n## Pipeline\n\n0. **Startup: survey + Preflight (index freshness + task-corpus warm-up).** Run this BEFORE anything else.\n   First resolve, once, the repo path (`git rev-parse --show-toplevel`) and the working branch\n   (`git branch --show-current`; if it is in `REVIEW_BRANCHES` use it, else the primary branch) —\n   step 3 reuses the same branch for `search_codebase`.\n\n   **Resolve `task_board` exactly once before any board call.** Read the repo `.review.yml` block:\n   its `task_board` mapping has priority; an absent block falls back to `get_board_config()`;\n   an explicit empty `task_board:` disables board work for this run. Keep the resolved\n   `{type, project, key_pattern, create_target, done_target, options}` value and **reuse this resolved value** in Step 1 and every board operation. Never call the deploy fallback when the\n   repo explicitly disables the board.\n\n   **Call `prepare_task_context(repo, key, branch, warm_board=True)` once here** — pass the\n   resolved `key` when `$ARGUMENTS` matches `key_pattern`, else board-less: pass the user's\n   formulation verbatim as `key` (the tool's `key` parameter is required and accepts free text\n   when no board key matches). It folds\n   the manual round trips below into one deterministic call and returns a single payload:\n   `preflight` (branch, indexed_sha, drift, summaries, chunks, graph_nodes — feeds Step 0.1\u002F0.4\n   below), `task_board`\u002F`task` (feeds Step 2), `related`\u002F`subsystems`\u002F`code`\u002F`test_exemplars`\n   (feeds Step 3), `gaps` (a list of `{section, reason, cause, cause_detail, remedy}` — branch on whether\n   `cause` is `unknown`, not on one non-`unknown` value; the classes are `storage_unavailable` |\n   `embedder_unavailable`, and `cause_detail` refines `storage_unavailable` only (`auth_failed` |\n   `missing_database` | `pool_exhausted` | `null`); copy every entry into **Constraints \u002F open questions**\n   in the Step 4 brief verbatim) and `warnings` (surface to the user). No source failure raises — a failed\n   section just adds a `gaps` entry, so the steps below stay fail-open.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fpreflight.md -->\n\n1. **Config.** Reuse the resolved value from preflight; do not read `.review.yml` or call\n   `get_board_config()` again. If no board resolved, continue board-less. For incomplete metadata\n   call `get_board_targets(board_type=\u003Ctask_board.type>,\n   project=\u003Ctask_board.project>, provider_options=\u003Ctask_board.options or {}>)`: select from\n   `targets` by `label`, and use option `required_for` \u002F `choices` to ask for missing `options`.\n   Never guess a target or an option and never branch on a board type.\n\n**Brief-building unit (Steps 2–4) runs on the chosen model.** Steps 2–4 (identify → gather → distill\n→ persist) are non-interactive; run them on the model chosen in the Step 0 startup survey. Dispatch\na subagent on the chosen model when a per-subagent model override is available (session-less tools +\n`Read`\u002F`Bash`\u002F`Glob`\u002F`Write` to persist the brief), passing the Step 0 `prepare_task_context` payload\ninto its dispatch prompt so it does not re-call `prepare_task_context` or the tools it already\nreplaced; otherwise build the brief inline. Details, the existing-artifacts pre-dispatch warn, the\n`Собран на:` marker line and the fail-open fallback are in `references\u002Fbrief-format.md` below.\n\n2. **Identify the task.**\n   - If `$ARGUMENTS` matches the board's `key_pattern`:\n     1. **Store-first.** Use `payload.task` from the Step 0 `prepare_task_context` call — it already\n        carries the task's own normalized content (`{key, aliases[], title, description, criteria[],\n        status, url}`) from the reviewer store, refreshed by that call's board warm-up. Call reviewer\n        `get_task(key, project=\u003Ctask_board.project>)` directly only as a fallback: when\n        `payload.task` is empty without a matching `gaps` entry explaining why, or when\n        `prepare_task_context` itself is unavailable — it returns the same normalized shape.\n        - **Hit** (a task object with a `key`, from `payload.task` or the fallback `get_task` call):\n          use it directly as the `TaskBrief`. The task is\n          already indexed (the preflight sync persisted it) — do NOT call `index_task`. Note in the\n          brief that the task data came from the reviewer store (after sync).\n          - **Thin criteria (optional, fail-open).** The store can return `criteria=[]`; requirements\n            normally live in `description`. If it has NO heading matching\n            `(?i)(критери|приёмк|acceptance)`, leave `criteria` empty and record the gap. Do NOT call `index_task`.\n        - **Miss** (`null` \u002F no `key`) AND a board is resolved: call generic incremental\n          `sync_board(board=\u003Ctask_board.project or null>, board_type=\u003Ctask_board.type>,\n          provider_options=\u003Ctask_board.options or {}>, limit=null, purge_orphaned=false)`, then\n          retry `get_task(key, project=\u003Ctask_board.project>)` once. Error or second miss →\n          board-less: treat `$ARGUMENTS` as the task description and record the gap.\n        - **Miss** AND no board: board-less — treat `$ARGUMENTS` as the task description.\n   - Otherwise: treat `$ARGUMENTS` as the task description; do not perform external task reads.\n\n   Store-first cuts the double-fetch: `prepare_task_context`'s board warm-up already pulled the whole\n   board into the reviewer store, and a miss gets one generic incremental sync\u002Fretry (fewer LLM\n   tokens and no provider-specific client dependency).\n\n3. **Gather context (best-effort, fail-open).** Any tool returning a \"(… unavailable)\" \u002F \"(ничего не\n   найдено)\" note or an error is non-fatal — continue. Details (subsystem prior, project scope,\n   related-task lookups, `search_codebase`, graph deepening, test exemplars, lazy expansion\u002FPR diff)\n   are in `references\u002Fcontext-gathering.md` below.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fcontext-gathering.md -->\n\n\u003C!-- include: _common\u002Ftool-usage.md -->\nUse the session-less tools above.\n\n   **Branch selection for `search_codebase`.**\n\n\u003C!-- include: _common\u002Fbranch-selection.md -->\n\n4. **Distill the solution brief.** Write a structured markdown brief whose only job is to seed\n   `brainstorming` — compact, scannable, nothing the implementer won't act on.\n\n\u003C!-- include: solve-task\u002Freferences\u002Fbrief-format.md -->\n\n\u003C!-- include: solve-task\u002Freferences\u002Fmodes.md -->\n\n## Failure handling (fail-open)\n\n- No configured `task_board` \u002F failed generic sync \u002F task not found → board-less: build the brief\n  from `search_tasks` (if the corpus is warm) + `search_codebase` + the user's formulation; note\n  the missing task context.\n- Neo4j down → `get_task_context` \u002F `index_task` graph parts degrade (empty + warning); build the\n  brief from `search_tasks` + `search_codebase`.\n- Empty task corpus (no prior `rag-reviewer:sync-tasks` or reviews) → `search_tasks` is empty; use\n  `search_codebase` + the user's formulation and note the missing task context.\n- Postgres down → `search_codebase` \u002F `search_tasks` return empty; build the brief from the user's\n  formulation alone and note the missing task context; still hand off to brainstorming.\n- Never abort: with any gap, distill what you have, note the deficit in the brief, and still hand off\n  to brainstorming.\n- This skill reads task data only through the reviewer store and generic `sync_board`\u002Fretry. It\n  writes exactly two files: the brief under `docs\u002Fsuperpowers\u002Fbriefs\u002F` and the git-ignored\n  run-state file under `.superpowers\u002Fsolve-task\u002F`; nothing else in the repository.\n\n## Reporting a reviewer defect\n\n\u003C!-- include: _common\u002Fbug-reporting.md -->\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task",490,"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 02:12:02",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill solve-task",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill solve-task",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill solve-task","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002FSKILL.md",true,[75,81,85,89],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fbrief-format.md","REFERENCE","参考文档",8541,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002Freferences\u002Fbrief-format.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fcontext-gathering.md",7681,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002Freferences\u002Fcontext-gathering.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fmodes.md",6747,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002Freferences\u002Fmodes.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fpreflight.md",14272,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fsolve-task\u002Freferences\u002Fpreflight.md",[94,102,109,116,141,166],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":101},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":101},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":101},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":46},"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",[],[123,124,125,126,127,128,129,130,131,132,133,28,134,135,36,136,137,138,139,140],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","io","change","cli","merge","past",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":46},"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",[],[148,149,150,136,151,152,153,154,155,156,157,158,159,160,128,161,162,163,164,165],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":179,"publishedAt":46},"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",[172,175,176],{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":177,"categoryName":178,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[168,180,181,182,183,184,185,162,186,129,187,188,35,189,28,190,45,191,192,193],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","song","image","schedule","api","publish"]