[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KB89CC05JDJVB426FXC99G":3,"skill-same:01M6KB89CC05JDJVB426FXC99G":55},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M6KB89CC05JDJVB426FXC99G","run",null,"One-shot lifecycle command that chains init → baseline → spawn → eval → merge in a single invocation.","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\u002Fskills\u002Frun\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26],"init","merge","baseline","lifecycle","eval","command","spawn","hub","2026-11-10 10:12:30",false,"---\nname: \"run\"\ndescription: \"One-shot lifecycle command that chains init → baseline → spawn → eval → merge in a single invocation.\"\ncommand: \u002Fhub:run\n---\n\n# \u002Fhub:run — One-Shot Lifecycle\n\nRun the full AgentHub lifecycle in one command: initialize, capture baseline, spawn agents, evaluate results, and merge the winner.\n\n## Usage\n\n```\n\u002Fhub:run --task \"Reduce p50 latency\" --agents 3 \\\n  --eval \"pytest bench.py --json\" --metric p50_ms --direction lower \\\n  --template optimizer\n\n\u002Fhub:run --task \"Refactor auth module\" --agents 2 --template refactorer\n\n\u002Fhub:run --task \"Cover untested utils\" --agents 3 \\\n  --eval \"pytest --cov=utils --cov-report=json\" --metric coverage_pct --direction higher \\\n  --template test-writer\n\n\u002Fhub:run --task \"Write 3 email subject lines for spring sale campaign\" --agents 3 --judge\n```\n\n## Parameters\n\n| Parameter | Required | Description |\n|-----------|----------|-------------|\n| `--task` | Yes | Task description for agents |\n| `--agents` | No | Number of parallel agents (default: 3) |\n| `--eval` | No | Eval command to measure results (skip for LLM judge mode) |\n| `--metric` | No | Metric name to extract from eval output (required if `--eval` given) |\n| `--direction` | No | `lower` or `higher` — which direction is better (required if `--metric` given) |\n| `--template` | No | Agent template: `optimizer`, `refactorer`, `test-writer`, `bug-fixer` |\n\n## What It Does\n\nExecute these steps sequentially:\n\n### Step 1: Initialize\n\nRun `\u002Fhub:init` with the provided arguments:\n\n```bash\npython {skill_path}\u002Fscripts\u002Fhub_init.py \\\n  --task \"{task}\" --agents {N} \\\n  [--eval \"{eval_cmd}\"] [--metric {metric}] [--direction {direction}]\n```\n\nDisplay the session ID to the user.\n\n### Step 2: Capture Baseline\n\nIf `--eval` was provided:\n\n1. Run the eval command in the current working directory\n2. Extract the metric value from stdout\n3. Display: `Baseline captured: {metric} = {value}`\n4. Append `baseline: {value}` to `.agenthub\u002Fsessions\u002F{session-id}\u002Fconfig.yaml`\n\nIf no `--eval` was provided, skip this step.\n\n### Step 3: Spawn Agents\n\nRun `\u002Fhub:spawn` with the session ID.\n\nIf `--template` was provided, use the template dispatch prompt from `references\u002Fagent-templates.md` instead of the default dispatch prompt. Pass the eval command, metric, and baseline to the template variables.\n\nLaunch all agents in a single message with multiple Agent tool calls (true parallelism).\n\n### Step 4: Wait and Monitor\n\nAfter spawning, inform the user that agents are running. When all agents complete (Agent tool returns results):\n\n1. Display a brief summary of each agent's work\n2. Proceed to evaluation\n\n### Step 5: Evaluate\n\nRun `\u002Fhub:eval` with the session ID:\n\n- If `--eval` was provided: metric-based ranking with `result_ranker.py`\n- If no `--eval`: LLM judge mode (coordinator reads diffs and ranks)\n\nIf baseline was captured, pass `--baseline {value}` to `result_ranker.py` so deltas are shown.\n\nDisplay the ranked results table.\n\n### Step 6: Confirm and Merge\n\nPresent the results to the user and ask for confirmation:\n\n```\nAgent-2 is the winner (128ms, -52ms from baseline).\nMerge agent-2's branch? [Y\u002Fn]\n```\n\nIf confirmed, run `\u002Fhub:merge`. If declined, inform the user they can:\n- `\u002Fhub:merge --agent agent-{N}` to pick a different winner\n- `\u002Fhub:eval --judge` to re-evaluate with LLM judge\n- Inspect branches manually\n\n## Critical Rules\n\n- **Sequential execution** — each step depends on the previous\n- **Stop on failure** — if any step fails, report the error and stop\n- **User confirms merge** — never auto-merge without asking\n- **Template is optional** — without `--template`, agents use the default dispatch prompt from `\u002Fhub:spawn`\n","# \u002Fhub:run — One-Shot Lifecycle\n\nRun the full AgentHub lifecycle in one command: initialize, capture baseline, spawn agents, evaluate results, and merge the winner.\n\n## Usage\n\n```\n\u002Fhub:run --task \"Reduce p50 latency\" --agents 3 \\\n  --eval \"pytest bench.py --json\" --metric p50_ms --direction lower \\\n  --template optimizer\n\n\u002Fhub:run --task \"Refactor auth module\" --agents 2 --template refactorer\n\n\u002Fhub:run --task \"Cover untested utils\" --agents 3 \\\n  --eval \"pytest --cov=utils --cov-report=json\" --metric coverage_pct --direction higher \\\n  --template test-writer\n\n\u002Fhub:run --task \"Write 3 email subject lines for spring sale campaign\" --agents 3 --judge\n```\n\n## Parameters\n\n| Parameter | Required | Description |\n|-----------|----------|-------------|\n| `--task` | Yes | Task description for agents |\n| `--agents` | No | Number of parallel agents (default: 3) |\n| `--eval` | No | Eval command to measure results (skip for LLM judge mode) |\n| `--metric` | No | Metric name to extract from eval output (required if `--eval` given) |\n| `--direction` | No | `lower` or `higher` — which direction is better (required if `--metric` given) |\n| `--template` | No | Agent template: `optimizer`, `refactorer`, `test-writer`, `bug-fixer` |\n\n## What It Does\n\nExecute these steps sequentially:\n\n### Step 1: Initialize\n\nRun `\u002Fhub:init` with the provided arguments:\n\n```bash\npython {skill_path}\u002Fscripts\u002Fhub_init.py \\\n  --task \"{task}\" --agents {N} \\\n  [--eval \"{eval_cmd}\"] [--metric {metric}] [--direction {direction}]\n```\n\nDisplay the session ID to the user.\n\n### Step 2: Capture Baseline\n\nIf `--eval` was provided:\n\n1. Run the eval command in the current working directory\n2. Extract the metric value from stdout\n3. Display: `Baseline captured: {metric} = {value}`\n4. Append `baseline: {value}` to `.agenthub\u002Fsessions\u002F{session-id}\u002Fconfig.yaml`\n\nIf no `--eval` was provided, skip this step.\n\n### Step 3: Spawn Agents\n\nRun `\u002Fhub:spawn` with the session ID.\n\nIf `--template` was provided, use the template dispatch prompt from `references\u002Fagent-templates.md` instead of the default dispatch prompt. Pass the eval command, metric, and baseline to the template variables.\n\nLaunch all agents in a single message with multiple Agent tool calls (true parallelism).\n\n### Step 4: Wait and Monitor\n\nAfter spawning, inform the user that agents are running. When all agents complete (Agent tool returns results):\n\n1. Display a brief summary of each agent's work\n2. Proceed to evaluation\n\n### Step 5: Evaluate\n\nRun `\u002Fhub:eval` with the session ID:\n\n- If `--eval` was provided: metric-based ranking with `result_ranker.py`\n- If no `--eval`: LLM judge mode (coordinator reads diffs and ranks)\n\nIf baseline was captured, pass `--baseline {value}` to `result_ranker.py` so deltas are shown.\n\nDisplay the ranked results table.\n\n### Step 6: Confirm and Merge\n\nPresent the results to the user and ask for confirmation:\n\n```\nAgent-2 is the winner (128ms, -52ms from baseline).\nMerge agent-2's branch? [Y\u002Fn]\n```\n\nIf confirmed, run `\u002Fhub:merge`. If declined, inform the user they can:\n- `\u002Fhub:merge --agent agent-{N}` to pick a different winner\n- `\u002Fhub:eval --judge` to re-evaluate with LLM judge\n- Inspect branches manually\n\n## Critical Rules\n\n- **Sequential execution** — each step depends on the previous\n- **Stop on failure** — if any step fails, report the error and stop\n- **User confirms merge** — never auto-merge without asking\n- **Template is optional** — without `--template`, agents use the default dispatch prompt from `\u002Fhub:spawn`\n",{"name":5,"command":32,"description":7},"\u002Fhub:run","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering\u002Fagenthub\u002Fskills\u002Frun",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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill run",{"tool":47,"command":48},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill run",{"tool":50,"command":51},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill run","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fagenthub\u002Fskills\u002Frun\u002FSKILL.md",true,[],[56,88,112,137,169,189],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":67,"publishedAt":27},"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",[62],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":27},"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",[],[95,96,97,98,99,100,101,22,75,76,102,103,104,105,106,107,108,109,110,111],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":27},"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",[],[119,120,121,122,123,124,125,126,127,76,128,129,130,131,132,133,134,135,136,87],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":151,"publishedAt":27},"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",[143,148],{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":149,"categoryName":150,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000032","设计师",[152,153,136,154,155,156,157,158,159,76,160,161,162,163,164,165,166,167,87,168],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":27},"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",[175],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[177,153,136,178,179,180,181,182,68,183,159,184,120,185,186,187,103,164,87,188],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":202,"publishedAt":27},"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",[195,198,201],{"categoryNo":196,"categoryName":197,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":199,"categoryName":200,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[203,204,153,136,178,205,206,72,159,207,208,209,210,211,104,212,213,214,215,87],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]