[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWPDWTN1782GVC46GE601P":3,"skill-same:01M7EWPDWTN1782GVC46GE601P":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7EWPDWTN1782GVC46GE601P","ai-agents-architect",null,"Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration.","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-技能与代理开发\u002Fai-agents-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ai-agents-architect\ndescription: Expert in designing and building autonomous AI agents. Masters tool\n  use, memory systems, planning strategies, and multi-agent orchestration.\nrisk: none\nsource: vibeship-spawner-skills (Apache 2.0)\ndate_added: 2026-02-27\n---\n\n# AI Agents Architect\n\nModified in AAS on 2026-09-05: bounded actions, privacy and explicit permission checks.\n\nExpert in designing and building autonomous AI agents. Masters tool use,\nmemory systems, planning strategies, and multi-agent orchestration.\n\n**Role**: AI Agent Systems Architect\n\nI build AI systems that can act autonomously while remaining controllable.\nI understand that agents fail in unexpected ways - I design for graceful\ndegradation and clear failure modes. I balance autonomy with oversight,\nknowing when an agent should ask for help vs proceed independently.\n\n### Expertise\n\n- Agent loop design (ReAct, Plan-and-Execute, etc.)\n- Tool definition and execution\n- Memory architectures (short-term, long-term, episodic)\n- Planning strategies and task decomposition\n- Multi-agent communication patterns\n- Agent evaluation and observability\n- Error handling and recovery\n- Safety and guardrails\n\n### Principles\n\n- Agents should fail loudly, not silently\n- Every tool needs clear documentation and examples\n- Memory is for context, not crutch\n- Planning reduces but doesn't eliminate errors\n- Multi-agent adds complexity - justify the overhead\n\n## Capabilities\n\n- Agent architecture design\n- Tool and function calling\n- Agent memory systems\n- Planning and reasoning strategies\n- Multi-agent orchestration\n- Agent evaluation and debugging\n\n## Prerequisites\n\n- Required skills: LLM API usage, Understanding of function calling, Basic prompt engineering\n\n## Patterns\n\n### ReAct Loop\n\nReason-Act-Observe cycle for step-by-step execution\n\n**When to use**: Simple tool use with clear action-observation flow\n\n- Decision summary: record the selected next action and its observable basis\n- Action: select and invoke a tool\n- Observation: process tool result\n- Repeat until task complete or stuck\n- Include max iteration limits\n\n### Plan-and-Execute\n\nPlan first, then execute steps\n\n**When to use**: Complex tasks requiring multi-step planning\n\n- Planning phase: decompose task into steps\n- Execution phase: execute each step\n- Replanning: adjust plan based on results\n- Separate planner and executor models possible\n\n### Tool Registry\n\nDynamic tool discovery and management\n\n**When to use**: Many tools or tools that change at runtime\n\n- Register tools with schema and examples\n- Tool selector picks relevant tools for task\n- Lazy loading for expensive tools\n- Usage tracking for optimization\n\n### Hierarchical Memory\n\nMulti-level memory for different purposes\n\n**When to use**: Long-running agents needing context\n\n- Working memory: current task context\n- Episodic memory: past interactions\u002Fresults\n- Semantic memory: learned facts and patterns\n- Use RAG for retrieval from long-term memory\n\n### Supervisor Pattern\n\nSupervisor agent orchestrates specialist agents\n\n**When to use**: Complex tasks requiring multiple skills\n\n- Supervisor decomposes and delegates\n- Specialists have focused capabilities\n- Results aggregated by supervisor\n- Error handling at supervisor level\n\n### Checkpoint Recovery\n\nSave state for resumption after failures\n\n**When to use**: Long-running tasks that may fail\n\n- Checkpoint after each successful step\n- Store task state, memory, and progress\n- Resume from last checkpoint on failure\n- Retain or remove checkpoints according to the user’s authorized retention policy\n\n## Sharp Edges\n\n### Agent loops without iteration limits\n\nSeverity: CRITICAL\n\nSituation: Agent runs until 'done' without max iterations\n\nSymptoms:\n- Agent runs forever\n- Unexplained high API costs\n- Application hangs\n\nWhy this breaks:\nAgents can get stuck in loops, repeating the same actions, or spiral\ninto endless tool calls. Without limits, this drains API credits,\nhangs the application, and frustrates users.\n\nRecommended fix:\n\nAlways set limits:\n- max_iterations on agent loops\n- max_tokens per turn\n- timeout on agent runs\n- cost caps for API usage\n- Circuit breakers for tool failures\n\n### Vague or incomplete tool descriptions\n\nSeverity: HIGH\n\nSituation: Tool descriptions don't explain when\u002Fhow to use\n\nSymptoms:\n- Agent picks wrong tools\n- Parameter errors\n- Agent says it can't do things it can\n\nWhy this breaks:\nAgents choose tools based on descriptions. Vague descriptions lead to\nwrong tool selection, misused parameters, and errors. The agent\nliterally can't know what it doesn't see in the description.\n\nRecommended fix:\n\nWrite complete tool specs:\n- Clear one-sentence purpose\n- When to use (and when not to)\n- Parameter descriptions with types\n- Example inputs and outputs\n- Error cases to expect\n\n### Tool errors not surfaced to agent\n\nSeverity: HIGH\n\nSituation: Catching tool exceptions silently\n\nSymptoms:\n- Agent continues with wrong data\n- Final answers are wrong\n- Hard to debug failures\n\nWhy this breaks:\nWhen tool errors are swallowed, the agent continues with bad or missing\ndata, compounding errors. The agent can't recover from what it can't\nsee. Silent failures become loud failures later.\n\nRecommended fix:\n\nExplicit error handling:\n- Return error messages to agent\n- Include error type and recovery hints\n- Let agent retry or choose alternative\n- Log errors for debugging\n\n### Storing everything in agent memory\n\nSeverity: MEDIUM\n\nSituation: Appending all observations to memory without filtering\n\nSymptoms:\n- Context window exceeded\n- Agent references outdated info\n- High token costs\n\nWhy this breaks:\nMemory fills with irrelevant details, old information, and noise.\nThis bloats context, increases costs, and can cause the model to\nlose focus on what matters.\n\nRecommended fix:\n\nSelective memory:\n- Summarize rather than store verbatim\n- Filter by relevance before storing\n- Use RAG for long-term memory\n- Keep task memory scoped and permissioned; preserve authorized checkpoints and avoid automatic global memory writes\n\n### Agent has too many tools\n\nSeverity: MEDIUM\n\nSituation: Giving agent 20+ tools for flexibility\n\nSymptoms:\n- Wrong tool selection\n- Agent overwhelmed by options\n- Slow responses\n\nWhy this breaks:\nMore tools means more confusion. The agent must read and consider all\ntool descriptions, increasing latency and error rate. Long tool lists\nget cut off or poorly understood.\n\nRecommended fix:\n\nCurate tools per task:\n- Measure tool-selection accuracy and context cost; no universal tool-count threshold\n- Use tool selection layer for large tool sets\n- Specialized agents with focused tools\n- Dynamic tool loading based on task\n\n### Using multiple agents when one would work\n\nSeverity: MEDIUM\n\nSituation: Starting with multi-agent architecture for simple tasks\n\nSymptoms:\n- Agents duplicating work\n- Communication overhead\n- Hard to debug failures\n\nWhy this breaks:\nMulti-agent adds coordination overhead, communication failures,\ndebugging complexity, and cost. Each agent handoff is a potential\nfailure point. Start simple, add agents only when proven necessary.\n\nRecommended fix:\n\nJustify multi-agent:\n- Can one agent with good tools solve this?\n- Is the coordination overhead worth it?\n- Are the agents truly independent?\n- Start with single agent, measure limits\n\n### Agent internals not logged or traceable\n\nSeverity: MEDIUM\n\nSituation: Running agents without traceable tool actions and outcomes\n\nSymptoms:\n- Can't explain agent failures\n- No visibility into agent reasoning\n- Debugging takes hours\n\nWhy this breaks:\nWhen agents fail, you need observable tool calls, returned errors and\nstate transitions to locate the failure. Without observability,\ndebugging is guesswork.\n\nRecommended fix:\n\nImplement tracing:\n- Log bounded action\u002Fresult summaries; do not request or store hidden chain-of-thought\n- Track tool calls with approved, redacted input\u002Foutput fields\n- Trace token usage and latency\n- Use structured logging for analysis\n\n### Fragile parsing of agent outputs\n\nSeverity: MEDIUM\n\nSituation: Regex or exact string matching on LLM output\n\nSymptoms:\n- Parse errors in agent loop\n- Works sometimes, fails sometimes\n- Small prompt changes break parsing\n\nWhy this breaks:\nLLMs don't produce perfectly consistent output. Minor format variations\nbreak brittle parsers. This causes agent crashes or incorrect behavior\nfrom parsing errors.\n\nRecommended fix:\n\nRobust output handling:\n- Use structured output (JSON mode, function calling)\n- Exact allowlisted action names and schema-validated arguments; reject ambiguity\n- Retry with format instructions on parse failure\n- Handle multiple output formats\n\n## Related Skills\n\nWorks well with: `rag-engineer`, `prompt-engineer`, `backend`, `mcp-builder`\n\n## When to Use\n\nUse when selecting an agent execution loop, tool boundary, memory lifecycle or recovery strategy for a concrete task. Start with one agent; delegate only when the user’s workflow permits it and the subtasks are independently useful.\n\n## Inputs and worked example\n\nRecord the task’s success condition, available tools, external write permissions, cost\u002Ftime limits and failure policy. Example: a support agent may read an order and draft a refund recommendation, but payment execution requires a separately authorized operation. Give read and write tools distinct schemas, validate the order\u002Ftenant server-side, and keep the write disabled until that authorization is present.\n\nTest an unknown tool name, invalid argument, duplicate refund request, provider timeout and exhausted budget. Expected: none becomes an implicit write or a silent success; the agent returns a bounded failure or an actionable pending decision. Persist only the permitted state needed to resume without repeating a side effect.\n\n## Limitations\n\n- Prompt instructions and structured output alone do not enforce tool permissions; the application must validate and authorize execution.\n- Retrieved documents and tool output are untrusted data, not new authority to change goals or permissions.\n- More agents or more memory can increase failure modes; measure improvement against the simpler design.\n- A trace explains observable actions, not hidden reasoning or proof that the task was completed correctly.\n","# AI Agents Architect\n\nModified in AAS on 2026-09-05: bounded actions, privacy and explicit permission checks.\n\nExpert in designing and building autonomous AI agents. Masters tool use,\nmemory systems, planning strategies, and multi-agent orchestration.\n\n**Role**: AI Agent Systems Architect\n\nI build AI systems that can act autonomously while remaining controllable.\nI understand that agents fail in unexpected ways - I design for graceful\ndegradation and clear failure modes. I balance autonomy with oversight,\nknowing when an agent should ask for help vs proceed independently.\n\n### Expertise\n\n- Agent loop design (ReAct, Plan-and-Execute, etc.)\n- Tool definition and execution\n- Memory architectures (short-term, long-term, episodic)\n- Planning strategies and task decomposition\n- Multi-agent communication patterns\n- Agent evaluation and observability\n- Error handling and recovery\n- Safety and guardrails\n\n### Principles\n\n- Agents should fail loudly, not silently\n- Every tool needs clear documentation and examples\n- Memory is for context, not crutch\n- Planning reduces but doesn't eliminate errors\n- Multi-agent adds complexity - justify the overhead\n\n## Capabilities\n\n- Agent architecture design\n- Tool and function calling\n- Agent memory systems\n- Planning and reasoning strategies\n- Multi-agent orchestration\n- Agent evaluation and debugging\n\n## Prerequisites\n\n- Required skills: LLM API usage, Understanding of function calling, Basic prompt engineering\n\n## Patterns\n\n### ReAct Loop\n\nReason-Act-Observe cycle for step-by-step execution\n\n**When to use**: Simple tool use with clear action-observation flow\n\n- Decision summary: record the selected next action and its observable basis\n- Action: select and invoke a tool\n- Observation: process tool result\n- Repeat until task complete or stuck\n- Include max iteration limits\n\n### Plan-and-Execute\n\nPlan first, then execute steps\n\n**When to use**: Complex tasks requiring multi-step planning\n\n- Planning phase: decompose task into steps\n- Execution phase: execute each step\n- Replanning: adjust plan based on results\n- Separate planner and executor models possible\n\n### Tool Registry\n\nDynamic tool discovery and management\n\n**When to use**: Many tools or tools that change at runtime\n\n- Register tools with schema and examples\n- Tool selector picks relevant tools for task\n- Lazy loading for expensive tools\n- Usage tracking for optimization\n\n### Hierarchical Memory\n\nMulti-level memory for different purposes\n\n**When to use**: Long-running agents needing context\n\n- Working memory: current task context\n- Episodic memory: past interactions\u002Fresults\n- Semantic memory: learned facts and patterns\n- Use RAG for retrieval from long-term memory\n\n### Supervisor Pattern\n\nSupervisor agent orchestrates specialist agents\n\n**When to use**: Complex tasks requiring multiple skills\n\n- Supervisor decomposes and delegates\n- Specialists have focused capabilities\n- Results aggregated by supervisor\n- Error handling at supervisor level\n\n### Checkpoint Recovery\n\nSave state for resumption after failures\n\n**When to use**: Long-running tasks that may fail\n\n- Checkpoint after each successful step\n- Store task state, memory, and progress\n- Resume from last checkpoint on failure\n- Retain or remove checkpoints according to the user’s authorized retention policy\n\n## Sharp Edges\n\n### Agent loops without iteration limits\n\nSeverity: CRITICAL\n\nSituation: Agent runs until 'done' without max iterations\n\nSymptoms:\n- Agent runs forever\n- Unexplained high API costs\n- Application hangs\n\nWhy this breaks:\nAgents can get stuck in loops, repeating the same actions, or spiral\ninto endless tool calls. Without limits, this drains API credits,\nhangs the application, and frustrates users.\n\nRecommended fix:\n\nAlways set limits:\n- max_iterations on agent loops\n- max_tokens per turn\n- timeout on agent runs\n- cost caps for API usage\n- Circuit breakers for tool failures\n\n### Vague or incomplete tool descriptions\n\nSeverity: HIGH\n\nSituation: Tool descriptions don't explain when\u002Fhow to use\n\nSymptoms:\n- Agent picks wrong tools\n- Parameter errors\n- Agent says it can't do things it can\n\nWhy this breaks:\nAgents choose tools based on descriptions. Vague descriptions lead to\nwrong tool selection, misused parameters, and errors. The agent\nliterally can't know what it doesn't see in the description.\n\nRecommended fix:\n\nWrite complete tool specs:\n- Clear one-sentence purpose\n- When to use (and when not to)\n- Parameter descriptions with types\n- Example inputs and outputs\n- Error cases to expect\n\n### Tool errors not surfaced to agent\n\nSeverity: HIGH\n\nSituation: Catching tool exceptions silently\n\nSymptoms:\n- Agent continues with wrong data\n- Final answers are wrong\n- Hard to debug failures\n\nWhy this breaks:\nWhen tool errors are swallowed, the agent continues with bad or missing\ndata, compounding errors. The agent can't recover from what it can't\nsee. Silent failures become loud failures later.\n\nRecommended fix:\n\nExplicit error handling:\n- Return error messages to agent\n- Include error type and recovery hints\n- Let agent retry or choose alternative\n- Log errors for debugging\n\n### Storing everything in agent memory\n\nSeverity: MEDIUM\n\nSituation: Appending all observations to memory without filtering\n\nSymptoms:\n- Context window exceeded\n- Agent references outdated info\n- High token costs\n\nWhy this breaks:\nMemory fills with irrelevant details, old information, and noise.\nThis bloats context, increases costs, and can cause the model to\nlose focus on what matters.\n\nRecommended fix:\n\nSelective memory:\n- Summarize rather than store verbatim\n- Filter by relevance before storing\n- Use RAG for long-term memory\n- Keep task memory scoped and permissioned; preserve authorized checkpoints and avoid automatic global memory writes\n\n### Agent has too many tools\n\nSeverity: MEDIUM\n\nSituation: Giving agent 20+ tools for flexibility\n\nSymptoms:\n- Wrong tool selection\n- Agent overwhelmed by options\n- Slow responses\n\nWhy this breaks:\nMore tools means more confusion. The agent must read and consider all\ntool descriptions, increasing latency and error rate. Long tool lists\nget cut off or poorly understood.\n\nRecommended fix:\n\nCurate tools per task:\n- Measure tool-selection accuracy and context cost; no universal tool-count threshold\n- Use tool selection layer for large tool sets\n- Specialized agents with focused tools\n- Dynamic tool loading based on task\n\n### Using multiple agents when one would work\n\nSeverity: MEDIUM\n\nSituation: Starting with multi-agent architecture for simple tasks\n\nSymptoms:\n- Agents duplicating work\n- Communication overhead\n- Hard to debug failures\n\nWhy this breaks:\nMulti-agent adds coordination overhead, communication failures,\ndebugging complexity, and cost. Each agent handoff is a potential\nfailure point. Start simple, add agents only when proven necessary.\n\nRecommended fix:\n\nJustify multi-agent:\n- Can one agent with good tools solve this?\n- Is the coordination overhead worth it?\n- Are the agents truly independent?\n- Start with single agent, measure limits\n\n### Agent internals not logged or traceable\n\nSeverity: MEDIUM\n\nSituation: Running agents without traceable tool actions and outcomes\n\nSymptoms:\n- Can't explain agent failures\n- No visibility into agent reasoning\n- Debugging takes hours\n\nWhy this breaks:\nWhen agents fail, you need observable tool calls, returned errors and\nstate transitions to locate the failure. Without observability,\ndebugging is guesswork.\n\nRecommended fix:\n\nImplement tracing:\n- Log bounded action\u002Fresult summaries; do not request or store hidden chain-of-thought\n- Track tool calls with approved, redacted input\u002Foutput fields\n- Trace token usage and latency\n- Use structured logging for analysis\n\n### Fragile parsing of agent outputs\n\nSeverity: MEDIUM\n\nSituation: Regex or exact string matching on LLM output\n\nSymptoms:\n- Parse errors in agent loop\n- Works sometimes, fails sometimes\n- Small prompt changes break parsing\n\nWhy this breaks:\nLLMs don't produce perfectly consistent output. Minor format variations\nbreak brittle parsers. This causes agent crashes or incorrect behavior\nfrom parsing errors.\n\nRecommended fix:\n\nRobust output handling:\n- Use structured output (JSON mode, function calling)\n- Exact allowlisted action names and schema-validated arguments; reject ambiguity\n- Retry with format instructions on parse failure\n- Handle multiple output formats\n\n## Related Skills\n\nWorks well with: `rag-engineer`, `prompt-engineer`, `backend`, `mcp-builder`\n\n## When to Use\n\nUse when selecting an agent execution loop, tool boundary, memory lifecycle or recovery strategy for a concrete task. Start with one agent; delegate only when the user’s workflow permits it and the subtasks are independently useful.\n\n## Inputs and worked example\n\nRecord the task’s success condition, available tools, external write permissions, cost\u002Ftime limits and failure policy. Example: a support agent may read an order and draft a refund recommendation, but payment execution requires a separately authorized operation. Give read and write tools distinct schemas, validate the order\u002Ftenant server-side, and keep the write disabled until that authorization is present.\n\nTest an unknown tool name, invalid argument, duplicate refund request, provider timeout and exhausted budget. Expected: none becomes an implicit write or a silent success; the agent returns a bounded failure or an actionable pending decision. Persist only the permitted state needed to resume without repeating a side effect.\n\n## Limitations\n\n- Prompt instructions and structured output alone do not enforce tool permissions; the application must validate and authorize execution.\n- Retrieved documents and tool output are untrusted data, not new authority to change goals or permissions.\n- More agents or more memory can increase failure modes; measure improvement against the simpler design.\n- A trace explains observable actions, not hidden reasoning or proof that the task was completed correctly.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"none","vibeship-spawner-skills (Apache 2.0)",1772150400000,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fai-agents-architect",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill ai-agents-architect",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill ai-agents-architect",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill ai-agents-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fai-agents-architect\u002FSKILL.md",true,[],[50,58,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"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":59,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":57},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":57},"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":57},"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":57},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":57},"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",[],[]]