[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4V6V28SXKKJHC8RBTY19K":3,"skill-same:01M7F4V6V28SXKKJHC8RBTY19K":52},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7F4V6V28SXKKJHC8RBTY19K","skill-decision-support",null,"Present options with trade-offs for informed decision-making — use when choosing between approaches","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-技能与代理开发\u002Fskill-decision-support\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: skill-decision-support\ndescription: \"Present options with trade-offs for informed decision-making — use when choosing between approaches\"\ndisable-model-invocation: true\n---\n\n> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Decision Support & Options Presentation\n\n## Overview\n\nStructured approach to presenting options and alternatives with clear trade-offs, enabling informed decision-making.\n\n**Core principle:** Understand context → Generate options → Analyze trade-offs → Present clearly → Support choice.\n\n\n## When to Use\n\n**Use this skill when user:**\n- Asks for options or alternatives\n- Says \"fix or provide options\"\n- Needs help deciding between approaches\n- Wants to see different ways to solve a problem\n- Is uncertain about best path forward\n\n**Do NOT use for:**\n- General research (\"what is X?\") → use flow-probe\n- Implementation work → use flow-tangle\n- Simple yes\u002Fno questions\n- Already-decided approaches\n\n\n## The Process\n\n### Phase 1: Context Understanding\n\n#### Step 1: Understand the Decision Point\n\n```markdown\n**Decision Context:**\n\nWhat needs to be decided: [the core question]\nWhy it matters: [impact of this decision]\nConstraints: [time, resources, compatibility, etc.]\nCurrent state: [what exists now]\n```\n\n#### Step 2: Gather Requirements\n\nUse AskUserQuestion if needed to understand:\n- Must-have requirements\n- Nice-to-have features\n- Deal-breakers\n- Timeline constraints\n- Budget\u002Fresource constraints\n\n\n### Phase 2: Generate Options\n\n#### Step 1: Identify Viable Approaches\n\nGenerate 2-4 distinct options (not just variations):\n\n| Option Type | When to Include |\n|-------------|-----------------|\n| **Conservative** | Low risk, proven approach |\n| **Moderate** | Balanced risk\u002Freward |\n| **Innovative** | Higher risk, potentially better outcome |\n| **Minimal** | Simplest possible solution |\n\n**Don't generate options that:**\n- Violate stated constraints\n- Are clearly inferior to others\n- Are essentially the same with minor tweaks\n\n#### Step 2: Research Each Option\n\nFor each option, understand:\n- How it works\n- What it requires\n- What the outcome looks like\n- What could go wrong\n\n\n### Phase 3: Trade-off Analysis\n\nFor each option, analyze:\n\n```markdown\n### Option N: [Name]\n\n**Description:**\n[1-2 sentence description]\n\n**Pros:**\n- ✅ [Advantage 1]\n- ✅ [Advantage 2]\n- ✅ [Advantage 3]\n\n**Cons:**\n- ❌ [Disadvantage 1]\n- ❌ [Disadvantage 2]\n- ❌ [Disadvantage 3]\n\n**Effort:** [Low\u002FMedium\u002FHigh]\n**Risk:** [Low\u002FMedium\u002FHigh]\n**Reversibility:** [Easy\u002FModerate\u002FDifficult to undo]\n\n**Best for:** [when this option makes sense]\n```\n\n\n### Phase 4: Present Options\n\n#### Format for Presentation\n\n```markdown\n# Decision: [What needs to be decided]\n\n**Context:** [Brief summary of why this decision is needed]\n\n\n## Option 1: [Conservative\u002FProven Approach] ⭐ (Recommended)\n\n**What it is:**\n[Clear explanation in 1-2 sentences]\n\n**Pros:**\n- ✅ [Pro 1]\n- ✅ [Pro 2]\n- ✅ [Pro 3]\n\n**Cons:**\n- ❌ [Con 1]\n- ❌ [Con 2]\n\n**Implementation:**\n[Brief overview of what's involved]\n\n**Timeline:** [estimate]\n**Risk Level:** Low\u002FMedium\u002FHigh\n\n\n## Option 2: [Alternative Approach]\n\n[Same structure as Option 1]\n\n\n## Option 3: [Another Alternative]\n\n[Same structure as Option 1]\n\n\n## Recommendation\n\n**I recommend Option [N]: [Name]**\n\n**Why:**\n1. [Reason 1]\n2. [Reason 2]\n3. [Reason 3]\n\n**This option is best because:** [summary of key advantage relative to context]\n\n\n## Quick Comparison\n\n| Criteria | Option 1 | Option 2 | Option 3 |\n|----------|----------|----------|----------|\n| Effort | [level] | [level] | [level] |\n| Risk | [level] | [level] | [level] |\n| Reversible | [yes\u002Fno] | [yes\u002Fno] | [yes\u002Fno] |\n| Timeline | [time] | [time] | [time] |\n| Best for | [scenario] | [scenario] | [scenario] |\n\n\n**Which option would you like to proceed with?**\n```\n\n#### Guidelines for Presentation\n\n1. **Mark recommendation clearly** with ⭐ or \"(Recommended)\"\n2. **Limit to 2-4 options** (too many = decision paralysis)\n3. **Be honest about cons** (don't oversell any option)\n4. **Make comparison easy** (use consistent structure)\n5. **Support with reasoning** (explain why recommendation makes sense)\n\n\n### Phase 5: Support the Choice\n\nAfter user chooses:\n\n```markdown\n✅ **Proceeding with Option [N]: [Name]**\n\n**Next steps:**\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n**I'll now [begin implementation \u002F gather more details \u002F create plan].**\n```\n\nIf user asks for more info on a specific option:\n\n```markdown\n**Deep dive on Option [N]:**\n\n**How it works:**\n[Detailed explanation]\n\n**Implementation steps:**\n1. [Detailed step 1]\n2. [Detailed step 2]\n...\n\n**Potential issues and mitigations:**\n- Issue: [potential problem]\n  Mitigation: [how to handle it]\n\n**Would you like to proceed with this option?**\n```\n\n\n## Common Patterns\n\n### Pattern 1: \"Fix or Provide Options\"\n\n```\nUser: \"The auth system is broken. Fix or provide options.\"\n\nResponse structure:\n1. Assess: Is the fix obvious or are there choices?\n2. If obvious: Present the fix + ask for confirmation\n3. If choices: Present options with trade-offs\n\nExample:\n\nI can see the auth issue. Here are your options:\n\n**Option 1: Quick Fix** (Recommended for immediate deployment)\n- Patch the current JWT validation\n- Pros: Fast, low risk\n- Cons: Doesn't address underlying architecture\n\n**Option 2: Comprehensive Refactor**\n- Rebuild auth with better patterns\n- Pros: Long-term solution\n- Cons: Takes longer, more testing needed\n\n**Which approach fits your timeline?**\n```\n\n### Pattern 2: \"What Are My Options\"\n\n```\nUser: \"I need to add caching. What are my options?\"\n\nResponse structure:\n1. Understand requirements (what needs caching, scale, etc.)\n2. Generate 3-4 caching options\n3. Present with trade-offs\n4. Recommend based on their context\n\nExample:\n\nFor caching your API responses, here are the main options:\n\n**Option 1: In-Memory Cache (Node-cache)** ⭐\n- Best for: Single-server setup\n- Pros: Simple, fast, no external dependencies\n- Cons: Lost on restart, doesn't scale across servers\n\n**Option 2: Redis**\n- Best for: Multi-server or persistence needed\n- Pros: Persistent, distributed, feature-rich\n- Cons: Requires Redis server, more complex\n\n**Option 3: CDN Caching (Cloudflare\u002FFastly)**\n- Best for: Static\u002Fsemi-static content\n- Pros: Global distribution, handles scale\n- Cons: Less control, costs, public content only\n\n**Based on your single-server setup, Option 1 is recommended.**\nWhich would you like to use?\n```\n\n### Pattern 3: \"Help Me Decide\"\n\n```\nUser: \"Should I use TypeScript or stick with JavaScript? Help me decide.\"\n\nResponse structure:\n1. Clarify decision factors (team size, project scope, timeline)\n2. Present structured comparison\n3. Make recommendation based on their specific context\n4. Support whatever they choose\n\nExample:\n\nLet me help you decide between TypeScript and JavaScript.\n\n**TypeScript:**\nPros: Type safety, better tooling, catches errors early\nCons: Learning curve, build step, more setup\nBest for: Larger teams, long-term projects, complex domains\n\n**JavaScript:**\nPros: Simpler, no build step, familiar to all devs\nCons: Runtime errors, less IDE support, harder to refactor\nBest for: Small projects, prototypes, simple applications\n\n**For your [context]:** I recommend TypeScript because [reason].\n\nWould you like to proceed with TypeScript, or would JavaScript be better for your needs?\n```\n\n\n## Integration with Other Skills\n\n### With flow-probe\n\n```\nNeed to research options thoroughly?\n→ Use flow-probe to gather information\n→ Use skill-decision-support to present findings as options\n```\n\n### With flow-tangle\n\n```\nUser chose an option?\n→ Use flow-tangle to implement the chosen approach\n```\n\n### With skill-debug\n\n```\nBug could be fixed multiple ways?\n→ Use skill-decision-support to present fix options\n→ Use skill-debug to implement chosen fix systematically\n```\n\n\n## Best Practices\n\n### 1. Tailor to User's Needs\n\n**Ask about constraints:**\n```markdown\nBefore presenting options, I need to understand:\n- Timeline: How urgent is this?\n- Resources: What's available (team size, budget, infrastructure)?\n- Risk tolerance: Is this production-critical or experimental?\n- Reversibility: Must this decision be reversible?\n```\n\n### 2. Quantify When Possible\n\n**Good:**\n```\n**Timeline:**\n- Option 1: 2-3 hours\n- Option 2: 1-2 days\n- Option 3: 1 week\n```\n\n**Poor:**\n```\n**Timeline:**\n- Option 1: Quick\n- Option 2: A while\n- Option 3: Longer\n```\n\n### 3. Be Honest About Unknowns\n\n```\n**Option 2: Microservices Architecture**\n\n⚠️ **Unknown:** Migration effort could be 2-4 weeks depending on current coupling.\nWould need to audit codebase to give accurate estimate.\n```\n\n### 4. Provide \"Escape Hatch\"\n\nAlways include:\n```\n**Not satisfied with these options?**\n\nI can also:\n- Research more alternatives\n- Combine aspects of multiple options\n- Deep-dive on any specific approach\n- Prototype a solution to test viability\n```\n\n\n## Red Flags - Don't Do This\n\n| Action | Why It's Wrong |\n|--------|----------------|\n| Only present one \"option\" | That's not a choice |\n| Present 8+ options | Decision paralysis |\n| Hide significant cons | User can't make informed choice |\n| Recommend without reasoning | User can't evaluate recommendation |\n| Ignore stated constraints | Wasting user's time |\n| Present obviously bad options as viable | Undermines trust |\n\n\n## Quick Reference\n\n| User Request | Action |\n|--------------|--------|\n| \"fix or provide options\" | Assess if fix obvious → If yes: present fix, if no: present options |\n| \"what are my options\" | Understand context → Generate 2-4 options → Present with trade-offs |\n| \"help me decide\" | Clarify decision factors → Compare approaches → Recommend with reasoning |\n| \"show alternatives\" | Generate alternatives → Analyze pros\u002Fcons → Present structured comparison |\n\n\n## The Bottom Line\n\n```\nDecision support → Clear options + Honest trade-offs + Reasoned recommendation\nOtherwise → Confusion + Poor decisions + Regret\n```\n\n**Understand context. Present real choices. Support with reasoning. Respect their decision.**\n","> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Decision Support & Options Presentation\n\n## Overview\n\nStructured approach to presenting options and alternatives with clear trade-offs, enabling informed decision-making.\n\n**Core principle:** Understand context → Generate options → Analyze trade-offs → Present clearly → Support choice.\n\n\n## When to Use\n\n**Use this skill when user:**\n- Asks for options or alternatives\n- Says \"fix or provide options\"\n- Needs help deciding between approaches\n- Wants to see different ways to solve a problem\n- Is uncertain about best path forward\n\n**Do NOT use for:**\n- General research (\"what is X?\") → use flow-probe\n- Implementation work → use flow-tangle\n- Simple yes\u002Fno questions\n- Already-decided approaches\n\n\n## The Process\n\n### Phase 1: Context Understanding\n\n#### Step 1: Understand the Decision Point\n\n```markdown\n**Decision Context:**\n\nWhat needs to be decided: [the core question]\nWhy it matters: [impact of this decision]\nConstraints: [time, resources, compatibility, etc.]\nCurrent state: [what exists now]\n```\n\n#### Step 2: Gather Requirements\n\nUse AskUserQuestion if needed to understand:\n- Must-have requirements\n- Nice-to-have features\n- Deal-breakers\n- Timeline constraints\n- Budget\u002Fresource constraints\n\n\n### Phase 2: Generate Options\n\n#### Step 1: Identify Viable Approaches\n\nGenerate 2-4 distinct options (not just variations):\n\n| Option Type | When to Include |\n|-------------|-----------------|\n| **Conservative** | Low risk, proven approach |\n| **Moderate** | Balanced risk\u002Freward |\n| **Innovative** | Higher risk, potentially better outcome |\n| **Minimal** | Simplest possible solution |\n\n**Don't generate options that:**\n- Violate stated constraints\n- Are clearly inferior to others\n- Are essentially the same with minor tweaks\n\n#### Step 2: Research Each Option\n\nFor each option, understand:\n- How it works\n- What it requires\n- What the outcome looks like\n- What could go wrong\n\n\n### Phase 3: Trade-off Analysis\n\nFor each option, analyze:\n\n```markdown\n### Option N: [Name]\n\n**Description:**\n[1-2 sentence description]\n\n**Pros:**\n- ✅ [Advantage 1]\n- ✅ [Advantage 2]\n- ✅ [Advantage 3]\n\n**Cons:**\n- ❌ [Disadvantage 1]\n- ❌ [Disadvantage 2]\n- ❌ [Disadvantage 3]\n\n**Effort:** [Low\u002FMedium\u002FHigh]\n**Risk:** [Low\u002FMedium\u002FHigh]\n**Reversibility:** [Easy\u002FModerate\u002FDifficult to undo]\n\n**Best for:** [when this option makes sense]\n```\n\n\n### Phase 4: Present Options\n\n#### Format for Presentation\n\n```markdown\n# Decision: [What needs to be decided]\n\n**Context:** [Brief summary of why this decision is needed]\n\n\n## Option 1: [Conservative\u002FProven Approach] ⭐ (Recommended)\n\n**What it is:**\n[Clear explanation in 1-2 sentences]\n\n**Pros:**\n- ✅ [Pro 1]\n- ✅ [Pro 2]\n- ✅ [Pro 3]\n\n**Cons:**\n- ❌ [Con 1]\n- ❌ [Con 2]\n\n**Implementation:**\n[Brief overview of what's involved]\n\n**Timeline:** [estimate]\n**Risk Level:** Low\u002FMedium\u002FHigh\n\n\n## Option 2: [Alternative Approach]\n\n[Same structure as Option 1]\n\n\n## Option 3: [Another Alternative]\n\n[Same structure as Option 1]\n\n\n## Recommendation\n\n**I recommend Option [N]: [Name]**\n\n**Why:**\n1. [Reason 1]\n2. [Reason 2]\n3. [Reason 3]\n\n**This option is best because:** [summary of key advantage relative to context]\n\n\n## Quick Comparison\n\n| Criteria | Option 1 | Option 2 | Option 3 |\n|----------|----------|----------|----------|\n| Effort | [level] | [level] | [level] |\n| Risk | [level] | [level] | [level] |\n| Reversible | [yes\u002Fno] | [yes\u002Fno] | [yes\u002Fno] |\n| Timeline | [time] | [time] | [time] |\n| Best for | [scenario] | [scenario] | [scenario] |\n\n\n**Which option would you like to proceed with?**\n```\n\n#### Guidelines for Presentation\n\n1. **Mark recommendation clearly** with ⭐ or \"(Recommended)\"\n2. **Limit to 2-4 options** (too many = decision paralysis)\n3. **Be honest about cons** (don't oversell any option)\n4. **Make comparison easy** (use consistent structure)\n5. **Support with reasoning** (explain why recommendation makes sense)\n\n\n### Phase 5: Support the Choice\n\nAfter user chooses:\n\n```markdown\n✅ **Proceeding with Option [N]: [Name]**\n\n**Next steps:**\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n**I'll now [begin implementation \u002F gather more details \u002F create plan].**\n```\n\nIf user asks for more info on a specific option:\n\n```markdown\n**Deep dive on Option [N]:**\n\n**How it works:**\n[Detailed explanation]\n\n**Implementation steps:**\n1. [Detailed step 1]\n2. [Detailed step 2]\n...\n\n**Potential issues and mitigations:**\n- Issue: [potential problem]\n  Mitigation: [how to handle it]\n\n**Would you like to proceed with this option?**\n```\n\n\n## Common Patterns\n\n### Pattern 1: \"Fix or Provide Options\"\n\n```\nUser: \"The auth system is broken. Fix or provide options.\"\n\nResponse structure:\n1. Assess: Is the fix obvious or are there choices?\n2. If obvious: Present the fix + ask for confirmation\n3. If choices: Present options with trade-offs\n\nExample:\n\nI can see the auth issue. Here are your options:\n\n**Option 1: Quick Fix** (Recommended for immediate deployment)\n- Patch the current JWT validation\n- Pros: Fast, low risk\n- Cons: Doesn't address underlying architecture\n\n**Option 2: Comprehensive Refactor**\n- Rebuild auth with better patterns\n- Pros: Long-term solution\n- Cons: Takes longer, more testing needed\n\n**Which approach fits your timeline?**\n```\n\n### Pattern 2: \"What Are My Options\"\n\n```\nUser: \"I need to add caching. What are my options?\"\n\nResponse structure:\n1. Understand requirements (what needs caching, scale, etc.)\n2. Generate 3-4 caching options\n3. Present with trade-offs\n4. Recommend based on their context\n\nExample:\n\nFor caching your API responses, here are the main options:\n\n**Option 1: In-Memory Cache (Node-cache)** ⭐\n- Best for: Single-server setup\n- Pros: Simple, fast, no external dependencies\n- Cons: Lost on restart, doesn't scale across servers\n\n**Option 2: Redis**\n- Best for: Multi-server or persistence needed\n- Pros: Persistent, distributed, feature-rich\n- Cons: Requires Redis server, more complex\n\n**Option 3: CDN Caching (Cloudflare\u002FFastly)**\n- Best for: Static\u002Fsemi-static content\n- Pros: Global distribution, handles scale\n- Cons: Less control, costs, public content only\n\n**Based on your single-server setup, Option 1 is recommended.**\nWhich would you like to use?\n```\n\n### Pattern 3: \"Help Me Decide\"\n\n```\nUser: \"Should I use TypeScript or stick with JavaScript? Help me decide.\"\n\nResponse structure:\n1. Clarify decision factors (team size, project scope, timeline)\n2. Present structured comparison\n3. Make recommendation based on their specific context\n4. Support whatever they choose\n\nExample:\n\nLet me help you decide between TypeScript and JavaScript.\n\n**TypeScript:**\nPros: Type safety, better tooling, catches errors early\nCons: Learning curve, build step, more setup\nBest for: Larger teams, long-term projects, complex domains\n\n**JavaScript:**\nPros: Simpler, no build step, familiar to all devs\nCons: Runtime errors, less IDE support, harder to refactor\nBest for: Small projects, prototypes, simple applications\n\n**For your [context]:** I recommend TypeScript because [reason].\n\nWould you like to proceed with TypeScript, or would JavaScript be better for your needs?\n```\n\n\n## Integration with Other Skills\n\n### With flow-probe\n\n```\nNeed to research options thoroughly?\n→ Use flow-probe to gather information\n→ Use skill-decision-support to present findings as options\n```\n\n### With flow-tangle\n\n```\nUser chose an option?\n→ Use flow-tangle to implement the chosen approach\n```\n\n### With skill-debug\n\n```\nBug could be fixed multiple ways?\n→ Use skill-decision-support to present fix options\n→ Use skill-debug to implement chosen fix systematically\n```\n\n\n## Best Practices\n\n### 1. Tailor to User's Needs\n\n**Ask about constraints:**\n```markdown\nBefore presenting options, I need to understand:\n- Timeline: How urgent is this?\n- Resources: What's available (team size, budget, infrastructure)?\n- Risk tolerance: Is this production-critical or experimental?\n- Reversibility: Must this decision be reversible?\n```\n\n### 2. Quantify When Possible\n\n**Good:**\n```\n**Timeline:**\n- Option 1: 2-3 hours\n- Option 2: 1-2 days\n- Option 3: 1 week\n```\n\n**Poor:**\n```\n**Timeline:**\n- Option 1: Quick\n- Option 2: A while\n- Option 3: Longer\n```\n\n### 3. Be Honest About Unknowns\n\n```\n**Option 2: Microservices Architecture**\n\n⚠️ **Unknown:** Migration effort could be 2-4 weeks depending on current coupling.\nWould need to audit codebase to give accurate estimate.\n```\n\n### 4. Provide \"Escape Hatch\"\n\nAlways include:\n```\n**Not satisfied with these options?**\n\nI can also:\n- Research more alternatives\n- Combine aspects of multiple options\n- Deep-dive on any specific approach\n- Prototype a solution to test viability\n```\n\n\n## Red Flags - Don't Do This\n\n| Action | Why It's Wrong |\n|--------|----------------|\n| Only present one \"option\" | That's not a choice |\n| Present 8+ options | Decision paralysis |\n| Hide significant cons | User can't make informed choice |\n| Recommend without reasoning | User can't evaluate recommendation |\n| Ignore stated constraints | Wasting user's time |\n| Present obviously bad options as viable | Undermines trust |\n\n\n## Quick Reference\n\n| User Request | Action |\n|--------------|--------|\n| \"fix or provide options\" | Assess if fix obvious → If yes: present fix, if no: present options |\n| \"what are my options\" | Understand context → Generate 2-4 options → Present with trade-offs |\n| \"help me decide\" | Clarify decision factors → Compare approaches → Recommend with reasoning |\n| \"show alternatives\" | Generate alternatives → Analyze pros\u002Fcons → Present structured comparison |\n\n\n## The Bottom Line\n\n```\nDecision support → Clear options + Honest trade-offs + Reasoned recommendation\nOtherwise → Confusion + Poor decisions + Regret\n```\n\n**Understand context. Present real choices. Support with reasoning. Respect their decision.**\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fskill-decision-support",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":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-decision-support",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-decision-support",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-decision-support","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-decision-support\u002FSKILL.md",[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",160,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-decision-support\u002Fagents\u002Fopenai.yaml",[53,60,65,72,79,86],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"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",[],[],{"skillNo":61,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"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":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":19},"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"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",[],[]]