[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP1GHWCFY0TNRSBCV5RMR5":3,"skill-same:01M6MP1GHWCFY0TNRSBCV5RMR5":71},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":70},"01M6MP1GHWCFY0TNRSBCV5RMR5","unattended",null,"Starts the Clean Room startup wizard in bounded unattended controller mode for authorized source-to-implementation work with finite loop limits and safety stops.","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\u002Fwhit3rabbit\u002Fclean-room-skill\u002Fskills\u002Funattended\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"output","limits","bounded","source","for","clean room","mode","true","with","startup","scope","clean","max","implementation","work","loop","wizard","Safety","controller","2026-11-10 10:12:30",false,"---\nname: unattended\ndescription: Starts the Clean Room startup wizard in bounded unattended controller mode for authorized source-to-implementation work with finite loop limits and safety stops.\nargument-hint: [authorized source scope, separated output roots, optional max iterations]\ndisable-model-invocation: true\n---\n\n# Clean Room Unattended\n\nStart the clean-room startup wizard with `controller_policy.mode` fixed to `unattended`.\n\nIn Pi, this entry point is invoked as `\u002Fskill:unattended`.\n\nUse the canonical `clean-room` skill workflow and references in this plugin. Read `skills\u002Fclean-room\u002Freferences\u002FCONTROLLER-LOOP.md` before defining unattended loop behavior. Preserve the same clean-room boundary, role separation, artifact schemas, leakage rules, implementation-root rules, and hook expectations.\n\nBefore asking setup or preflight questions, use the canonical `clean-room` \"Run State Discovery Before Wizard\" rules. Resolve explicit artifact paths first, then current-repo `.clean-room\u002Flocal-state.json`, then configured clean-room roots, then bounded `~\u002FDocuments\u002FCleanRoom\u002Ftask-*` (legacy) and `~\u002FDocuments\u002FCleanRoom\u002F*\u002Ftasks\u002Ftask-*` (project layout) candidates. Treat target-repo `.clean-room\u002Ftasks\u002F` as noncanonical unless explicitly provided or named by the local pointer. If a valid `task-manifest.json` exists, route to `resume-cr`. If a `task-manifest.json` exists but is invalid or legacy-shaped, stop and report its exact path and validation errors. If a valid canonical `preflight-goal.json` exists without a manifest, continue at source\u002Fdestination discovery and manifest creation. If a preflight artifact exists but is invalid, stop with schema errors instead of restarting preflight. If a project is found with only completed tasks and the user wants more work, create the next task in that project by default. If multiple candidates are found without an explicit path, list them and stop for selection.\n\nThis `unattended` skill runs on every supported runtime; only the optional dynamic-workflow shortcut below is Claude Code specific. Role execution preference, most to least preferred:\n\n1. In-harness roles with fresh context and no external process spawn. In Claude Code this is the cost-free dynamic workflow front door `\u002Fclean-room:clean-room-loop` (in-session `agent()` subagents, new context per role; self-bootstraps init, preflight, and decomposition). It is Claude Code only and installs project-local (`.claude\u002Fworkflows\u002F`); it gives context-level separation, not the OS-enforced wall. On non-Claude harnesses, run each role as a fresh in-harness subagent or skill session orchestrated from the controller.\n2. Durable runner with external process dispatch: last resort, or when you specifically need the OS-enforced wall. Use `clean-room-skill run --task-manifest \u003Cpath> --agent-commands \u003Cadapter>` (spawns the harness's own CLI, `shell: false`) on Codex, Pi, and every non-Claude runtime; `--agent-runtime claude` spawns `claude -p` per role and is Claude only and per-token, so treat it as the last resort even on Claude Code. Never pass `--agent-runtime claude` on a non-Claude runtime. Launch the runner only after the manifest has `loop_context` with an approved pending or gap unit. For ccsilo\u002FOpenRouter sessions, use `clean-room-skill run --task-manifest \u003Cpath> --ccsilo [variant]` instead of manual `--agent-runtime claude`, `--agent-config-dir`, or `CLEAN_ROOM_CLAUDE_EXECUTABLE` wiring. Never write `ANTHROPIC_AUTH_TOKEN` or API keys into ccsilo or Claude settings files. If an unattended manifest lacks `loop_context`, treat it as incomplete outer-loop state: finish decomposition or selected-slice approval first, or stop with the missing outer-loop fields instead of launching the runner. If `clean-room-skill` is not on `PATH`, immediately use `npx clean-room-skill@latest run --task-manifest \u003Cpath> --agent-runtime claude` instead of searching for the installed package. Do not search plugin cache paths for schema files, and do not pass `--schema-dir \u002Fdev\u002Fnull`. The runner uses bundled schemas by default; pass `--schema-dir` only when the user provides a real schema directory. The main conversation must not perform Agent 1, Agent 2, Agent 3, or Agent 4 work once runner-ready unattended state exists. Do not edit `task-manifest.json` unit statuses in the main conversation; unit completion must come from runner-managed role artifacts and contaminated-side coverage verification. Do not ask to continue while `controller_policy.mode` is `unattended`, the iteration budget remains, and approved pending or gap units remain. If Claude role-agent dispatch or the runner is unavailable, stop with `BLOCKERS: Claude role-agent dispatch unavailable` instead of falling back to main-chat execution.\n\nLoad or create `preflight-goal.json` first. Unattended mode requires a complete goal contract with no blocking or non-blocking `open_questions`, `controller_policy.unattended_allowed_after_preflight: true`, finite `controller_policy.max_iterations`, and `intent_confirmation` showing the end goal, target stack, and controller mode came from explicit user answers.\n\nDo not assume end goal, target language, runtime, framework, package manager, test framework, license policy, dependency policy, exactness policy, output directory, or feature add\u002Fremove policy during the unattended loop. Source language and build tooling are not destination choices. If the user's end goal or target stack is unknown, leave blocking `open_questions`, keep unattended disabled, and stop on ambiguity instead of inventing product decisions.\n\nGather only required setup facts:\n\n- Authorization statement, requester, allowed actions, prohibited actions, and evidence handling.\n- Artifact base root, defaulting the task root to `~\u002FDocuments\u002FCleanRoom\u002F\u003Cproject>\u002Ftasks\u002F\u003Ctask-id>\u002F`. If the user does not provide an explicitly approved neutral task ID, generate one as `task-` plus 8 lowercase hex characters. Do not derive task IDs or output directory names from source folder names.\n- Project grouping, following the canonical `clean-room` project layout rules: `\u003Cbase>\u002F\u003Cproject>\u002Ftasks\u002F\u003Ctask-id>\u002F` with one shared `\u003Cbase>\u002F\u003Cproject>\u002Fimplementation\u002F` root, an existing project from `.clean-room\u002Flocal-state.json` when available, otherwise a neutral project name (`proj-` plus 8 lowercase hex unless the user supplies an approved neutral name, matching `[a-z0-9][a-z0-9-]{0,63}`, never source-derived), and at most one active task per project. Use legacy flat `\u003Cbase>\u002F\u003Ctask-id>\u002F` roots only when the user explicitly chooses single-task compatibility.\n- Source roots, contaminated artifact root, clean artifact root, clean implementation root, quarantine root, and optional public or destination reference roots.\n- Explicit user-confirmed end goal, target stack, destination constraints, dependency\u002Flicense policy, exactness policy, feature policy, code hygiene policy, and output policy from `preflight-goal.json`.\n- Target schema profile: `openspec-delta`, `gsd-planning-package`, `speckit-feature-folder`, or `kiro-spec-folder`.\n- Default model plus optional clean, contaminated, or per-role overrides.\n- Finite maximum iteration count for the inner clean-room loop from `preflight-goal.json`.\n- Loop context for the selected spec slice: parent loop ref, spec slice ref, approved scope refs, acceptance refs, and public surface refs.\n\nBefore indexing or artifact generation, confirm that source roots, contaminated artifact roots, clean artifact roots, clean implementation roots, approved public reference roots, and schema directory are separate paths, and that clean\u002Fcontaminated\u002Fimplementation root names are not source-derived. Stop if authorization is unclear, if clean and contaminated roots overlap, if implementation roots overlap another trust-domain root, or if root paths contain source root basenames or meaningful non-generic source-name tokens. Clean roles must receive `clean-run-context.json` and, when enabled, `role-session-brief.json`; they must not receive the full `task-manifest.json`. Agent 0 must influence clean roles only through durable sanitized artifacts.\n\nRecord `preflight_goal_ref`, `preflight_goal_sha256`, required `handoff_sequence`, `controller_policy.mode` as `unattended`, `max_units_per_iteration` as `1`, and `max_iterations` as the selected finite value. Record `loop_context` with `parent_loop_kind: \"spec-development\"`, `child_loop_kind: \"clean-room\"`, `return_to: \"outer-spec-loop\"`, the selected `spec_slice_ref`, and bounded approved scope refs. Include these stop conditions: `authorization-missing`, `scope-change`, `contamination-suspected`, `schema-validation-failed`, `leakage-scan-failed`, `unit-blocked`, `implementation-complete`, `coverage-complete`, `iteration-limit-reached`, `spec-slice-complete`, `spec-slice-blocked`, `spec-delta-required`, `no-progress-detected`, `repeated-unit-selection`, and `clean-room-returned`.\n\nThe inner loop returns only after Agent 0 consumes the terminal Agent 3 report, any configured Agent 4 `polish-report.json`, and completes contaminated-side coverage verification. Write `clean-room-result.json` before returning control to the outer spec loop.\n\nFor multi-file source scope, guide agent zero\u002Fcontroller to run `skills\u002Fclean-room\u002Fscripts\u002Fbuild_source_index.py` as preflight outside clean-room role sessions. Store `source-index.json` only under the contaminated artifact root and never include it in clean handoff packages. If no indexable source code exists and screenshots\u002Fimages are the only authorized evidence, unattended mode may use `skills\u002Fclean-room\u002Fscripts\u002Fbuild_visual_index.py` only after preflight already answers the visual-fallback questions with no open questions. Store `visual-index.json` only under the contaminated artifact root and include visual roots in `CLEAN_ROOM_SOURCE_ROOTS` (ensuring screenshot evidence directories are explicitly added to `CLEAN_ROOM_SOURCE_ROOTS` during execution so that path-aware read hooks such as `hooks\u002Fdeny-clean-source-read.py` can protect them as expected).\n","# Clean Room Unattended\n\nStart the clean-room startup wizard with `controller_policy.mode` fixed to `unattended`.\n\nIn Pi, this entry point is invoked as `\u002Fskill:unattended`.\n\nUse the canonical `clean-room` skill workflow and references in this plugin. Read `skills\u002Fclean-room\u002Freferences\u002FCONTROLLER-LOOP.md` before defining unattended loop behavior. Preserve the same clean-room boundary, role separation, artifact schemas, leakage rules, implementation-root rules, and hook expectations.\n\nBefore asking setup or preflight questions, use the canonical `clean-room` \"Run State Discovery Before Wizard\" rules. Resolve explicit artifact paths first, then current-repo `.clean-room\u002Flocal-state.json`, then configured clean-room roots, then bounded `~\u002FDocuments\u002FCleanRoom\u002Ftask-*` (legacy) and `~\u002FDocuments\u002FCleanRoom\u002F*\u002Ftasks\u002Ftask-*` (project layout) candidates. Treat target-repo `.clean-room\u002Ftasks\u002F` as noncanonical unless explicitly provided or named by the local pointer. If a valid `task-manifest.json` exists, route to `resume-cr`. If a `task-manifest.json` exists but is invalid or legacy-shaped, stop and report its exact path and validation errors. If a valid canonical `preflight-goal.json` exists without a manifest, continue at source\u002Fdestination discovery and manifest creation. If a preflight artifact exists but is invalid, stop with schema errors instead of restarting preflight. If a project is found with only completed tasks and the user wants more work, create the next task in that project by default. If multiple candidates are found without an explicit path, list them and stop for selection.\n\nThis `unattended` skill runs on every supported runtime; only the optional dynamic-workflow shortcut below is Claude Code specific. Role execution preference, most to least preferred:\n\n1. In-harness roles with fresh context and no external process spawn. In Claude Code this is the cost-free dynamic workflow front door `\u002Fclean-room:clean-room-loop` (in-session `agent()` subagents, new context per role; self-bootstraps init, preflight, and decomposition). It is Claude Code only and installs project-local (`.claude\u002Fworkflows\u002F`); it gives context-level separation, not the OS-enforced wall. On non-Claude harnesses, run each role as a fresh in-harness subagent or skill session orchestrated from the controller.\n2. Durable runner with external process dispatch: last resort, or when you specifically need the OS-enforced wall. Use `clean-room-skill run --task-manifest \u003Cpath> --agent-commands \u003Cadapter>` (spawns the harness's own CLI, `shell: false`) on Codex, Pi, and every non-Claude runtime; `--agent-runtime claude` spawns `claude -p` per role and is Claude only and per-token, so treat it as the last resort even on Claude Code. Never pass `--agent-runtime claude` on a non-Claude runtime. Launch the runner only after the manifest has `loop_context` with an approved pending or gap unit. For ccsilo\u002FOpenRouter sessions, use `clean-room-skill run --task-manifest \u003Cpath> --ccsilo [variant]` instead of manual `--agent-runtime claude`, `--agent-config-dir`, or `CLEAN_ROOM_CLAUDE_EXECUTABLE` wiring. Never write `ANTHROPIC_AUTH_TOKEN` or API keys into ccsilo or Claude settings files. If an unattended manifest lacks `loop_context`, treat it as incomplete outer-loop state: finish decomposition or selected-slice approval first, or stop with the missing outer-loop fields instead of launching the runner. If `clean-room-skill` is not on `PATH`, immediately use `npx clean-room-skill@latest run --task-manifest \u003Cpath> --agent-runtime claude` instead of searching for the installed package. Do not search plugin cache paths for schema files, and do not pass `--schema-dir \u002Fdev\u002Fnull`. The runner uses bundled schemas by default; pass `--schema-dir` only when the user provides a real schema directory. The main conversation must not perform Agent 1, Agent 2, Agent 3, or Agent 4 work once runner-ready unattended state exists. Do not edit `task-manifest.json` unit statuses in the main conversation; unit completion must come from runner-managed role artifacts and contaminated-side coverage verification. Do not ask to continue while `controller_policy.mode` is `unattended`, the iteration budget remains, and approved pending or gap units remain. If Claude role-agent dispatch or the runner is unavailable, stop with `BLOCKERS: Claude role-agent dispatch unavailable` instead of falling back to main-chat execution.\n\nLoad or create `preflight-goal.json` first. Unattended mode requires a complete goal contract with no blocking or non-blocking `open_questions`, `controller_policy.unattended_allowed_after_preflight: true`, finite `controller_policy.max_iterations`, and `intent_confirmation` showing the end goal, target stack, and controller mode came from explicit user answers.\n\nDo not assume end goal, target language, runtime, framework, package manager, test framework, license policy, dependency policy, exactness policy, output directory, or feature add\u002Fremove policy during the unattended loop. Source language and build tooling are not destination choices. If the user's end goal or target stack is unknown, leave blocking `open_questions`, keep unattended disabled, and stop on ambiguity instead of inventing product decisions.\n\nGather only required setup facts:\n\n- Authorization statement, requester, allowed actions, prohibited actions, and evidence handling.\n- Artifact base root, defaulting the task root to `~\u002FDocuments\u002FCleanRoom\u002F\u003Cproject>\u002Ftasks\u002F\u003Ctask-id>\u002F`. If the user does not provide an explicitly approved neutral task ID, generate one as `task-` plus 8 lowercase hex characters. Do not derive task IDs or output directory names from source folder names.\n- Project grouping, following the canonical `clean-room` project layout rules: `\u003Cbase>\u002F\u003Cproject>\u002Ftasks\u002F\u003Ctask-id>\u002F` with one shared `\u003Cbase>\u002F\u003Cproject>\u002Fimplementation\u002F` root, an existing project from `.clean-room\u002Flocal-state.json` when available, otherwise a neutral project name (`proj-` plus 8 lowercase hex unless the user supplies an approved neutral name, matching `[a-z0-9][a-z0-9-]{0,63}`, never source-derived), and at most one active task per project. Use legacy flat `\u003Cbase>\u002F\u003Ctask-id>\u002F` roots only when the user explicitly chooses single-task compatibility.\n- Source roots, contaminated artifact root, clean artifact root, clean implementation root, quarantine root, and optional public or destination reference roots.\n- Explicit user-confirmed end goal, target stack, destination constraints, dependency\u002Flicense policy, exactness policy, feature policy, code hygiene policy, and output policy from `preflight-goal.json`.\n- Target schema profile: `openspec-delta`, `gsd-planning-package`, `speckit-feature-folder`, or `kiro-spec-folder`.\n- Default model plus optional clean, contaminated, or per-role overrides.\n- Finite maximum iteration count for the inner clean-room loop from `preflight-goal.json`.\n- Loop context for the selected spec slice: parent loop ref, spec slice ref, approved scope refs, acceptance refs, and public surface refs.\n\nBefore indexing or artifact generation, confirm that source roots, contaminated artifact roots, clean artifact roots, clean implementation roots, approved public reference roots, and schema directory are separate paths, and that clean\u002Fcontaminated\u002Fimplementation root names are not source-derived. Stop if authorization is unclear, if clean and contaminated roots overlap, if implementation roots overlap another trust-domain root, or if root paths contain source root basenames or meaningful non-generic source-name tokens. Clean roles must receive `clean-run-context.json` and, when enabled, `role-session-brief.json`; they must not receive the full `task-manifest.json`. Agent 0 must influence clean roles only through durable sanitized artifacts.\n\nRecord `preflight_goal_ref`, `preflight_goal_sha256`, required `handoff_sequence`, `controller_policy.mode` as `unattended`, `max_units_per_iteration` as `1`, and `max_iterations` as the selected finite value. Record `loop_context` with `parent_loop_kind: \"spec-development\"`, `child_loop_kind: \"clean-room\"`, `return_to: \"outer-spec-loop\"`, the selected `spec_slice_ref`, and bounded approved scope refs. Include these stop conditions: `authorization-missing`, `scope-change`, `contamination-suspected`, `schema-validation-failed`, `leakage-scan-failed`, `unit-blocked`, `implementation-complete`, `coverage-complete`, `iteration-limit-reached`, `spec-slice-complete`, `spec-slice-blocked`, `spec-delta-required`, `no-progress-detected`, `repeated-unit-selection`, and `clean-room-returned`.\n\nThe inner loop returns only after Agent 0 consumes the terminal Agent 3 report, any configured Agent 4 `polish-report.json`, and completes contaminated-side coverage verification. Write `clean-room-result.json` before returning control to the outer spec loop.\n\nFor multi-file source scope, guide agent zero\u002Fcontroller to run `skills\u002Fclean-room\u002Fscripts\u002Fbuild_source_index.py` as preflight outside clean-room role sessions. Store `source-index.json` only under the contaminated artifact root and never include it in clean handoff packages. If no indexable source code exists and screenshots\u002Fimages are the only authorized evidence, unattended mode may use `skills\u002Fclean-room\u002Fscripts\u002Fbuild_visual_index.py` only after preflight already answers the visual-fallback questions with no open questions. Store `visual-index.json` only under the contaminated artifact root and include visual roots in `CLEAN_ROOM_SOURCE_ROOTS` (ensuring screenshot evidence directories are explicitly added to `CLEAN_ROOM_SOURCE_ROOTS` during execution so that path-aware read hooks such as `hooks\u002Fdeny-clean-source-read.py` can protect them as expected).\n",{"name":5,"description":7,"argument-hint":43,"disable-model-invocation":47},[44,45,46],"authorized source scope","separated output roots","optional max iterations",true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fwhit3rabbit\u002Fclean-room-skill\u002Fskills\u002Funattended",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":59,"prompt":69,"zipAvailable":47},[60,63,66],{"tool":61,"command":62},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill unattended",{"tool":64,"command":65},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill unattended",{"tool":67,"command":68},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill unattended","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhit3rabbit\u002Fclean-room-skill\u002Fskills\u002Funattended\u002FSKILL.md",[],[72,80,87,94,121,145],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":79},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":79},"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":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":38},"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",[],[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":38},"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",[],[128,129,130,116,27,131,132,133,134,135,136,137,138,139,106,140,141,142,143,144],"deja reflect","reflect","review","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":162,"publishedAt":38},"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",[151,156,159],{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":157,"categoryName":158,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":160,"categoryName":161,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000010","后端与接口",[147,163,164,165,166,167,168,141,169,107,170,171,172,173,112,174,175,176,177,178],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]