[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M781BYEZD92R3479DHRHTNPD":3,"skill-same:01M781BYEZD92R3479DHRHTNPD":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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M781BYEZD92R3479DHRHTNPD","agent-architecture-audit",null,"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 fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_affaan-m_ecc_agent-architecture-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agent-architecture-audit\ndescription: 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 fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature.\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":24,"origin":25,"description":7},"Read, Write, Edit, Bash, Grep, Glob","oh-my-agent-check","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fskills_sh\u002Fs\u002Fskills-sh_affaan-m_ecc_agent-architecture-audit",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill agent-architecture-audit",{"tool":41,"command":42},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill agent-architecture-audit",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill agent-architecture-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_affaan-m_ecc_agent-architecture-audit\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"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":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"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":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]