[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DDSEQXMRRYSRPHN2T1SYNM":3,"skill-same:01M6DDSEQXMRRYSRPHN2T1SYNM":77},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6DDSEQXMRRYSRPHN2T1SYNM","agent-architecture-audit",null,"Use when agent architecture audit is needed. Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first.","Prekzursil\u002Fagent-skills-toolchain","Prekzursil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54636077?v=4","01M6DACZ1PCQHD99SCR1YXG28B","Andrei Mihai Visalon","01M6DACZ670WZF535V3WYYSS4Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Fskills\u002Fagent-architecture-audit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"architecture","agent architecture audit","agent architecture","audit","regression","memory","pollution","repair","discipline","use","write","read","check","tool","stack","Bash","first","applications","severity","code","2026-11-10 10:12:30",false,"---\nname: agent-architecture-audit\ndescription: \"Use when agent architecture audit is needed. Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first.\"\norigin: oh-my-agent-check\ntools: Read, Write, Edit, Bash, Grep, Glob\n---\n\n# Agent Architecture Audit\n\nA diagnostic workflow for agent systems that hide failures behind wrapper layers, stale memory, retry loops, or transport\u002Frendering mutations.\n\n## When to Activate\n\n**MANDATORY for:**\n- Releasing any agent or LLM-powered application to production\n- Shipping features with tool calling, memory, or multi-step workflows\n- Agent behavior degrades after adding wrapper layers\n- User reports \"the agent is getting worse\" or \"tools are flaky\"\n- Same model works in playground but breaks inside your wrapper\n- Debugging agent behavior for more than 15 minutes without finding root cause\n\n**Especially critical when:**\n- You've added new prompt layers, tool definitions, or memory systems\n- Different agents in your system behave inconsistently\n- The model was fine yesterday but is hallucinating today\n- You suspect hidden repair\u002Fretry loops silently mutating responses\n\n**Do not use for:**\n- General code debugging — use `agent-introspection-debugging`\n- Code review — use language-specific reviewer agents\n- Security scanning — use `security-review` or `security-review\u002Fscan`\n- Agent performance benchmarking — use `agent-eval`\n- Writing new features — use the appropriate workflow skill\n\n## The 12-Layer Stack\n\nEvery agent system has these layers. Any of them can corrupt the answer:\n\n| # | Layer | What Goes Wrong |\n|---|-------|----------------|\n| 1 | System prompt | Conflicting instructions, instruction bloat |\n| 2 | Session history | Stale context injection from previous turns |\n| 3 | Long-term memory | Pollution across sessions, old topics in new conversations |\n| 4 | Distillation | Compressed artifacts re-entering as pseudo-facts |\n| 5 | Active recall | Redundant re-summary layers wasting context |\n| 6 | Tool selection | Wrong tool routing, model skips required tools |\n| 7 | Tool execution | Hallucinated execution — claims to call but doesn't |\n| 8 | Tool interpretation | Misread or ignored tool output |\n| 9 | Answer shaping | Format corruption in final response |\n| 10 | Platform rendering | Transport-layer mutation (UI, API, CLI mutates valid answers) |\n| 11 | Hidden repair loops | Silent fallback\u002Fretry agents running second LLM pass |\n| 12 | Persistence | Expired state or cached artifacts reused as live evidence |\n\n## Common Failure Patterns\n\n### 1. Wrapper Regression\n\nThe base model produces correct answers, but the wrapper layers make it worse.\n\n**Symptoms:**\n- Model works fine in playground or direct API call, breaks in your agent\n- Added a new prompt layer, existing behavior degraded\n- Agent sounds confident but is confidently wrong\n- \"It was working before the last update\"\n\n### 2. Memory Contamination\n\nOld topics leak into new conversations through history, memory retrieval, or distillation.\n\n**Symptoms:**\n- Agent brings up unrelated past topics\n- User corrections don't stick (old memory overwrites new)\n- Same-session artifacts re-enter as pseudo-facts\n- Memory grows without bound, degrading response quality over time\n\n### 3. Tool Discipline Failure\n\nTools are declared in the prompt but not enforced in code. The model skips them or hallucinates execution.\n\n**Symptoms:**\n- \"Must use tool X\" in prompt, but model answers without calling it\n- Tool results look correct but were never actually executed\n- Different tools fight over the same responsibility\n- Model uses tool when it shouldn't, or skips it when it must\n\n### 4. Rendering\u002FTransport Corruption\n\nThe agent's internal answer is correct, but the platform layer mutates it during delivery.\n\n**Symptoms:**\n- Logs show correct answer, user sees broken output\n- Markdown rendering, JSON parsing, or streaming fragments corrupt valid responses\n- Hidden fallback agent quietly replaces the answer before delivery\n- Output differs between terminal and UI\n\n### 5. Hidden Agent Layers\n\nSilent repair, retry, summarization, or recall agents run without explicit contracts.\n\n**Symptoms:**\n- Output changes between internal generation and user delivery\n- \"Auto-fix\" loops run a second LLM pass the user doesn't know about\n- Multiple agents modify the same output without coordination\n- Answers get \"smoothed\" or \"corrected\" by invisible layers\n\n## Audit Workflow\n\n### Phase 1: Scope\n\nDefine what you're auditing:\n\n- **Target system** — what agent application?\n- **Entrypoints** — how do users interact with it?\n- **Model stack** — which LLM(s) and providers?\n- **Symptoms** — what does the user report?\n- **Time window** — when did it start?\n- **Layers to audit** — which of the 12 layers apply?\n\n### Phase 2: Evidence Collection\n\nGather evidence from the codebase:\n\n- **Source code** — agent loop, tool router, memory admission, prompt assembly\n- **Logs** — historical session traces, tool call records\n- **Config** — prompt templates, tool schemas, provider settings\n- **Memory files** — SOPs, knowledge bases, session archives\n\nUse `rg` to search for anti-patterns:\n\n```bash\n# Tool requirements expressed only in prompt text (not code)\nrg \"must.*tool|必须.*工具|required.*call\" --type md\n\n# Tool execution without validation\nrg \"tool_call|toolCall|tool_use\" --type py --type ts\n\n# Hidden LLM calls outside main agent loop\nrg \"completion|chat\\.create|messages\\.create|llm\\.invoke\"\n\n# Memory admission without user-correction priority\nrg \"memory.*admit|long.*term.*update|persist.*memory\" --type py --type ts\n\n# Fallback loops that run additional LLM calls\nrg \"fallback|retry.*llm|repair.*prompt|re-?prompt\" --type py --type ts\n\n# Silent output mutation\nrg \"mutate|rewrite.*response|transform.*output|shap\" --type py --type ts\n```\n\n### Phase 3: Failure Mapping\n\nFor each finding, document:\n\n- **Symptom** — what the user sees\n- **Mechanism** — how the wrapper causes it\n- **Source layer** — which of the 12 layers\n- **Root cause** — the deepest cause\n- **Evidence** — file:line or log:row reference\n- **Confidence** — 0.0 to 1.0\n\n### Phase 4: Fix Strategy\n\nDefault fix order (code-first, not prompt-first):\n\n1. **Code-gate tool requirements** — enforce in code, not just prompt text\n2. **Remove or narrow hidden repair agents** — make fallback explicit with contracts\n3. **Reduce context duplication** — same info through prompt + history + memory + distillation\n4. **Tighten memory admission** — user corrections > agent assertions\n5. **Tighten distillation triggers** — don't compress what shouldn't be compressed\n6. **Reduce rendering mutation** — pass-through, don't transform\n7. **Convert to typed JSON envelopes** — structured internal flow, not freeform prose\n\n## Severity Model\n\n| Level | Meaning | Action |\n|-------|---------|--------|\n| `critical` | Agent can confidently produce wrong operational behavior | Fix before next release |\n| `high` | Agent frequently degrades correctness or stability | Fix this sprint |\n| `medium` | Correctness usually survives but output is fragile or wasteful | Plan for next cycle |\n| `low` | Mostly cosmetic or maintainability issues | Backlog |\n\n## Output Format\n\nPresent findings to the user in this order:\n\n1. **Severity-ranked findings** (most critical first)\n2. **Architecture diagnosis** (which layer corrupted what, and why)\n3. **Ordered fix plan** (code-first, not prompt-first)\n\nDo not lead with compliments or summaries. If the system is broken, say so directly.\n\n## Quick Diagnostic Questions\n\nWhen auditing an agent system, answer these:\n\n| # | Question | If Yes → |\n|---|----------|----------|\n| 1 | Can the model skip a required tool and still answer? | Tool not code-gated |\n| 2 | Does old conversation content appear in new turns? | Memory contamination |\n| 3 | Is the same info in system prompt AND memory AND history? | Context duplication |\n| 4 | Does the platform run a second LLM pass before delivery? | Hidden repair loop |\n| 5 | Does the output differ between internal generation and user delivery? | Rendering corruption |\n| 6 | Are \"must use tool X\" rules only in prompt text? | Tool discipline failure |\n| 7 | Can the agent's own monologue become persistent memory? | Memory poisoning |\n\n## Anti-Patterns to Avoid\n\n- Avoid blaming the model before falsifying wrapper-layer regressions.\n- Avoid blaming memory without showing the contamination path.\n- Do not let a clean current state erase a dirty historical incident.\n- Do not treat markdown prose as a trustworthy internal protocol.\n- Do not accept \"must use tool\" in prompt text when code never enforces it.\n- Keep findings direct, evidence-backed, and severity-ranked.\n\n## Report Schema\n\nAudits should produce structured reports following this shape:\n\n```json\n{\n  \"schema_version\": \"ecc.agent-architecture-audit.report.v1\",\n  \"executive_verdict\": {\n    \"overall_health\": \"high_risk\",\n    \"primary_failure_mode\": \"string\",\n    \"most_urgent_fix\": \"string\"\n  },\n  \"scope\": {\n    \"target_name\": \"string\",\n    \"model_stack\": [\"string\"],\n    \"layers_to_audit\": [\"string\"]\n  },\n  \"findings\": [\n    {\n      \"severity\": \"critical|high|medium|low\",\n      \"title\": \"string\",\n      \"mechanism\": \"string\",\n      \"source_layer\": \"string\",\n      \"root_cause\": \"string\",\n      \"evidence_refs\": [\"file:line\"],\n      \"confidence\": 0.0,\n      \"recommended_fix\": \"string\"\n    }\n  ],\n  \"ordered_fix_plan\": [\n    { \"order\": 1, \"goal\": \"string\", \"why_now\": \"string\", \"expected_effect\": \"string\" }\n  ]\n}\n```\n\n## Related Skills\n\n- `agent-introspection-debugging` — Debug agent runtime failures (loops, timeouts, state errors)\n- `agent-eval` — Benchmark agent performance head-to-head\n- `security-review` — Security audit for code and configuration\n- `autonomous-agent-harness` — Set up autonomous agent operations\n- `agent-harness-construction` — Build agent harnesses from scratch\n","# Agent Architecture Audit\n\nA diagnostic workflow for agent systems that hide failures behind wrapper layers, stale memory, retry loops, or transport\u002Frendering mutations.\n\n## When to Activate\n\n**MANDATORY for:**\n- Releasing any agent or LLM-powered application to production\n- Shipping features with tool calling, memory, or multi-step workflows\n- Agent behavior degrades after adding wrapper layers\n- User reports \"the agent is getting worse\" or \"tools are flaky\"\n- Same model works in playground but breaks inside your wrapper\n- Debugging agent behavior for more than 15 minutes without finding root cause\n\n**Especially critical when:**\n- You've added new prompt layers, tool definitions, or memory systems\n- Different agents in your system behave inconsistently\n- The model was fine yesterday but is hallucinating today\n- You suspect hidden repair\u002Fretry loops silently mutating responses\n\n**Do not use for:**\n- General code debugging — use `agent-introspection-debugging`\n- Code review — use language-specific reviewer agents\n- Security scanning — use `security-review` or `security-review\u002Fscan`\n- Agent performance benchmarking — use `agent-eval`\n- Writing new features — use the appropriate workflow skill\n\n## The 12-Layer Stack\n\nEvery agent system has these layers. Any of them can corrupt the answer:\n\n| # | Layer | What Goes Wrong |\n|---|-------|----------------|\n| 1 | System prompt | Conflicting instructions, instruction bloat |\n| 2 | Session history | Stale context injection from previous turns |\n| 3 | Long-term memory | Pollution across sessions, old topics in new conversations |\n| 4 | Distillation | Compressed artifacts re-entering as pseudo-facts |\n| 5 | Active recall | Redundant re-summary layers wasting context |\n| 6 | Tool selection | Wrong tool routing, model skips required tools |\n| 7 | Tool execution | Hallucinated execution — claims to call but doesn't |\n| 8 | Tool interpretation | Misread or ignored tool output |\n| 9 | Answer shaping | Format corruption in final response |\n| 10 | Platform rendering | Transport-layer mutation (UI, API, CLI mutates valid answers) |\n| 11 | Hidden repair loops | Silent fallback\u002Fretry agents running second LLM pass |\n| 12 | Persistence | Expired state or cached artifacts reused as live evidence |\n\n## Common Failure Patterns\n\n### 1. Wrapper Regression\n\nThe base model produces correct answers, but the wrapper layers make it worse.\n\n**Symptoms:**\n- Model works fine in playground or direct API call, breaks in your agent\n- Added a new prompt layer, existing behavior degraded\n- Agent sounds confident but is confidently wrong\n- \"It was working before the last update\"\n\n### 2. Memory Contamination\n\nOld topics leak into new conversations through history, memory retrieval, or distillation.\n\n**Symptoms:**\n- Agent brings up unrelated past topics\n- User corrections don't stick (old memory overwrites new)\n- Same-session artifacts re-enter as pseudo-facts\n- Memory grows without bound, degrading response quality over time\n\n### 3. Tool Discipline Failure\n\nTools are declared in the prompt but not enforced in code. The model skips them or hallucinates execution.\n\n**Symptoms:**\n- \"Must use tool X\" in prompt, but model answers without calling it\n- Tool results look correct but were never actually executed\n- Different tools fight over the same responsibility\n- Model uses tool when it shouldn't, or skips it when it must\n\n### 4. Rendering\u002FTransport Corruption\n\nThe agent's internal answer is correct, but the platform layer mutates it during delivery.\n\n**Symptoms:**\n- Logs show correct answer, user sees broken output\n- Markdown rendering, JSON parsing, or streaming fragments corrupt valid responses\n- Hidden fallback agent quietly replaces the answer before delivery\n- Output differs between terminal and UI\n\n### 5. Hidden Agent Layers\n\nSilent repair, retry, summarization, or recall agents run without explicit contracts.\n\n**Symptoms:**\n- Output changes between internal generation and user delivery\n- \"Auto-fix\" loops run a second LLM pass the user doesn't know about\n- Multiple agents modify the same output without coordination\n- Answers get \"smoothed\" or \"corrected\" by invisible layers\n\n## Audit Workflow\n\n### Phase 1: Scope\n\nDefine what you're auditing:\n\n- **Target system** — what agent application?\n- **Entrypoints** — how do users interact with it?\n- **Model stack** — which LLM(s) and providers?\n- **Symptoms** — what does the user report?\n- **Time window** — when did it start?\n- **Layers to audit** — which of the 12 layers apply?\n\n### Phase 2: Evidence Collection\n\nGather evidence from the codebase:\n\n- **Source code** — agent loop, tool router, memory admission, prompt assembly\n- **Logs** — historical session traces, tool call records\n- **Config** — prompt templates, tool schemas, provider settings\n- **Memory files** — SOPs, knowledge bases, session archives\n\nUse `rg` to search for anti-patterns:\n\n```bash\n# Tool requirements expressed only in prompt text (not code)\nrg \"must.*tool|必须.*工具|required.*call\" --type md\n\n# Tool execution without validation\nrg \"tool_call|toolCall|tool_use\" --type py --type ts\n\n# Hidden LLM calls outside main agent loop\nrg \"completion|chat\\.create|messages\\.create|llm\\.invoke\"\n\n# Memory admission without user-correction priority\nrg \"memory.*admit|long.*term.*update|persist.*memory\" --type py --type ts\n\n# Fallback loops that run additional LLM calls\nrg \"fallback|retry.*llm|repair.*prompt|re-?prompt\" --type py --type ts\n\n# Silent output mutation\nrg \"mutate|rewrite.*response|transform.*output|shap\" --type py --type ts\n```\n\n### Phase 3: Failure Mapping\n\nFor each finding, document:\n\n- **Symptom** — what the user sees\n- **Mechanism** — how the wrapper causes it\n- **Source layer** — which of the 12 layers\n- **Root cause** — the deepest cause\n- **Evidence** — file:line or log:row reference\n- **Confidence** — 0.0 to 1.0\n\n### Phase 4: Fix Strategy\n\nDefault fix order (code-first, not prompt-first):\n\n1. **Code-gate tool requirements** — enforce in code, not just prompt text\n2. **Remove or narrow hidden repair agents** — make fallback explicit with contracts\n3. **Reduce context duplication** — same info through prompt + history + memory + distillation\n4. **Tighten memory admission** — user corrections > agent assertions\n5. **Tighten distillation triggers** — don't compress what shouldn't be compressed\n6. **Reduce rendering mutation** — pass-through, don't transform\n7. **Convert to typed JSON envelopes** — structured internal flow, not freeform prose\n\n## Severity Model\n\n| Level | Meaning | Action |\n|-------|---------|--------|\n| `critical` | Agent can confidently produce wrong operational behavior | Fix before next release |\n| `high` | Agent frequently degrades correctness or stability | Fix this sprint |\n| `medium` | Correctness usually survives but output is fragile or wasteful | Plan for next cycle |\n| `low` | Mostly cosmetic or maintainability issues | Backlog |\n\n## Output Format\n\nPresent findings to the user in this order:\n\n1. **Severity-ranked findings** (most critical first)\n2. **Architecture diagnosis** (which layer corrupted what, and why)\n3. **Ordered fix plan** (code-first, not prompt-first)\n\nDo not lead with compliments or summaries. If the system is broken, say so directly.\n\n## Quick Diagnostic Questions\n\nWhen auditing an agent system, answer these:\n\n| # | Question | If Yes → |\n|---|----------|----------|\n| 1 | Can the model skip a required tool and still answer? | Tool not code-gated |\n| 2 | Does old conversation content appear in new turns? | Memory contamination |\n| 3 | Is the same info in system prompt AND memory AND history? | Context duplication |\n| 4 | Does the platform run a second LLM pass before delivery? | Hidden repair loop |\n| 5 | Does the output differ between internal generation and user delivery? | Rendering corruption |\n| 6 | Are \"must use tool X\" rules only in prompt text? | Tool discipline failure |\n| 7 | Can the agent's own monologue become persistent memory? | Memory poisoning |\n\n## Anti-Patterns to Avoid\n\n- Avoid blaming the model before falsifying wrapper-layer regressions.\n- Avoid blaming memory without showing the contamination path.\n- Do not let a clean current state erase a dirty historical incident.\n- Do not treat markdown prose as a trustworthy internal protocol.\n- Do not accept \"must use tool\" in prompt text when code never enforces it.\n- Keep findings direct, evidence-backed, and severity-ranked.\n\n## Report Schema\n\nAudits should produce structured reports following this shape:\n\n```json\n{\n  \"schema_version\": \"ecc.agent-architecture-audit.report.v1\",\n  \"executive_verdict\": {\n    \"overall_health\": \"high_risk\",\n    \"primary_failure_mode\": \"string\",\n    \"most_urgent_fix\": \"string\"\n  },\n  \"scope\": {\n    \"target_name\": \"string\",\n    \"model_stack\": [\"string\"],\n    \"layers_to_audit\": [\"string\"]\n  },\n  \"findings\": [\n    {\n      \"severity\": \"critical|high|medium|low\",\n      \"title\": \"string\",\n      \"mechanism\": \"string\",\n      \"source_layer\": \"string\",\n      \"root_cause\": \"string\",\n      \"evidence_refs\": [\"file:line\"],\n      \"confidence\": 0.0,\n      \"recommended_fix\": \"string\"\n    }\n  ],\n  \"ordered_fix_plan\": [\n    { \"order\": 1, \"goal\": \"string\", \"why_now\": \"string\", \"expected_effect\": \"string\" }\n  ]\n}\n```\n\n## Related Skills\n\n- `agent-introspection-debugging` — Debug agent runtime failures (loops, timeouts, state errors)\n- `agent-eval` — Benchmark agent performance head-to-head\n- `security-review` — Security audit for code and configuration\n- `autonomous-agent-harness` — Set up autonomous agent operations\n- `agent-harness-construction` — Build agent harnesses from scratch\n",{"name":5,"tools":49,"origin":50,"description":7},"Read, Write, Edit, Bash, Grep, Glob","oh-my-agent-check","main","a298c929b6cbd662e1fce54302ce520d5ceea1a5","skills\u002Fagent-architecture-audit","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill agent-architecture-audit",{"tool":63,"command":64},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill agent-architecture-audit",{"tool":66,"command":67},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill agent-architecture-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Fskills\u002Fagent-architecture-audit\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"bmad-skill-manifest.yaml","REFERENCE","参考文档",629,"https:\u002F\u002Fgithub.com\u002Fdanielmtt9\u002Fbloomcornerkiddies\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fbmad-agent-dev\u002Fbmad-skill-manifest.yaml",[78,99,124,150,164,180],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":44},"01M6DF7D7478R55P46REYH4QAC","clarify-requirements","Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fworkspace-hooks\u002Fskills\u002Fclarify-requirements\u002FSKILL.md",[],[85,86,87,88,89,90,91,92,93,33,94,95,96,97,98],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","context","repo","injection","execution","file",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"publishedAt":44},"01M6DF79CA4BHJS66J8EZDBPWJ","openmm-md","Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein \u002F protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fmcp\u002Fopenmm-md-mcp\u002Fskill\u002Fopenmm-md\u002FSKILL.md",[105],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[107,108,109,110,111,112,37,38,113,114,115,116,117,118,33,119,120,121,122,123],"openmm md","how","decision","pick","linux","analyze","open","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do","MCP",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":136,"publishedAt":44},"01M6DF76C1MG85VEWP8VZCBNMN","visual-review","Take screenshots of web pages and UI using Playwright for visual review and iteration","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fvisual-review\u002FSKILL.md",[130,133],{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[137,138,139,140,141,142,143,144,36,145,108,146,147,148,149],"review","visual","visual review","pages","web","false","iteration","take","slides","ui","screenshot","playwright","screenshots",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":44},"01M6DF73AQVCBZKEN0YXEX9FXP","status","Diagnostic status report — shows metaswarm installation state, project setup, and potential issues","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstatus\u002FSKILL.md",[],[152,157,158,159,160,161,162,163],"setup","report","project","installation","project setup","issues","state",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":171,"publishedAt":44},"01M6DF6X6C2XB0P6GX76P7TTYV","start","Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstart\u002FSKILL.md",[170],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[166,172,90,173,174,175,33,176,177,178,179],"start issue","issue","ready","work on issue","user","work","work on","development",{"skillNo":181,"name":157,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":44},"01M6DF6QMJ9AJKFKHHKRT005PQ","Interactive project setup — detects your project, configures metaswarm, writes project-local files","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fsetup\u002FSKILL.md",[],[157,159,121,186,161,187],"files","interactive"]