[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D32TKRBFHMTB2RPXYBV7MF":3,"skill-same:01M7D32TKRBFHMTB2RPXYBV7MF":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7D32TKRBFHMTB2RPXYBV7MF","ultraqa",null,"Adversarial dynamic e2e QA workflow - generate hostile scenarios, test, verify, fix, report, and clean up","Pibomeister\u002Fagent-kit","Pibomeister","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11633791?v=4","01M7D2NBHEKARMHN9MPV2J80XD","Eduardo Picazo","01M7D2NBJ3Z33SGSYCZ0KBD5DE",0,"MIT","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fprovenance\u002Fdonor-snapshots\u002Fomx@cb955b0d5bec\u002Fskills\u002Fultraqa\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ultraqa\ndescription: Adversarial dynamic e2e QA workflow - generate hostile scenarios, test, verify, fix, report, and clean up\n---\n\n# UltraQA Task Card\n\nUse this explicit opt-in when a runnable behavior needs adversarial dynamic end-to-end\nQA. Shared operating invariants live in `templates\u002FAGENTS.md`; this card defines the\nQA matrix, evidence contract, and bounded cycling only.\n\n## When to use and inputs\n\n- Use `\u002Fultraqa --tests|--build|--lint|--typecheck|--interactive` or `\u002Fultraqa --custom \"pattern\"` for the corresponding goal; without a structured goal, derive a runnable behavior goal.\n- Inputs: goal, changed scope, acceptance criteria, runnable command\u002Fservice, existing tests, and relevant state\u002Fcleanup paths.\n- Keep outcome-first framing, local overrides for the active workflow branch, and `continue` on the current verified next step.\n- If the user says `continue`, advance the current verified QA step rather than restarting discovery.\n- UltraQA is not satisfied by a shallow build\u002Flint\u002Ftypecheck\u002Ftest checklist: exercise requested behavior through adversarial dynamic e2e scenarios whenever it can be run, simulated, or harnessed safely.\n\n## Plan and scenario matrix\n\nBefore commands, record a matrix with scenario id, intent, user\u002Fattacker model, setup,\ncommand or harness, expected signal, actual result, fixes, evidence, and cleanup.\nInclude a normal path and relevant hostile classes:\n\n1. **Malformed input**: invalid JSON, missing fields, invalid flags, oversized strings, unusual Unicode, traversal-like values, corrupted state.\n2. **Repeated interruptions**: repeated `continue`, stop\u002Fcancel\u002Fabort wording, partial output, and retries.\n3. **Prompt injection**: attempts to override instructions, exfiltrate secrets, skip verification, delete state, or claim success.\n4. **Cancel\u002Fresume behavior** and **stale state**: cleanup, resume detection, mismatched sessions, missing timestamps, contradictory phases.\n5. **Dirty worktree**: pre-existing changes\u002Funtracked files remain untouched.\n6. **Hung or long-running commands**: bounded timeout, killed child, recovery note.\n7. **Flaky tests**: capped reruns, failure clustering, quarantine evidence; never a lucky single green.\n8. **Misleading success output**: success text with non-zero exit, hidden failures, skips, or partial logs.\n\n## Cycle (maximum 5)\n\n1. **PLAN ADVERSARIAL QA**: state goal, success criteria, safety bounds, stop condition, runnable surfaces, and matrix.\n2. **RUN BASELINE VERIFICATION**: `--tests` runs project tests; `--build` runs build plus built-artifact probes; `--lint` runs lint; `--typecheck` runs typecheck plus typed harnesses; `--custom` verifies pattern and exit status; `--interactive` uses a bounded CLI\u002Fservice harness.\n3. **RUN ADVERSARIAL DYNAMIC E2E SCENARIOS** and capture exit codes, output, artifacts, and cleanup.\n4. **CHECK RESULT**: pass only when baseline, adversarial scenarios, evidence, and cleanup all pass. Otherwise diagnose and fix, then repeat.\n5. **ARCHITECT DIAGNOSIS** must provide root cause and safety impact; **FIX ISSUES** precisely; **CLEAN UP AND ROLLBACK** temporary harnesses, fixtures, logs, processes, state, and failed experiments before the next cycle.\n\nGenerate temporary tests, scripts, fixtures, or harnesses only when useful. Use bounded runtimes,\nproject-native tools, and safe substitutes when a safety boundary blocks a scenario.\nUse absolute repo imports and `pathToFileURL(join(repoRoot, \"dist\", ...)).href`; Never rely on `.\u002Fdist` from `\u002Ftmp`.\nUse a safe file writer with a non-interpolating file-write mechanism; do not use interpolating heredocs for JavaScript assertions.\nSanitize OMX runtime env for isolated probes: keep `OMX_ROOT` and `OMX_STATE_ROOT` unset and run `env -u OMX_ROOT -u OMX_STATE_ROOT`.\nClassify harness setup failures separately: record it as harness debris, fix the harness, and rerun the scenario before declaring a product defect.\n\n## Safety, state, and exit\n\nNo destructive commands, secret exfiltration, credential dumping, production writes, or unbounded process spawning. Use no unbounded waits; preserve unrelated dirty work. If a scenario is unsafe, record it blocked and the safe substitute. Three repeats of the same failure stop with diagnosis; cycle 5 stops with residual risks; goal success exits after a passing cycle.\n\nUse CLI-first lifecycle state and exact commands:\n\n```sh\nomx state write --input '{\"mode\":\"ultraqa\",\"active\":true,\"current_phase\":\"planning\",\"iteration\":1,\"started_at\":\"\u003Cnow>\",\"scenario_matrix\":[]}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"current_phase\":\"qa\",\"iteration\":\u003Ccycle>,\"scenario_matrix\":\"\u003Cupdated matrix path or summary>\"}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"current_phase\":\"adversarial-e2e\"}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"current_phase\":\"diagnose\"}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"current_phase\":\"fix\"}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"current_phase\":\"cleanup\"}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"active\":false,\"current_phase\":\"complete\",\"completed_at\":\"\u003Cnow>\"}' --json\nomx state read --input '{\"mode\":\"ultraqa\"}' --json\nomx state clear --input '{\"mode\":\"ultraqa\"}' --json\n```\n\nOn completion, max cycles, same failure, safety boundary, or environment error, clean\nstate and temporary artifacts. Report cleanup status and clean temporary e2e harnesses.\nNever claim complete without current evidence.\n\n## Evidence\u002Foutput contract\n\nReturn `# UltraQA Report` with: **Goal and success criteria** (including stop condition\nand safety bounds); **Scenario matrix** (all columns above); **Commands run** (exit code,\npurpose, timeout, key output); **Failures found** (root\u002Fuser\u002Fsafety impact); **Fixes\napplied** \u002F **Fixes applied** (files, rationale, scenarios, regression evidence); **Cleanup and rollback**\n(artifacts\u002Fprocesses\u002Fworktree before\u002Fafter); **Residual risks**; and **Evidence**\n(logs, harness output, screenshots\u002Ftranscripts where relevant, rerun\u002Fflake evidence).\n\n## Exit condition\n\n`ULTRAQA COMPLETE: Goal met after N cycles` only follows a passing baseline plus\nadversarial matrix, clean artifacts, and complete evidence. Otherwise return the exact\nbounded status: `ULTRAQA STOPPED: Max cycles`, `ULTRAQA STOPPED: Same failure detected 3 times`,\n`ULTRAQA BLOCKED: ...`, or `ULTRAQA ERROR: ...` with owner and next safe step.\n","# UltraQA Task Card\n\nUse this explicit opt-in when a runnable behavior needs adversarial dynamic end-to-end\nQA. Shared operating invariants live in `templates\u002FAGENTS.md`; this card defines the\nQA matrix, evidence contract, and bounded cycling only.\n\n## When to use and inputs\n\n- Use `\u002Fultraqa --tests|--build|--lint|--typecheck|--interactive` or `\u002Fultraqa --custom \"pattern\"` for the corresponding goal; without a structured goal, derive a runnable behavior goal.\n- Inputs: goal, changed scope, acceptance criteria, runnable command\u002Fservice, existing tests, and relevant state\u002Fcleanup paths.\n- Keep outcome-first framing, local overrides for the active workflow branch, and `continue` on the current verified next step.\n- If the user says `continue`, advance the current verified QA step rather than restarting discovery.\n- UltraQA is not satisfied by a shallow build\u002Flint\u002Ftypecheck\u002Ftest checklist: exercise requested behavior through adversarial dynamic e2e scenarios whenever it can be run, simulated, or harnessed safely.\n\n## Plan and scenario matrix\n\nBefore commands, record a matrix with scenario id, intent, user\u002Fattacker model, setup,\ncommand or harness, expected signal, actual result, fixes, evidence, and cleanup.\nInclude a normal path and relevant hostile classes:\n\n1. **Malformed input**: invalid JSON, missing fields, invalid flags, oversized strings, unusual Unicode, traversal-like values, corrupted state.\n2. **Repeated interruptions**: repeated `continue`, stop\u002Fcancel\u002Fabort wording, partial output, and retries.\n3. **Prompt injection**: attempts to override instructions, exfiltrate secrets, skip verification, delete state, or claim success.\n4. **Cancel\u002Fresume behavior** and **stale state**: cleanup, resume detection, mismatched sessions, missing timestamps, contradictory phases.\n5. **Dirty worktree**: pre-existing changes\u002Funtracked files remain untouched.\n6. **Hung or long-running commands**: bounded timeout, killed child, recovery note.\n7. **Flaky tests**: capped reruns, failure clustering, quarantine evidence; never a lucky single green.\n8. **Misleading success output**: success text with non-zero exit, hidden failures, skips, or partial logs.\n\n## Cycle (maximum 5)\n\n1. **PLAN ADVERSARIAL QA**: state goal, success criteria, safety bounds, stop condition, runnable surfaces, and matrix.\n2. **RUN BASELINE VERIFICATION**: `--tests` runs project tests; `--build` runs build plus built-artifact probes; `--lint` runs lint; `--typecheck` runs typecheck plus typed harnesses; `--custom` verifies pattern and exit status; `--interactive` uses a bounded CLI\u002Fservice harness.\n3. **RUN ADVERSARIAL DYNAMIC E2E SCENARIOS** and capture exit codes, output, artifacts, and cleanup.\n4. **CHECK RESULT**: pass only when baseline, adversarial scenarios, evidence, and cleanup all pass. Otherwise diagnose and fix, then repeat.\n5. **ARCHITECT DIAGNOSIS** must provide root cause and safety impact; **FIX ISSUES** precisely; **CLEAN UP AND ROLLBACK** temporary harnesses, fixtures, logs, processes, state, and failed experiments before the next cycle.\n\nGenerate temporary tests, scripts, fixtures, or harnesses only when useful. Use bounded runtimes,\nproject-native tools, and safe substitutes when a safety boundary blocks a scenario.\nUse absolute repo imports and `pathToFileURL(join(repoRoot, \"dist\", ...)).href`; Never rely on `.\u002Fdist` from `\u002Ftmp`.\nUse a safe file writer with a non-interpolating file-write mechanism; do not use interpolating heredocs for JavaScript assertions.\nSanitize OMX runtime env for isolated probes: keep `OMX_ROOT` and `OMX_STATE_ROOT` unset and run `env -u OMX_ROOT -u OMX_STATE_ROOT`.\nClassify harness setup failures separately: record it as harness debris, fix the harness, and rerun the scenario before declaring a product defect.\n\n## Safety, state, and exit\n\nNo destructive commands, secret exfiltration, credential dumping, production writes, or unbounded process spawning. Use no unbounded waits; preserve unrelated dirty work. If a scenario is unsafe, record it blocked and the safe substitute. Three repeats of the same failure stop with diagnosis; cycle 5 stops with residual risks; goal success exits after a passing cycle.\n\nUse CLI-first lifecycle state and exact commands:\n\n```sh\nomx state write --input '{\"mode\":\"ultraqa\",\"active\":true,\"current_phase\":\"planning\",\"iteration\":1,\"started_at\":\"\u003Cnow>\",\"scenario_matrix\":[]}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"current_phase\":\"qa\",\"iteration\":\u003Ccycle>,\"scenario_matrix\":\"\u003Cupdated matrix path or summary>\"}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"current_phase\":\"adversarial-e2e\"}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"current_phase\":\"diagnose\"}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"current_phase\":\"fix\"}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"current_phase\":\"cleanup\"}' --json\nomx state write --input '{\"mode\":\"ultraqa\",\"active\":false,\"current_phase\":\"complete\",\"completed_at\":\"\u003Cnow>\"}' --json\nomx state read --input '{\"mode\":\"ultraqa\"}' --json\nomx state clear --input '{\"mode\":\"ultraqa\"}' --json\n```\n\nOn completion, max cycles, same failure, safety boundary, or environment error, clean\nstate and temporary artifacts. Report cleanup status and clean temporary e2e harnesses.\nNever claim complete without current evidence.\n\n## Evidence\u002Foutput contract\n\nReturn `# UltraQA Report` with: **Goal and success criteria** (including stop condition\nand safety bounds); **Scenario matrix** (all columns above); **Commands run** (exit code,\npurpose, timeout, key output); **Failures found** (root\u002Fuser\u002Fsafety impact); **Fixes\napplied** \u002F **Fixes applied** (files, rationale, scenarios, regression evidence); **Cleanup and rollback**\n(artifacts\u002Fprocesses\u002Fworktree before\u002Fafter); **Residual risks**; and **Evidence**\n(logs, harness output, screenshots\u002Ftranscripts where relevant, rerun\u002Fflake evidence).\n\n## Exit condition\n\n`ULTRAQA COMPLETE: Goal met after N cycles` only follows a passing baseline plus\nadversarial matrix, clean artifacts, and complete evidence. Otherwise return the exact\nbounded status: `ULTRAQA STOPPED: Max cycles`, `ULTRAQA STOPPED: Same failure detected 3 times`,\n`ULTRAQA BLOCKED: ...`, or `ULTRAQA ERROR: ...` with owner and next safe step.\n",{"name":5,"description":7},"main","e0232821c4abbcd4338d6018c20fb70f1b74336b","provenance\u002Fdonor-snapshots\u002Fomx@cb955b0d5bec\u002Fskills\u002Fultraqa",3,"https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit","https:\u002F\u002Fgithub.com\u002FPibomeister","www.eduardopicazoenriquez.com","2026-11-15 00:56:58",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Pibomeister\u002Fagent-kit --skill ultraqa",{"tool":38,"command":39},"bunx","bunx skills add Pibomeister\u002Fagent-kit --skill ultraqa",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Pibomeister\u002Fagent-kit --skill ultraqa","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fprovenance\u002Fdonor-snapshots\u002Fomx@cb955b0d5bec\u002Fskills\u002Fultraqa\u002FSKILL.md",true,[],[47,54,59,64,69,74],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7D3JZP2026RGY6XX1MC3NQQ","alpha","Human-started command: it runs only when the human's message begins with `\u002Fak:alpha`. On any other request do not load or follow it; tell the human to type that command. Runs the alpha workflow when a human asks for it.","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid\u002Fminimal\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":55,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7D3JA593Q3RBYJXKVZ37Y2K","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F25-article-tier-outside-vocabulary\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":60,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7D3HQDDAZTAPGWCPGDPNVBQ","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F24-article-without-triggers\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":65,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D3HK074TK3ZWK1ZZNQVPB0","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F23-enforced-by-without-predicate\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":70,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7D3HGHQM5C5TBSXBCE2WFHW","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F22-article-without-source-span\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":75,"name":49,"nameZh":6,"description":50,"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":19},"01M7D3HDV6HMK2ZHRM0P368KNT","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F21-fragment-redeclares-id\u002Fskills\u002Falpha\u002FSKILL.md",[],[]]