[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75GE5CS34PW6D9TASWNYR88":3,"skill-same:01M75GE5CS34PW6D9TASWNYR88":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75GE5CS34PW6D9TASWNYR88","ultraqa",null,"QA cycling workflow - test, verify, fix, repeat until goal met","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Foh-my-codex\u002Fskills\u002Fultraqa\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ultraqa\ndescription: QA cycling workflow - test, verify, fix, repeat until goal met\n---\n\n# UltraQA Skill\n\n[ULTRAQA ACTIVATED - AUTONOMOUS QA CYCLING]\n\n## Overview\n\n## GPT-5.4 Guidance Alignment\n\n- Default to concise, evidence-dense progress and completion reporting unless the user or risk level requires more detail.\n- Treat newer user task updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.\n- If correctness depends on additional inspection, retrieval, execution, or verification, keep using the relevant tools until the QA cycle is grounded.\n- Continue through clear, low-risk, reversible next steps automatically; ask only when the next step is materially branching, destructive, or preference-dependent.\n\nYou are now in **ULTRAQA** mode - an autonomous QA cycling workflow that runs until your quality goal is met.\n\n**Cycle**: qa-tester → architect verification → fix → repeat\n\n## Goal Parsing\n\nParse the goal from arguments. Supported formats:\n\n| Invocation | Goal Type | What to Check |\n|------------|-----------|---------------|\n| `\u002Fultraqa --tests` | tests | All test suites pass |\n| `\u002Fultraqa --build` | build | Build succeeds with exit 0 |\n| `\u002Fultraqa --lint` | lint | No lint errors |\n| `\u002Fultraqa --typecheck` | typecheck | No TypeScript errors |\n| `\u002Fultraqa --custom \"pattern\"` | custom | Custom success pattern in output |\n\nIf no structured goal provided, interpret the argument as a custom goal.\n\n## Cycle Workflow\n\n### Cycle N (Max 5)\n\n1. **RUN QA**: Execute verification based on goal type\n   - `--tests`: Run the project's test command\n   - `--build`: Run the project's build command\n   - `--lint`: Run the project's lint command\n   - `--typecheck`: Run the project's type check command\n   - `--custom`: Run appropriate command and check for pattern\n   - `--interactive`: Use qa-tester for interactive CLI\u002Fservice testing:\n     ```\n     delegate(role=\"qa-tester\", tier=\"STANDARD\", task=\"TEST:\n     Goal: [describe what to verify]\n     Service: [how to start]\n     Test cases: [specific scenarios to verify]\")\n     ```\n\n2. **CHECK RESULT**: Did the goal pass?\n   - **YES** → Exit with success message\n   - **NO** → Continue to step 3\n\n3. **ARCHITECT DIAGNOSIS**: Spawn architect to analyze failure\n   ```\n   delegate(role=\"architect\", tier=\"THOROUGH\", task=\"DIAGNOSE FAILURE:\n   Goal: [goal type]\n   Output: [test\u002Fbuild output]\n   Provide root cause and specific fix recommendations.\")\n   ```\n\n4. **FIX ISSUES**: Apply architect's recommendations\n   ```\n   delegate(role=\"executor\", tier=\"STANDARD\", task=\"FIX:\n   Issue: [architect diagnosis]\n   Files: [affected files]\n   Apply the fix precisely as recommended.\")\n   ```\n\n5. **REPEAT**: Go back to step 1\n\n## Exit Conditions\n\n| Condition | Action |\n|-----------|--------|\n| **Goal Met** | Exit with success: \"ULTRAQA COMPLETE: Goal met after N cycles\" |\n| **Cycle 5 Reached** | Exit with diagnosis: \"ULTRAQA STOPPED: Max cycles. Diagnosis: ...\" |\n| **Same Failure 3x** | Exit early: \"ULTRAQA STOPPED: Same failure detected 3 times. Root cause: ...\" |\n| **Environment Error** | Exit: \"ULTRAQA ERROR: [tmux\u002Fport\u002Fdependency issue]\" |\n\n## Observability\n\nOutput progress each cycle:\n```\n[ULTRAQA Cycle 1\u002F5] Running tests...\n[ULTRAQA Cycle 1\u002F5] FAILED - 3 tests failing\n[ULTRAQA Cycle 1\u002F5] Architect diagnosing...\n[ULTRAQA Cycle 1\u002F5] Fixing: auth.test.ts - missing mock\n[ULTRAQA Cycle 2\u002F5] Running tests...\n[ULTRAQA Cycle 2\u002F5] PASSED - All 47 tests pass\n[ULTRAQA COMPLETE] Goal met after 2 cycles\n```\n\n## State Tracking\n\nUse `omx_state` MCP tools for UltraQA lifecycle state.\n\n- **On start**:\n  `state_write({mode: \"ultraqa\", active: true, current_phase: \"qa\", iteration: 1, started_at: \"\u003Cnow>\"})`\n- **On each cycle**:\n  `state_write({mode: \"ultraqa\", current_phase: \"qa\", iteration: \u003Ccycle>})`\n- **On diagnose\u002Ffix transitions**:\n  `state_write({mode: \"ultraqa\", current_phase: \"diagnose\"})`\n  `state_write({mode: \"ultraqa\", current_phase: \"fix\"})`\n- **On completion**:\n  `state_write({mode: \"ultraqa\", active: false, current_phase: \"complete\", completed_at: \"\u003Cnow>\"})`\n- **For resume detection**:\n  `state_read({mode: \"ultraqa\"})`\n\n\n## Scenario Examples\n\n**Good:** The user says `continue` after the workflow already has a clear next step. Continue the current branch of work instead of restarting or re-asking the same question.\n\n**Good:** The user changes only the output shape or downstream delivery step (for example `make a PR`). Preserve earlier non-conflicting workflow constraints and apply the update locally.\n\n**Bad:** The user says `continue`, and the workflow restarts discovery or stops before the missing verification\u002Fevidence is gathered.\n\n## Cancellation\n\nUser can cancel with `\u002Fcancel` which clears the state file.\n\n## Important Rules\n\n1. **PARALLEL when possible** - Run diagnosis while preparing potential fixes\n2. **TRACK failures** - Record each failure to detect patterns\n3. **EARLY EXIT on pattern** - 3x same failure = stop and surface\n4. **CLEAR OUTPUT** - User should always know current cycle and status\n5. **CLEAN UP** - Clear state file on completion or cancellation\n\n## STATE CLEANUP ON COMPLETION\n\nWhen goal is met OR max cycles reached OR exiting early, run `$cancel` or call:\n\n`state_clear({mode: \"ultraqa\"})`\n\nUse MCP state cleanup rather than deleting files directly.\n\n---\n\nBegin ULTRAQA cycling now. Parse the goal and start cycle 1.\n","# UltraQA Skill\n\n[ULTRAQA ACTIVATED - AUTONOMOUS QA CYCLING]\n\n## Overview\n\n## GPT-5.4 Guidance Alignment\n\n- Default to concise, evidence-dense progress and completion reporting unless the user or risk level requires more detail.\n- Treat newer user task updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.\n- If correctness depends on additional inspection, retrieval, execution, or verification, keep using the relevant tools until the QA cycle is grounded.\n- Continue through clear, low-risk, reversible next steps automatically; ask only when the next step is materially branching, destructive, or preference-dependent.\n\nYou are now in **ULTRAQA** mode - an autonomous QA cycling workflow that runs until your quality goal is met.\n\n**Cycle**: qa-tester → architect verification → fix → repeat\n\n## Goal Parsing\n\nParse the goal from arguments. Supported formats:\n\n| Invocation | Goal Type | What to Check |\n|------------|-----------|---------------|\n| `\u002Fultraqa --tests` | tests | All test suites pass |\n| `\u002Fultraqa --build` | build | Build succeeds with exit 0 |\n| `\u002Fultraqa --lint` | lint | No lint errors |\n| `\u002Fultraqa --typecheck` | typecheck | No TypeScript errors |\n| `\u002Fultraqa --custom \"pattern\"` | custom | Custom success pattern in output |\n\nIf no structured goal provided, interpret the argument as a custom goal.\n\n## Cycle Workflow\n\n### Cycle N (Max 5)\n\n1. **RUN QA**: Execute verification based on goal type\n   - `--tests`: Run the project's test command\n   - `--build`: Run the project's build command\n   - `--lint`: Run the project's lint command\n   - `--typecheck`: Run the project's type check command\n   - `--custom`: Run appropriate command and check for pattern\n   - `--interactive`: Use qa-tester for interactive CLI\u002Fservice testing:\n     ```\n     delegate(role=\"qa-tester\", tier=\"STANDARD\", task=\"TEST:\n     Goal: [describe what to verify]\n     Service: [how to start]\n     Test cases: [specific scenarios to verify]\")\n     ```\n\n2. **CHECK RESULT**: Did the goal pass?\n   - **YES** → Exit with success message\n   - **NO** → Continue to step 3\n\n3. **ARCHITECT DIAGNOSIS**: Spawn architect to analyze failure\n   ```\n   delegate(role=\"architect\", tier=\"THOROUGH\", task=\"DIAGNOSE FAILURE:\n   Goal: [goal type]\n   Output: [test\u002Fbuild output]\n   Provide root cause and specific fix recommendations.\")\n   ```\n\n4. **FIX ISSUES**: Apply architect's recommendations\n   ```\n   delegate(role=\"executor\", tier=\"STANDARD\", task=\"FIX:\n   Issue: [architect diagnosis]\n   Files: [affected files]\n   Apply the fix precisely as recommended.\")\n   ```\n\n5. **REPEAT**: Go back to step 1\n\n## Exit Conditions\n\n| Condition | Action |\n|-----------|--------|\n| **Goal Met** | Exit with success: \"ULTRAQA COMPLETE: Goal met after N cycles\" |\n| **Cycle 5 Reached** | Exit with diagnosis: \"ULTRAQA STOPPED: Max cycles. Diagnosis: ...\" |\n| **Same Failure 3x** | Exit early: \"ULTRAQA STOPPED: Same failure detected 3 times. Root cause: ...\" |\n| **Environment Error** | Exit: \"ULTRAQA ERROR: [tmux\u002Fport\u002Fdependency issue]\" |\n\n## Observability\n\nOutput progress each cycle:\n```\n[ULTRAQA Cycle 1\u002F5] Running tests...\n[ULTRAQA Cycle 1\u002F5] FAILED - 3 tests failing\n[ULTRAQA Cycle 1\u002F5] Architect diagnosing...\n[ULTRAQA Cycle 1\u002F5] Fixing: auth.test.ts - missing mock\n[ULTRAQA Cycle 2\u002F5] Running tests...\n[ULTRAQA Cycle 2\u002F5] PASSED - All 47 tests pass\n[ULTRAQA COMPLETE] Goal met after 2 cycles\n```\n\n## State Tracking\n\nUse `omx_state` MCP tools for UltraQA lifecycle state.\n\n- **On start**:\n  `state_write({mode: \"ultraqa\", active: true, current_phase: \"qa\", iteration: 1, started_at: \"\u003Cnow>\"})`\n- **On each cycle**:\n  `state_write({mode: \"ultraqa\", current_phase: \"qa\", iteration: \u003Ccycle>})`\n- **On diagnose\u002Ffix transitions**:\n  `state_write({mode: \"ultraqa\", current_phase: \"diagnose\"})`\n  `state_write({mode: \"ultraqa\", current_phase: \"fix\"})`\n- **On completion**:\n  `state_write({mode: \"ultraqa\", active: false, current_phase: \"complete\", completed_at: \"\u003Cnow>\"})`\n- **For resume detection**:\n  `state_read({mode: \"ultraqa\"})`\n\n\n## Scenario Examples\n\n**Good:** The user says `continue` after the workflow already has a clear next step. Continue the current branch of work instead of restarting or re-asking the same question.\n\n**Good:** The user changes only the output shape or downstream delivery step (for example `make a PR`). Preserve earlier non-conflicting workflow constraints and apply the update locally.\n\n**Bad:** The user says `continue`, and the workflow restarts discovery or stops before the missing verification\u002Fevidence is gathered.\n\n## Cancellation\n\nUser can cancel with `\u002Fcancel` which clears the state file.\n\n## Important Rules\n\n1. **PARALLEL when possible** - Run diagnosis while preparing potential fixes\n2. **TRACK failures** - Record each failure to detect patterns\n3. **EARLY EXIT on pattern** - 3x same failure = stop and surface\n4. **CLEAR OUTPUT** - User should always know current cycle and status\n5. **CLEAN UP** - Clear state file on completion or cancellation\n\n## STATE CLEANUP ON COMPLETION\n\nWhen goal is met OR max cycles reached OR exiting early, run `$cancel` or call:\n\n`state_clear({mode: \"ultraqa\"})`\n\nUse MCP state cleanup rather than deleting files directly.\n\n---\n\nBegin ULTRAQA cycling now. Parse the goal and start cycle 1.\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Foh-my-codex\u002Fskills\u002Fultraqa",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill ultraqa",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill ultraqa",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill ultraqa","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Foh-my-codex\u002Fskills\u002Fultraqa\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]