[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EX1Y1FTKFNQV4KY0YP4NJZ":3,"skill-same:01M7EX1Y1FTKFNQV4KY0YP4NJZ":60},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7EX1Y1FTKFNQV4KY0YP4NJZ","argue",null,"Run structured multi-agent debates using argue CLI for cross-examined, high-confidence answers. Use when facing strategic decisions, ambiguous trade-offs, architecture debates, or questions where multiple perspectives improve the answer. Triggers on: argue, debate, cross-examine, second opinion, multi-agent, 'Should we X or Y?' with real stakes, consensus-building, risk analysis, or confirmation-bias mitigation.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fargue\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: argue\ndescription: \"Run structured multi-agent debates using argue CLI for cross-examined, high-confidence answers. Use when facing strategic decisions, ambiguous trade-offs, architecture debates, or questions where multiple perspectives improve the answer. Triggers on: argue, debate, cross-examine, second opinion, multi-agent, 'Should we X or Y?' with real stakes, consensus-building, risk analysis, or confirmation-bias mitigation.\"\nlicense: MIT\ncompatibility: \"Requires argue CLI (@onevcat\u002Fargue-cli v0.2+) and at least 2 configured agents. CLI-based providers need their respective CLIs installed (codex, gemini, claude, etc.). API-based providers need API keys in environment.\"\nmetadata: { \"author\": \"onevcat\", \"repo\": \"https:\u002F\u002Fgithub.com\u002Fonevcat\u002Fargue\" }\n---\n\n# Argue — Multi-Agent Debate Engine\n\nStructured debates where AI agents analyze independently, cross-examine across rounds, and converge on consensus through voting. Higher-confidence answers than any single model alone.\n\n## When to Use\n\n✅ Strategic \u002F architectural decisions with real trade-offs, \"Should we X or Y?\" with real stakes, risk analysis, confirmation-bias mitigation, pre-commit quality gates on big decisions.\n\n❌ Simple factual lookups, time-critical tasks (debates take 3–7 minutes), open-ended creative generation, questions with obvious answers.\n\n## Pre-flight\n\nIf `argue` is not on PATH, install it (confirm with the user first — this is a global install):\n\n```bash\nnpm install -g @onevcat\u002Fargue-cli\n```\n\nThen verify and configure:\n\n```bash\nargue version                          # verify installed (v0.2+)\nargue config init --global             # ~\u002F.config\u002Fargue\u002Fconfig.json — recommended for agent use\n\n# Add at least 2 agents — `--agent \u003Cid>` shorthand creates provider + agent in one shot\nargue config add-provider --id codex  --type cli --cli-type codex  --model-id gpt-5.4 --agent codex-agent\nargue config add-provider --id gemini --type cli --cli-type gemini --model-id gemini-3.1-pro-preview --agent gemini-agent\n```\n\n**Why global by default**: a global config is set up once and works from any cwd, and outputs go to `~\u002F.argue\u002Foutput\u002F\u003CrequestId>\u002F` instead of cluttering the current project tree. Use `argue config init --local` only when a specific project needs its own dedicated agent line-up — that writes `.\u002Fargue.config.json` and outputs to `.\u002Fout\u002F\u003CrequestId>\u002F`.\n\nFor API providers, SDK adapters, roles, and system prompts, see [references\u002Fsetup.md](references\u002Fsetup.md).\n\n## Running Debates\n\n```bash\n# Basic — 2 agents, 2-3 rounds, auto-consensus\nargue run --task \"Should we use a monorepo or polyrepo?\" --verbose\n\n# With a follow-up action: representative executes once consensus is reached\nargue run \\\n  --task \"Review the API design in docs\u002Fapi.md\" \\\n  --action \"Implement the consensus recommendation and open a PR\" \\\n  --verbose\n\n# Open the rendered report in the hosted viewer when the run finishes\nargue run --task \"...\" --view\n```\n\nUseful flags (full list: `argue --help`):\n\n| Flag                            | Purpose                                                                                                       |\n| ------------------------------- | ------------------------------------------------------------------------------------------------------------- |\n| `--agents a,b`                  | Pick which agents participate (default: `defaults.defaultAgents` from config, else **all configured agents**) |\n| `--min-rounds` \u002F `--max-rounds` | Control debate depth (defaults: 2 \u002F 3)                                                                        |\n| `--threshold \u003C0..1>`            | Consensus threshold (default: 1 = unanimous)                                                                  |\n| `--action \u003Cprompt>`             | Execute task after consensus                                                                                  |\n| `--view` \u002F `--viewer-url \u003Curl>` | Open report in the hosted viewer                                                                              |\n| `--input \u003Cfile>`                | JSON input for complex setups                                                                                 |\n| `--verbose` \u002F `-v`              | Stream agent reasoning live                                                                                   |\n\nDebates typically take 3–7 minutes for 2 agents × 3 rounds. Default cap is 20 min per round (and per task, which tracks the round cap by default); bump `--per-round-timeout-ms` for heavy reviews.\n\n## Viewing & Acting on Results\n\nWhen a run finishes, argue prints the request id and a viewer hint. Open it any time:\n\n```bash\nargue view                  # most recent run\nargue view \u003Crequest-id>     # specific run\n```\n\nThe hosted viewer renders `result.json` entirely client-side (gzip + base64url in the URL fragment — nothing is uploaded). Use `--viewer-url` to point at a self-hosted viewer.\n\nTo run a follow-up task using a debate result as context:\n\n```bash\nargue act --result ~\u002F.argue\u002Foutput\u002F\u003CrequestId>\u002Fresult.json --task \"Write a summary blog post\"\nargue act --result .\u002Fout\u002F\u003CrequestId>\u002Fresult.json --task \"Implement the changes\" --agent codex-agent\n```\n\n## Output Files\n\nAfter every run, argue writes to `~\u002F.argue\u002Foutput\u002F\u003CrequestId>\u002F` (global config) or `.\u002Fout\u002F\u003CrequestId>\u002F` (project-local config):\n\n- `result.json` — full structured result\n- `summary.md` — markdown report (written on completion)\n- `events.jsonl` — event stream (written live, survives crashes — parse it for partial results if a run is killed)\n- `error.json` — error details (only on failure)\n\nResult status: `consensus` | `partial_consensus` | `unresolved` | `failed`.\n\nIf you need to parse `result.json` programmatically, the canonical schema lives at [`packages\u002Fargue\u002Fsrc\u002Fcontracts\u002Fresult.ts`](https:\u002F\u002Fgithub.com\u002Fonevcat\u002Fargue\u002Fblob\u002Fmaster\u002Fpackages\u002Fargue\u002Fsrc\u002Fcontracts\u002Fresult.ts).\n\n## Tips\n\n1. **Frame as decisions, not topics.** \"Should we use SwiftUI or UIKit?\" beats \"Tell me about SwiftUI\".\n2. **Add context.** \"Should we use a monorepo? Context: 8 microservices, 3 teams, Node+Go\" produces sharper claims.\n3. **2–3 agents is the sweet spot.** Agents in the same round are dispatched in parallel, so wall-clock is dominated by rounds rather than agent count — adding more agents barely costs time. The real cost is **tokens**: every extra agent produces its own claims, plus every other agent has to read them as peer context, so token usage grows roughly with N². If the user's config has more than 3 agents, pass `--agents a,b,c` explicitly to pick a focused subset, or set `defaults.defaultAgents` in the config file once.\n4. **Use `--action`** when consensus should drive code changes or another real-world side-effect.\n\n## Troubleshooting\n\nFor common errors and fixes, see [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md).\n","# Argue — Multi-Agent Debate Engine\n\nStructured debates where AI agents analyze independently, cross-examine across rounds, and converge on consensus through voting. Higher-confidence answers than any single model alone.\n\n## When to Use\n\n✅ Strategic \u002F architectural decisions with real trade-offs, \"Should we X or Y?\" with real stakes, risk analysis, confirmation-bias mitigation, pre-commit quality gates on big decisions.\n\n❌ Simple factual lookups, time-critical tasks (debates take 3–7 minutes), open-ended creative generation, questions with obvious answers.\n\n## Pre-flight\n\nIf `argue` is not on PATH, install it (confirm with the user first — this is a global install):\n\n```bash\nnpm install -g @onevcat\u002Fargue-cli\n```\n\nThen verify and configure:\n\n```bash\nargue version                          # verify installed (v0.2+)\nargue config init --global             # ~\u002F.config\u002Fargue\u002Fconfig.json — recommended for agent use\n\n# Add at least 2 agents — `--agent \u003Cid>` shorthand creates provider + agent in one shot\nargue config add-provider --id codex  --type cli --cli-type codex  --model-id gpt-5.4 --agent codex-agent\nargue config add-provider --id gemini --type cli --cli-type gemini --model-id gemini-3.1-pro-preview --agent gemini-agent\n```\n\n**Why global by default**: a global config is set up once and works from any cwd, and outputs go to `~\u002F.argue\u002Foutput\u002F\u003CrequestId>\u002F` instead of cluttering the current project tree. Use `argue config init --local` only when a specific project needs its own dedicated agent line-up — that writes `.\u002Fargue.config.json` and outputs to `.\u002Fout\u002F\u003CrequestId>\u002F`.\n\nFor API providers, SDK adapters, roles, and system prompts, see [references\u002Fsetup.md](references\u002Fsetup.md).\n\n## Running Debates\n\n```bash\n# Basic — 2 agents, 2-3 rounds, auto-consensus\nargue run --task \"Should we use a monorepo or polyrepo?\" --verbose\n\n# With a follow-up action: representative executes once consensus is reached\nargue run \\\n  --task \"Review the API design in docs\u002Fapi.md\" \\\n  --action \"Implement the consensus recommendation and open a PR\" \\\n  --verbose\n\n# Open the rendered report in the hosted viewer when the run finishes\nargue run --task \"...\" --view\n```\n\nUseful flags (full list: `argue --help`):\n\n| Flag                            | Purpose                                                                                                       |\n| ------------------------------- | ------------------------------------------------------------------------------------------------------------- |\n| `--agents a,b`                  | Pick which agents participate (default: `defaults.defaultAgents` from config, else **all configured agents**) |\n| `--min-rounds` \u002F `--max-rounds` | Control debate depth (defaults: 2 \u002F 3)                                                                        |\n| `--threshold \u003C0..1>`            | Consensus threshold (default: 1 = unanimous)                                                                  |\n| `--action \u003Cprompt>`             | Execute task after consensus                                                                                  |\n| `--view` \u002F `--viewer-url \u003Curl>` | Open report in the hosted viewer                                                                              |\n| `--input \u003Cfile>`                | JSON input for complex setups                                                                                 |\n| `--verbose` \u002F `-v`              | Stream agent reasoning live                                                                                   |\n\nDebates typically take 3–7 minutes for 2 agents × 3 rounds. Default cap is 20 min per round (and per task, which tracks the round cap by default); bump `--per-round-timeout-ms` for heavy reviews.\n\n## Viewing & Acting on Results\n\nWhen a run finishes, argue prints the request id and a viewer hint. Open it any time:\n\n```bash\nargue view                  # most recent run\nargue view \u003Crequest-id>     # specific run\n```\n\nThe hosted viewer renders `result.json` entirely client-side (gzip + base64url in the URL fragment — nothing is uploaded). Use `--viewer-url` to point at a self-hosted viewer.\n\nTo run a follow-up task using a debate result as context:\n\n```bash\nargue act --result ~\u002F.argue\u002Foutput\u002F\u003CrequestId>\u002Fresult.json --task \"Write a summary blog post\"\nargue act --result .\u002Fout\u002F\u003CrequestId>\u002Fresult.json --task \"Implement the changes\" --agent codex-agent\n```\n\n## Output Files\n\nAfter every run, argue writes to `~\u002F.argue\u002Foutput\u002F\u003CrequestId>\u002F` (global config) or `.\u002Fout\u002F\u003CrequestId>\u002F` (project-local config):\n\n- `result.json` — full structured result\n- `summary.md` — markdown report (written on completion)\n- `events.jsonl` — event stream (written live, survives crashes — parse it for partial results if a run is killed)\n- `error.json` — error details (only on failure)\n\nResult status: `consensus` | `partial_consensus` | `unresolved` | `failed`.\n\nIf you need to parse `result.json` programmatically, the canonical schema lives at [`packages\u002Fargue\u002Fsrc\u002Fcontracts\u002Fresult.ts`](https:\u002F\u002Fgithub.com\u002Fonevcat\u002Fargue\u002Fblob\u002Fmaster\u002Fpackages\u002Fargue\u002Fsrc\u002Fcontracts\u002Fresult.ts).\n\n## Tips\n\n1. **Frame as decisions, not topics.** \"Should we use SwiftUI or UIKit?\" beats \"Tell me about SwiftUI\".\n2. **Add context.** \"Should we use a monorepo? Context: 8 microservices, 3 teams, Node+Go\" produces sharper claims.\n3. **2–3 agents is the sweet spot.** Agents in the same round are dispatched in parallel, so wall-clock is dominated by rounds rather than agent count — adding more agents barely costs time. The real cost is **tokens**: every extra agent produces its own claims, plus every other agent has to read them as peer context, so token usage grows roughly with N². If the user's config has more than 3 agents, pass `--agents a,b,c` explicitly to pick a focused subset, or set `defaults.defaultAgents` in the config file once.\n4. **Use `--action`** when consensus should drive code changes or another real-world side-effect.\n\n## Troubleshooting\n\nFor common errors and fixes, see [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md).\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":27},{"repo":25,"author":26},"https:\u002F\u002Fgithub.com\u002Fonevcat\u002Fargue","onevcat","Requires argue CLI (@onevcat\u002Fargue-cli v0.2+) and at least 2 configured agents. CLI-based providers need their respective CLIs installed (codex, gemini, claude, etc.). API-based providers need API keys in environment.","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fargue",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill argue",{"tool":42,"command":43},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill argue",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill argue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fargue\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fsetup.md","REFERENCE","参考文档",6133,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fargue\u002Freferences\u002Fsetup.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Ftroubleshooting.md",5752,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fargue\u002Freferences\u002Ftroubleshooting.md",[61,69,74,81,88,95],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":70,"name":63,"nameZh":6,"description":64,"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":68},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":68},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":68},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":68},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":68},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]