[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7783HTDF24QAZZ4QE3CY2CH":3,"skill-same:01M7783HTDF24QAZZ4QE3CY2CH":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":20,"frontMatter":21,"refName":22,"commitSha":23,"skillDirectory":24,"forksCount":25,"repositoryHtmlUrl":26,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7783HTDF24QAZZ4QE3CY2CH","coding-team-setup",null,"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\u002Fclawhub\u002Fc\u002Fcoding-team-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"# Coding Team Setup v2.1 — Flexible Multi-Agent Development Team\n\n## English\n\n> Flexible setup for 2–10 agent collaborative teams on OpenClaw.\n\n### What's New in v2.0\n\n| Feature | v1.0 | v2.0 |\n|---------|------|------|\n| Team size | Fixed 7 | **2–10 agents** |\n| Team naming | Single team | **Multiple named teams** |\n| Roles | 7 preset only | **10 preset + custom roles** |\n| Workflow | Fixed 9-step | **4 templates + fully custom** |\n| Model assignment | Hardcoded | **Auto-detect + manual override** |\n\n### When to Use\n\n- Set up a multi-role collaborative development team (2–10 agents)\n- Need multiple teams to work in parallel with independent configurations\n- Need custom collaboration workflows (not limited to standard 9-step)\n- Need flexible role combinations and model assignments\n\n### Quick Start\n\n#### Interactive Setup Wizard (Recommended)\n\n```bash\n# Default team\nnode \u003Cskill-dir>\u002Fwizard\u002Fsetup.js\n\n# Named team (supports multiple teams coexisting)\nnode \u003Cskill-dir>\u002Fwizard\u002Fsetup.js --team alpha\nnode \u003Cskill-dir>\u002Fwizard\u002Fsetup.js --team beta\n```\n\nThe wizard guides you through:\n1. **Team naming** — Give your team a name (supports multi-team setup)\n2. **Select roles** — Choose 2–10 from 10 preset roles or add custom ones\n3. **Assign models** — Auto-detect registered models or specify manually\n4. **Select collaboration workflow** — 4 preset templates or fully custom\n5. **Write config** — Auto-update openclaw.json + create workspace\n\n### Available Role Templates (10)\n\n| Role | ID | Emoji | Category | Default Model Type |\n|------|----|-------|----------|--------------------|\n| Product Manager | `pm` | 📋 | Management | Balanced |\n| Architect | `architect` | 🏗️ | Engineering | Strongest |\n| Frontend | `frontend` | 🎨 | Engineering | Code |\n| Backend | `backend` | ⚙️ | Engineering | Code |\n| QA | `qa` | 🔍 | Quality | Balanced |\n| DevOps | `devops` | 🚀 | Operations | Strongest |\n| Code Artisan | `code-artisan` | 🛠️ | Quality | Code |\n| Data Engineer | `data-engineer` | 📊 | Engineering | Code |\n| Security | `security` | 🔒 | Quality | Strongest |\n| Tech Writer | `tech-writer` | 📝 | Management | Balanced |\n\n**Custom roles:** The wizard supports adding fully custom roles (ID, name, emoji, responsibilities, model type).\n\n### Workflow Templates (4)\n\n#### 1. Standard 9-Step Collaboration (`standard-9step`)\n```\nPM → Architect Review → Frontend + Backend (parallel) → Code Review → QA → Approval → Deployment\n```\nBest for: Complete project development with strict process control\n\n#### 2. Quick 3-Step Flow (`quick-3step`)\n```\nDirect Development → Code Review → Deployment\n```\nBest for: Small features, hotfixes, rapid iteration\n\n#### 3. Fullstack Solo (`fullstack-solo`)\n```\nRequirements Design → Fullstack Development → Testing & Deployment\n```\nBest for: 2–3 person lean team\n\n#### 4. Fully Custom (`custom`)\n- Free definition of step count\n- Specify roles per step (supports parallel roles)\n- Set feedback loops\n- Mark optional steps\n\n### Multi-Team Support\n\nA single OpenClaw instance can run multiple teams:\n\n```bash\n# Team alpha: frontend team\nnode setup.js --team alpha\n# Select: frontend, qa, devops\n\n# Team beta: backend team\nnode setup.js --team beta\n# Select: backend, architect, qa, devops\n\n# Team gamma: fullstack\nnode setup.js --team gamma\n```\n\nEach team's agent ID includes the team prefix: `alpha-frontend`, `beta-backend`, etc.\n\nTeam configs are stored at: `teamtask\u002Fteams\u002F\u003Cteam-name>.json`\n\n### Architecture\n\n```\n~\u002F.openclaw\u002F\n├── openclaw.json              # Agent config for all teams\n├── workspace\u002F\n│   └── teamtask\u002F\n│       ├── teams\u002F             # Team manifests\n│       │   ├── default.json\n│       │   ├── alpha.json\n│       │   └── beta.json\n│       └── tasks\u002F             # Project task directory\n└── agents\u002F                    # Subagent directory\n    ├── pm\u002F                    # default team\n    ├── alpha-frontend\u002F        # alpha team\n    ├── beta-backend\u002F          # beta team\n    └── ...\n```\n\n### Model Assignment\n\nThe wizard auto-detects registered models in `openclaw.json` and matches by type:\n\n| Model Type | Best For | Auto-detect Pattern |\n|-----------|----------|---------------------|\n| Strongest Reasoning | Architect, DevOps, Security | `\u002Fopus\u002Fi` |\n| Code Specialized | Frontend, Backend, Code Artisan | `\u002Fcodex\u002Fi` |\n| Balanced | PM, QA, Tech Writer | `\u002Fsonnet\u002Fi` |\n| Fast | Simple tasks | `\u002Fhaiku\u002Fi` |\n| Long Context | Cross-file analysis | `\u002Fgemini.*pro\u002Fi` |\n\nFallback chains are auto-generated based on model type relationships.\n\n### Collaboration Workflow\n\n#### Activation Protocol\n\n```\n@codingteam wake up              — Activate default team\n@codingteam \u003Cteam-name> wake up  — Activate specified team\n@codingteam \u003Crole>               — Activate specified role\n@codingteam 收工                 — All team members sleep\n```\n\n#### Spawning Method\n\n```javascript\n\u002F\u002F Spawn by agent ID\nsessions_spawn({\n  task: \"Implement user auth API\",\n  agentId: \"backend\"        \u002F\u002F default team\n  \u002F\u002F agentId: \"alpha-backend\"  \u002F\u002F named team\n})\n```\n\n### File Structure\n\n```\nskills\u002Fcoding-team-setup\u002F\n├── SKILL.md               # This file\n├── README.md              # Public description\n├── clawhub.yaml           # ClawHub metadata\n├── config\u002F\n│   └── roles.json         # Role templates + workflow templates + model types\n├── templates\u002F\n│   └── SOUL-template.md   # SOUL.md template\n└── wizard\u002F\n    └── setup.js           # Interactive setup wizard (v2.0)\n```\n\n### Troubleshooting\n\n| Problem | Cause | Fix |\n|---------|-------|-----|\n| `agents_list` only shows main | `allowAgents` missing agent ID | Re-run wizard or add manually |\n| Spawn timeout | Rate Limit \u002F model unavailable | Check fallback chain |\n| Multi-team ID conflict | --team parameter not used | Use `--team \u003Cname>` to distinguish |\n| Workspace files missing | Directory deleted manually | Re-run wizard |\n\n### Lessons Learned\n\n1. **`allowAgents` must be under main agent's `subagents`** — not under `defaults.subagents`\n2. **Model IDs must be complete** — include provider prefix\n3. **Gateway must restart** — after modifying openclaw.json, run `openclaw gateway restart`\n4. **Concurrency control** — spawning too many at once triggers Rate Limit; spawn in batches\n5. **Team prefix** — multi-team agent IDs auto-include prefix; use full ID when spawning\n\n### Standard Post-Setup Workflow (UPDATED in v2.2)\n\nAfter creating any sub-agent team, execute this as **mandatory standard flow**:\n\n1. **Core skill baseline assignment**\n   - Assign 2–4 core skills per role directly in `openclaw.json`\n   - Keep advanced\u002Fdomain skills as on-demand skills\n\n2. **Skill learning telemetry**\n   - Enable usage logging per agent\u002Fskill\n   - Log format: `agent_id + skill_name + timestamp + context`\n\n3. **Weekly optimization task (OpenClaw Cron)**\n   - Create a weekly `openclaw cron` job in isolated session\n   - Analyze last 7 days usage and update `openclaw.json` skill mapping\n   - Always backup before writing config\n\n4. **All-team scope**\n   - Mechanism must apply to **all teams** (coding\u002Fwealth\u002Fother future teams)\n   - No team-specific hardcoding in the optimizer\n\n5. **Review outputs**\n   - Save weekly optimization summary to `memory\u002FYYYY-MM-DD.md`\n   - Keep optimization history under `.lib\u002Fskill_analytics\u002F`\n\n6. **Mandatory Subagent Timeout Governance (NEW)**\n   - Do not call `sessions_spawn` directly for production fan-out checks.\n   - Use timeout governance wrapper with graded timeout + retry + circuit breaker.\n   - Recommended baseline:\n     - Simple tasks: 60s, retry 2\n     - Normal tasks: 120s, retry 3\n     - Complex tasks: 180s, retry 3\n   - Failure classification must be explicit in reports:\n     - `SPAWN_REJECTED` \u002F `TIMEOUT` \u002F `NO_CHANNEL_503` \u002F `RATE_LIMIT` \u002F `UNKNOWN`\n   - Health-check outputs must include three blocks:\n     1) spawn accepted\u002Frejected\n     2) fallback trace (primary → fallback1 → fallback2)\n     3) final failure type + request id (if any)\n\n7. **Allowlist Guardrail (NEW)**\n   - `allowAgents` must be merged into `main.subagents.allowAgents` (append + dedupe), never overwritten blindly.\n   - After write, verify with `agents_list` that all new agents are visible before any spawn.\n\n---\n\n## 中文\n\n> 灵活搭建 2–10 位子代理开发团队，支持多团队命名、自定义协作流程\n\n### v2.0 新增特性\n\n| 特性 | v1.0 | v2.0 |\n|------|------|------|\n| 团队规模 | 固定 7 人 | **2–10 人** |\n| 团队命名 | 单一团队 | **多个命名团队** |\n| 角色 | 7 个预设 | **10 个预设 + 自定义** |\n| 协作流程 | 固定 9 步 | **4 个模板 + 完全自定义** |\n| 模型分配 | 硬编码 | **自动检测 + 手动覆盖** |\n\n### 适用场景\n\n- 搭建一个多角色协作开发团队（2–10人）\n- 需要多个团队并行工作，各自独立配置\n- 需要自定义协作流程（不限于标准9步）\n- 需要灵活的角色组合和模型分配\n\n### 快速开始\n\n#### 交互式配置向导（推荐）\n\n```bash\n# 默认团队\nnode \u003Cskill-dir>\u002Fwizard\u002Fsetup.js\n\n# 命名团队（支持多个团队并存）\nnode \u003Cskill-dir>\u002Fwizard\u002Fsetup.js --team alpha\nnode \u003Cskill-dir>\u002Fwizard\u002Fsetup.js --team beta\n```\n\n向导会引导你完成：\n1. **团队命名** — 给团队一个名字（支持多团队）\n2. **选择角色** — 从10个预设角色中选2–10个，或添加自定义角色\n3. **分配模型** — 自动检测已注册模型，或手动指定\n4. **选择协作流程** — 4个预设模板或完全自定义\n5. **写入配置** — 自动更新 openclaw.json + 创建 workspace\n\n### 可用的角色模板（10个）\n\n| 角色 | ID | Emoji | 类别 | 默认模型类型 |\n|------|-------|-------|------|------------|\n| 产品经理 | `pm` | 📋 | 管理 | 均衡型 |\n| 架构师 | `architect` | 🏗️ | 工程 | 最强推理 |\n| 前端 | `frontend` | 🎨 | 工程 | 代码专长 |\n| 后端 | `backend` | ⚙️ | 工程 | 代码专长 |\n| QA | `qa` | 🔍 | 质量 | 均衡型 |\n| DevOps | `devops` | 🚀 | 运维 | 最强推理 |\n| 代码工匠 | `code-artisan` | 🛠️ | 质量 | 代码专长 |\n| 数据工程师 | `data-engineer` | 📊 | 工程 | 代码专长 |\n| 安全 | `security` | 🔒 | 质量 | 最强推理 |\n| 技术文档 | `tech-writer` | 📝 | 管理 | 均衡型 |\n\n**自定义角色：** 向导支持添加完全自定义的角色（ID、名称、emoji、职责、模型类型）。\n\n### 协作流程模板（4个）\n\n#### 1. 标准9步协作流程 (`standard-9step`)\n```\nPM → 架构师评审 → 前端 + 后端（并行） → 代码审查 → QA → 确认 → 部署\n```\n适合：完整项目开发，需要严格流程控制\n\n#### 2. 快速3步流程 (`quick-3step`)\n```\n直接开发 → 代码审查 → 部署\n```\n适合：小型功能、hotfix、快速迭代\n\n#### 3. 全栈独角兽 (`fullstack-solo`)\n```\n需求设计 → 全栈开发 → 测试部署\n```\n适合：2–3人精简团队\n\n#### 4. 完全自定义 (`custom`)\n- 自由定义步骤数量\n- 每步指定角色（支持多角色并行）\n- 可设置 feedback loop\n- 可标记可选步骤\n\n### 多团队支持\n\n一个 OpenClaw 实例可以运行多个团队：\n\n```bash\n# 团队 alpha：前端团队\nnode setup.js --team alpha\n# 选择: frontend, qa, devops\n\n# 团队 beta：后端团队\nnode setup.js --team beta\n# 选择: backend, architect, qa, devops\n\n# 团队 gamma：全栈\nnode setup.js --team gamma\n```\n\n每个团队的 agent ID 带团队前缀：`alpha-frontend`, `beta-backend` 等。\n\n团队配置存储在：`teamtask\u002Fteams\u002F\u003Cteam-name>.json`\n\n### 架构\n\n```\n~\u002F.openclaw\u002F\n├── openclaw.json              # 所有团队的 agent 配置\n├── workspace\u002F\n│   └── teamtask\u002F\n│       ├── teams\u002F             # 团队 manifest\n│       │   ├── default.json\n│       │   ├── alpha.json\n│       │   └── beta.json\n│       └── tasks\u002F             # 项目任务目录\n└── agents\u002F                    # 子代理目录\n    ├── pm\u002F                    # default team\n    ├── alpha-frontend\u002F        # alpha team\n    ├── beta-backend\u002F          # beta team\n    └── ...\n```\n\n### 模型分配\n\n向导自动检测 `openclaw.json` 中已注册的模型，按类型匹配：\n\n| 模型类型 | 适用角色 | 自动检测规则 |\n|---------|---------|-------------|\n| 最强推理 | 架构师、DevOps、安全 | `\u002Fopus\u002Fi` |\n| 代码专长 | 前端、后端、代码工匠 | `\u002Fcodex\u002Fi` |\n| 均衡型 | PM、QA、技术文档 | `\u002Fsonnet\u002Fi` |\n| 快速 | 简单任务 | `\u002Fhaiku\u002Fi` |\n| 长上下文 | 跨文件分析 | `\u002Fgemini.*pro\u002Fi` |\n\nFallback 链根据模型类型关系自动生成。\n\n### 协作工作流\n\n#### 唤醒协议\n\n```\n@codingteam wake up              — 激活默认团队全体\n@codingteam \u003Cteam-name> wake up  — 激活指定团队\n@codingteam \u003Crole>               — 激活指定角色\n@codingteam 收工                 — 全员休眠\n```\n\n#### 调度方式\n\n```javascript\n\u002F\u002F 按 agent ID 生成\nsessions_spawn({\n  task: \"实现用户认证 API\",\n  agentId: \"backend\"        \u002F\u002F default team\n  \u002F\u002F agentId: \"alpha-backend\"  \u002F\u002F named team\n})\n```\n\n### 文件结构\n\n```\nskills\u002Fcoding-team-setup\u002F\n├── SKILL.md               # 本文件\n├── README.md              # 公开描述\n├── clawhub.yaml           # ClawHub 元数据\n├── config\u002F\n│   └── roles.json         # 角色模板 + 流程模板 + 模型类型\n├── templates\u002F\n│   └── SOUL-template.md   # SOUL.md 模板\n└── wizard\u002F\n    └── setup.js           # 交互式配置向导 (v2.0)\n```\n\n### 故障排查\n\n| 问题 | 原因 | 解决方案 |\n|------|------|---------|\n| `agents_list` 只显示 main | `allowAgents` 缺少 agent ID | 重新运行向导或手动添加 |\n| Spawn 超时 | Rate Limit \u002F 模型不可用 | 检查 fallback 链 |\n| 多团队 ID 冲突 | 未使用 --team 参数 | 用 `--team \u003Cname>` 区分 |\n| Workspace 文件缺失 | 手动删除了目录 | 重新运行向导 |\n\n### 经验教训\n\n1. **`allowAgents` 必须在 main agent 的 `subagents` 下** — 不是 `defaults.subagents`\n2. **模型 ID 必须完整** — 包含 provider 前缀\n3. **Gateway 必须重启** — 修改 openclaw.json 后 `openclaw gateway restart`\n4. **并发控制** — 同时 spawn 太多会触发 Rate Limit，建议分批\n5. **团队前缀** — 多团队时 agent ID 自动带前缀，spawn 时要用完整 ID\n\n### 标准后置流程（v2.2 更新）\n\n所有子代理团队创建完成后，必须执行以下标准流程：\n\n1. **核心技能基线配置**\n   - 每个角色在 `openclaw.json` 固定配置 2–4 个核心技能\n   - 进阶\u002F领域技能保留为按需调用\n\n2. **技能学习与使用追踪**\n   - 记录每个子代理的技能调用事件\n   - 记录字段：`agent_id + skill_name + timestamp + context`\n\n3. **每周技能优化任务（OpenClaw Cron）**\n   - 通过 `openclaw cron` 创建每周任务（isolated session）\n   - 分析近7天使用频率，自动优化 `openclaw.json` 的技能映射\n   - 写入前必须自动备份配置\n\n4. **全团队统一适用**\n   - 机制覆盖所有团队（coding\u002Fwealth\u002F未来团队）\n   - 禁止只对单一团队硬编码\n\n5. **输出与归档**\n   - 每周优化结果写入 `memory\u002FYYYY-MM-DD.md`\n   - 优化历史保存在 `.lib\u002Fskill_analytics\u002F`\n\n6. **子代理超时治理（新增，强制）**\n   - 生产场景禁止裸调 `sessions_spawn` 做并发健康检查。\n   - 必须走超时治理封装（分级超时 + 重试 + 熔断）。\n   - 推荐基线：\n     - 简单任务：60s，重试2次\n     - 普通任务：120s，重试3次\n     - 复杂任务：180s，重试3次\n   - 报告必须输出统一失败分型：\n     - `SPAWN_REJECTED` \u002F `TIMEOUT` \u002F `NO_CHANNEL_503` \u002F `RATE_LIMIT` \u002F `UNKNOWN`\n   - 健康检查结果必须包含三段：\n     1) spawn 是否 accepted\n     2) fallback 轨迹（primary → fallback1 → fallback2）\n     3) 最终失败类型 + request id（若有）\n\n7. **Allowlist 防护（新增）**\n   - `allowAgents` 只能合并写入 `main.subagents.allowAgents`（追加+去重），禁止覆盖清空。\n   - 写入后先用 `agents_list` 验证新增代理可见，再进行 spawn。\n",{},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fc\u002Fcoding-team-setup",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":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill coding-team-setup",{"tool":37,"command":38},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill coding-team-setup",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill coding-team-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fc\u002Fcoding-team-setup\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"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":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"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",[],[]]