[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KB7QVK4Q69AD2W0K10YQNF":3,"skill-same:01M6KB7QVK4Q69AD2W0K10YQNF":140},{"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":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6KB7QVK4Q69AD2W0K10YQNF","agenthub",null,"Multi-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"git worktree isolation","code","metric","worktree isolation","benefits","judge","isolation","competition","exploration","subagents","repo","branch","work","parallel","multi-agent","git worktree","llm judge","worktree","git","2026-11-10 10:12:30",false,"---\nname: \"agenthub\"\ndescription: \"Multi-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.\"\nlicense: MIT\nmetadata:\n  version: 2.1.2\n  author: Md Faiz Alam\n  category: engineering\n  updated: 2026-03-17\n---\n\n# AgentHub — Multi-Agent Collaboration\n\nSpawn N parallel AI agents that compete on the same task. Each agent works in an isolated git worktree. The coordinator evaluates results and merges the winner.\n\n## Slash Commands\n\n| Command | Description |\n|---------|-------------|\n| `\u002Fhub:init` | Create a new collaboration session — task, agent count, eval criteria |\n| `\u002Fhub:spawn` | Launch N parallel subagents in isolated worktrees |\n| `\u002Fhub:status` | Show DAG state, agent progress, branch status |\n| `\u002Fhub:eval` | Rank agent results by metric or LLM judge |\n| `\u002Fhub:merge` | Merge winning branch, archive losers |\n| `\u002Fhub:board` | Read\u002Fwrite the agent message board |\n| `\u002Fhub:run` | One-shot lifecycle: init → baseline → spawn → eval → merge |\n\n## Agent Templates\n\nWhen spawning with `--template`, agents follow a predefined iteration pattern:\n\n| Template | Pattern | Use Case |\n|----------|---------|----------|\n| `optimizer` | Edit → eval → keep\u002Fdiscard → repeat x10 | Performance, latency, size |\n| `refactorer` | Restructure → test → iterate until green | Code quality, tech debt |\n| `test-writer` | Write tests → measure coverage → repeat | Test coverage gaps |\n| `bug-fixer` | Reproduce → diagnose → fix → verify | Bug fix approaches |\n\nTemplates are defined in `references\u002Fagent-templates.md`.\n\n## When This Skill Activates\n\nTrigger phrases:\n- \"try multiple approaches\"\n- \"have agents compete\"\n- \"parallel optimization\"\n- \"spawn N agents\"\n- \"compare different solutions\"\n- \"fan-out\" or \"tournament\"\n- \"generate content variations\"\n- \"compare different drafts\"\n- \"A\u002FB test copy\"\n- \"explore multiple strategies\"\n\n## Coordinator Protocol\n\nThe main Claude Code session is the coordinator. It follows this lifecycle:\n\n```\nINIT → DISPATCH → MONITOR → EVALUATE → MERGE\n```\n\n### 1. Init\n\nRun `\u002Fhub:init` to create a session. This generates:\n- `.agenthub\u002Fsessions\u002F{session-id}\u002Fconfig.yaml` — task config\n- `.agenthub\u002Fsessions\u002F{session-id}\u002Fstate.json` — state machine\n- `.agenthub\u002Fboard\u002F` — message board channels\n\n### 2. Dispatch\n\nRun `\u002Fhub:spawn` to launch agents. For each agent 1..N:\n- Post task assignment to `.agenthub\u002Fboard\u002Fdispatch\u002F`\n- Spawn via Agent tool with `isolation: \"worktree\"`\n- All agents launched in a single message (parallel)\n\n### 3. Monitor\n\nRun `\u002Fhub:status` to check progress:\n- `dag_analyzer.py --status --session {id}` shows branch state\n- Board `progress\u002F` channel has agent updates\n\n### 4. Evaluate\n\nRun `\u002Fhub:eval` to rank results:\n- **Metric mode**: run eval command in each worktree, parse numeric result\n- **Judge mode**: read diffs, coordinator ranks by quality\n- **Hybrid**: metric first, LLM-judge for ties\n\n### 5. Merge\n\nRun `\u002Fhub:merge` to finalize:\n- `git merge --no-ff` winner into base branch\n- Tag losers: `git tag hub\u002Farchive\u002F{session}\u002Fagent-{i}`\n- Clean up worktrees\n- Post merge summary to board\n\n## Agent Protocol\n\nEach subagent receives this prompt pattern:\n\n```\nYou are agent-{i} in hub session {session-id}.\nYour task: {task description}\n\nInstructions:\n1. Read your assignment at .agenthub\u002Fboard\u002Fdispatch\u002F{seq}-agent-{i}.md\n2. Work in your worktree — make changes, run tests, iterate\n3. Commit all changes with descriptive messages\n4. Write your result summary to .agenthub\u002Fboard\u002Fresults\u002Fagent-{i}-result.md\n5. Exit when done\n```\n\nAgents do NOT see each other's work. They do NOT communicate with each other. They only write to the board for the coordinator to read.\n\n## DAG Model\n\n### Branch Naming\n\n```\nhub\u002F{session-id}\u002Fagent-{N}\u002Fattempt-{M}\n```\n\n- Session ID: timestamp-based (`YYYYMMDD-HHMMSS`)\n- Agent N: sequential (1 to agent-count)\n- Attempt M: increments on retry (usually 1)\n\n### Frontier Detection\n\nFrontier = branch tips with no child branches. Equivalent to AgentHub's \"leaves\" query.\n\n```bash\npython scripts\u002Fdag_analyzer.py --frontier --session {id}\n```\n\n### Immutability\n\nThe DAG is append-only:\n- Never rebase or force-push agent branches\n- Never delete commits (only branch refs after archival)\n- Every approach preserved via git tags\n\n## Message Board\n\nLocation: `.agenthub\u002Fboard\u002F`\n\n### Channels\n\n| Channel | Writer | Reader | Purpose |\n|---------|--------|--------|---------|\n| `dispatch\u002F` | Coordinator | Agents | Task assignments |\n| `progress\u002F` | Agents | Coordinator | Status updates |\n| `results\u002F` | Agents + Coordinator | All | Final results + merge summary |\n\n### Post Format\n\n```markdown\n---\nauthor: agent-1\ntimestamp: 2026-03-17T14:30:22Z\nchannel: results\nparent: null\n---\n\n## Result Summary\n\n- **Approach**: Replaced O(n²) sort with hash map\n- **Files changed**: 3\n- **Metric**: 142ms (baseline: 180ms, delta: -38ms)\n- **Confidence**: High — all tests pass\n```\n\n### Board Rules\n\n- Append-only: never edit or delete posts\n- Unique filenames: `{seq:03d}-{author}-{timestamp}.md`\n- YAML frontmatter required on all posts\n\n## Evaluation Modes\n\n### Metric-Based\n\nBest for: benchmarks, test pass rates, file sizes, response times.\n\n```bash\npython scripts\u002Fresult_ranker.py --session {id} \\\n  --eval-cmd \"pytest bench.py --json\" \\\n  --metric p50_ms --direction lower\n```\n\nThe ranker runs the eval command in each agent's worktree directory and parses the metric from stdout.\n\n### LLM Judge\n\nBest for: code quality, readability, architecture decisions.\n\nThe coordinator reads each agent's diff (`git diff base...agent-branch`) and ranks by:\n1. Correctness (does it solve the task?)\n2. Simplicity (fewer lines changed preferred)\n3. Quality (clean execution, good structure)\n\n### Hybrid\n\nRun metric first. If top agents are within 10% of each other, use LLM judge to break ties.\n\n## Session Lifecycle\n\n```\ninit → running → evaluating → merged\n                            → archived (if no winner)\n```\n\nState transitions managed by `session_manager.py`:\n\n| From | To | Trigger |\n|------|----|---------|\n| `init` | `running` | `\u002Fhub:spawn` completes |\n| `running` | `evaluating` | All agents return |\n| `evaluating` | `merged` | `\u002Fhub:merge` completes |\n| `evaluating` | `archived` | No winner \u002F all failed |\n\n## Proactive Triggers\n\nThe coordinator should act when:\n\n| Signal | Action |\n|--------|--------|\n| All agents crashed | Post failure summary, suggest retry with different constraints |\n| No improvement over baseline | Archive session, suggest different approaches |\n| Orphan worktrees detected | Run `session_manager.py --cleanup {id}` |\n| Session stuck in `running` | Check board for progress, consider timeout |\n\n## Installation\n\n```bash\n# Copy to your Claude Code skills directory\ncp -r engineering\u002Fagenthub ~\u002F.claude\u002Fskills\u002Fagenthub\n\n# Or install via ClawHub\nclawhub install agenthub\n```\n\n## Scripts\n\n| Script | Purpose |\n|--------|---------|\n| `hub_init.py` | Initialize `.agenthub\u002F` structure and session |\n| `dag_analyzer.py` | Frontier detection, DAG graph, branch status |\n| `board_manager.py` | Message board CRUD (channels, posts, threads) |\n| `result_ranker.py` | Rank agents by metric or diff quality |\n| `session_manager.py` | Session state machine and cleanup |\n\n## Related Skills\n\n- **autoresearch-agent** — Single-agent optimization loop (use AgentHub when you want N agents competing)\n- **self-improving-agent** — Self-modifying agent (use AgentHub when you want external competition)\n- **git-worktree-manager** — Git worktree utilities (AgentHub uses worktrees internally)\n","# AgentHub — Multi-Agent Collaboration\n\nSpawn N parallel AI agents that compete on the same task. Each agent works in an isolated git worktree. The coordinator evaluates results and merges the winner.\n\n## Slash Commands\n\n| Command | Description |\n|---------|-------------|\n| `\u002Fhub:init` | Create a new collaboration session — task, agent count, eval criteria |\n| `\u002Fhub:spawn` | Launch N parallel subagents in isolated worktrees |\n| `\u002Fhub:status` | Show DAG state, agent progress, branch status |\n| `\u002Fhub:eval` | Rank agent results by metric or LLM judge |\n| `\u002Fhub:merge` | Merge winning branch, archive losers |\n| `\u002Fhub:board` | Read\u002Fwrite the agent message board |\n| `\u002Fhub:run` | One-shot lifecycle: init → baseline → spawn → eval → merge |\n\n## Agent Templates\n\nWhen spawning with `--template`, agents follow a predefined iteration pattern:\n\n| Template | Pattern | Use Case |\n|----------|---------|----------|\n| `optimizer` | Edit → eval → keep\u002Fdiscard → repeat x10 | Performance, latency, size |\n| `refactorer` | Restructure → test → iterate until green | Code quality, tech debt |\n| `test-writer` | Write tests → measure coverage → repeat | Test coverage gaps |\n| `bug-fixer` | Reproduce → diagnose → fix → verify | Bug fix approaches |\n\nTemplates are defined in `references\u002Fagent-templates.md`.\n\n## When This Skill Activates\n\nTrigger phrases:\n- \"try multiple approaches\"\n- \"have agents compete\"\n- \"parallel optimization\"\n- \"spawn N agents\"\n- \"compare different solutions\"\n- \"fan-out\" or \"tournament\"\n- \"generate content variations\"\n- \"compare different drafts\"\n- \"A\u002FB test copy\"\n- \"explore multiple strategies\"\n\n## Coordinator Protocol\n\nThe main Claude Code session is the coordinator. It follows this lifecycle:\n\n```\nINIT → DISPATCH → MONITOR → EVALUATE → MERGE\n```\n\n### 1. Init\n\nRun `\u002Fhub:init` to create a session. This generates:\n- `.agenthub\u002Fsessions\u002F{session-id}\u002Fconfig.yaml` — task config\n- `.agenthub\u002Fsessions\u002F{session-id}\u002Fstate.json` — state machine\n- `.agenthub\u002Fboard\u002F` — message board channels\n\n### 2. Dispatch\n\nRun `\u002Fhub:spawn` to launch agents. For each agent 1..N:\n- Post task assignment to `.agenthub\u002Fboard\u002Fdispatch\u002F`\n- Spawn via Agent tool with `isolation: \"worktree\"`\n- All agents launched in a single message (parallel)\n\n### 3. Monitor\n\nRun `\u002Fhub:status` to check progress:\n- `dag_analyzer.py --status --session {id}` shows branch state\n- Board `progress\u002F` channel has agent updates\n\n### 4. Evaluate\n\nRun `\u002Fhub:eval` to rank results:\n- **Metric mode**: run eval command in each worktree, parse numeric result\n- **Judge mode**: read diffs, coordinator ranks by quality\n- **Hybrid**: metric first, LLM-judge for ties\n\n### 5. Merge\n\nRun `\u002Fhub:merge` to finalize:\n- `git merge --no-ff` winner into base branch\n- Tag losers: `git tag hub\u002Farchive\u002F{session}\u002Fagent-{i}`\n- Clean up worktrees\n- Post merge summary to board\n\n## Agent Protocol\n\nEach subagent receives this prompt pattern:\n\n```\nYou are agent-{i} in hub session {session-id}.\nYour task: {task description}\n\nInstructions:\n1. Read your assignment at .agenthub\u002Fboard\u002Fdispatch\u002F{seq}-agent-{i}.md\n2. Work in your worktree — make changes, run tests, iterate\n3. Commit all changes with descriptive messages\n4. Write your result summary to .agenthub\u002Fboard\u002Fresults\u002Fagent-{i}-result.md\n5. Exit when done\n```\n\nAgents do NOT see each other's work. They do NOT communicate with each other. They only write to the board for the coordinator to read.\n\n## DAG Model\n\n### Branch Naming\n\n```\nhub\u002F{session-id}\u002Fagent-{N}\u002Fattempt-{M}\n```\n\n- Session ID: timestamp-based (`YYYYMMDD-HHMMSS`)\n- Agent N: sequential (1 to agent-count)\n- Attempt M: increments on retry (usually 1)\n\n### Frontier Detection\n\nFrontier = branch tips with no child branches. Equivalent to AgentHub's \"leaves\" query.\n\n```bash\npython scripts\u002Fdag_analyzer.py --frontier --session {id}\n```\n\n### Immutability\n\nThe DAG is append-only:\n- Never rebase or force-push agent branches\n- Never delete commits (only branch refs after archival)\n- Every approach preserved via git tags\n\n## Message Board\n\nLocation: `.agenthub\u002Fboard\u002F`\n\n### Channels\n\n| Channel | Writer | Reader | Purpose |\n|---------|--------|--------|---------|\n| `dispatch\u002F` | Coordinator | Agents | Task assignments |\n| `progress\u002F` | Agents | Coordinator | Status updates |\n| `results\u002F` | Agents + Coordinator | All | Final results + merge summary |\n\n### Post Format\n\n```markdown\n---\nauthor: agent-1\ntimestamp: 2026-03-17T14:30:22Z\nchannel: results\nparent: null\n---\n\n## Result Summary\n\n- **Approach**: Replaced O(n²) sort with hash map\n- **Files changed**: 3\n- **Metric**: 142ms (baseline: 180ms, delta: -38ms)\n- **Confidence**: High — all tests pass\n```\n\n### Board Rules\n\n- Append-only: never edit or delete posts\n- Unique filenames: `{seq:03d}-{author}-{timestamp}.md`\n- YAML frontmatter required on all posts\n\n## Evaluation Modes\n\n### Metric-Based\n\nBest for: benchmarks, test pass rates, file sizes, response times.\n\n```bash\npython scripts\u002Fresult_ranker.py --session {id} \\\n  --eval-cmd \"pytest bench.py --json\" \\\n  --metric p50_ms --direction lower\n```\n\nThe ranker runs the eval command in each agent's worktree directory and parses the metric from stdout.\n\n### LLM Judge\n\nBest for: code quality, readability, architecture decisions.\n\nThe coordinator reads each agent's diff (`git diff base...agent-branch`) and ranks by:\n1. Correctness (does it solve the task?)\n2. Simplicity (fewer lines changed preferred)\n3. Quality (clean execution, good structure)\n\n### Hybrid\n\nRun metric first. If top agents are within 10% of each other, use LLM judge to break ties.\n\n## Session Lifecycle\n\n```\ninit → running → evaluating → merged\n                            → archived (if no winner)\n```\n\nState transitions managed by `session_manager.py`:\n\n| From | To | Trigger |\n|------|----|---------|\n| `init` | `running` | `\u002Fhub:spawn` completes |\n| `running` | `evaluating` | All agents return |\n| `evaluating` | `merged` | `\u002Fhub:merge` completes |\n| `evaluating` | `archived` | No winner \u002F all failed |\n\n## Proactive Triggers\n\nThe coordinator should act when:\n\n| Signal | Action |\n|--------|--------|\n| All agents crashed | Post failure summary, suggest retry with different constraints |\n| No improvement over baseline | Archive session, suggest different approaches |\n| Orphan worktrees detected | Run `session_manager.py --cleanup {id}` |\n| Session stuck in `running` | Check board for progress, consider timeout |\n\n## Installation\n\n```bash\n# Copy to your Claude Code skills directory\ncp -r engineering\u002Fagenthub ~\u002F.claude\u002Fskills\u002Fagenthub\n\n# Or install via ClawHub\nclawhub install agenthub\n```\n\n## Scripts\n\n| Script | Purpose |\n|--------|---------|\n| `hub_init.py` | Initialize `.agenthub\u002F` structure and session |\n| `dag_analyzer.py` | Frontier detection, DAG graph, branch status |\n| `board_manager.py` | Message board CRUD (channels, posts, threads) |\n| `result_ranker.py` | Rank agents by metric or diff quality |\n| `session_manager.py` | Session state machine and cleanup |\n\n## Related Skills\n\n- **autoresearch-agent** — Single-agent optimization loop (use AgentHub when you want N agents competing)\n- **self-improving-agent** — Self-modifying agent (use AgentHub when you want external competition)\n- **git-worktree-manager** — Git worktree utilities (AgentHub uses worktrees internally)\n",{"name":5,"license":15,"metadata":53,"description":7},{"author":54,"updated":55,"version":56,"category":57},"Md Faiz Alam",1773705600000,"2.1.2","engineering","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering\u002Fagenthub",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill agenthub",{"tool":72,"command":73},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill agenthub",{"tool":75,"command":76},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill agenthub","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002FSKILL.md",true,[80,86,90,94,98,102,106,110,116,120,124,128,132,136],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",703,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002F.claude-plugin\u002Fplugin.json",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"agents\u002Fhub-coordinator.md",3789,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fagents\u002Fhub-coordinator.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"CLAUDE.md",2540,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002FCLAUDE.md",{"path":95,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":96,"sourceHtmlUrl":97},"README.md",11506,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002FREADME.md",{"path":99,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fagent-templates.md",7795,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Freferences\u002Fagent-templates.md",{"path":103,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fcoordination-strategies.md",5946,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Freferences\u002Fcoordination-strategies.md",{"path":107,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fdag-patterns.md",4091,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Freferences\u002Fdag-patterns.md",{"path":111,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fboard_manager.py","SCRIPT","脚本",8562,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fscripts\u002Fboard_manager.py",{"path":117,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fdag_analyzer.py",8942,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fscripts\u002Fdag_analyzer.py",{"path":121,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Fdry_run.py",11415,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fscripts\u002Fdry_run.py",{"path":125,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":126,"sourceHtmlUrl":127},"scripts\u002Fhub_init.py",8528,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fscripts\u002Fhub_init.py",{"path":129,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":130,"sourceHtmlUrl":131},"scripts\u002Fresult_ranker.py",10557,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fscripts\u002Fresult_ranker.py",{"path":133,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":134,"sourceHtmlUrl":135},"scripts\u002Fsession_manager.py",9991,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fscripts\u002Fsession_manager.py",{"path":137,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":138,"sourceHtmlUrl":139},"settings.json",856,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fsettings.json",[141,171,196,221,251,271],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":48},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":48},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[178,179,180,181,182,183,184,185,158,159,186,187,188,189,190,191,192,193,194,195],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":48},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[203,204,205,206,207,208,209,210,211,159,212,213,214,215,216,217,218,219,220,170],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":233,"publishedAt":48},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[227,230],{"categoryNo":228,"categoryName":229,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":231,"categoryName":232,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[234,235,220,236,237,238,239,240,241,159,242,243,244,245,246,247,248,249,170,250],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":252,"name":253,"nameZh":6,"description":254,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":255,"categories":256,"keywords":258,"publishedAt":48},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[257],{"categoryNo":148,"categoryName":149,"taxonomyType":26,"taxonomyTypeDesc":27},[259,235,220,260,261,262,263,264,151,265,241,266,204,267,268,269,187,246,170,270],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":272,"name":273,"nameZh":6,"description":274,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":275,"categories":276,"keywords":282,"publishedAt":48},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[277,280,281],{"categoryNo":278,"categoryName":279,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":148,"categoryName":149,"taxonomyType":26,"taxonomyTypeDesc":27},[283,284,235,220,260,285,286,155,241,287,288,289,290,291,188,292,293,294,295,170],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]