[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBA7W278DXJZKWJBCJBZCC":3,"skill-same:01M6KBA7W278DXJZKWJBCJBZCC":54},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6KBA7W278DXJZKWJBCJBZCC","run",null,"Run a single experiment iteration. Edit the target file, evaluate, keep or discard.","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\u002Fautoresearch-agent\u002Fskills\u002Frun\u002FSKILL.md",[],[5,19,20,21,22,23,24,25],"file","edit","experiment","iteration","ar","keep","evaluate","2026-11-10 10:12:30",false,"---\nname: \"run\"\ndescription: \"Run a single experiment iteration. Edit the target file, evaluate, keep or discard.\"\ncommand: \u002Far:run\n---\n\n# \u002Far:run — Single Experiment Iteration\n\nRun exactly ONE experiment iteration: review history, decide a change, edit, commit, evaluate.\n\n## Usage\n\n```\n\u002Far:run engineering\u002Fapi-speed              # Run one iteration\n\u002Far:run                                     # List experiments, let user pick\n```\n\n## What It Does\n\n### Step 1: Resolve experiment\n\nIf no experiment specified, run `python {skill_path}\u002Fscripts\u002Fsetup_experiment.py --list` and ask the user to pick.\n\n### Step 2: Load context\n\n```bash\n# Read experiment config\ncat .autoresearch\u002F{domain}\u002F{name}\u002Fconfig.cfg\n\n# Read strategy and constraints\ncat .autoresearch\u002F{domain}\u002F{name}\u002Fprogram.md\n\n# Read experiment history\ncat .autoresearch\u002F{domain}\u002F{name}\u002Fresults.tsv\n\n# Checkout the experiment branch\ngit checkout autoresearch\u002F{domain}\u002F{name}\n```\n\n### Step 3: Decide what to try\n\nReview results.tsv:\n- What changes were kept? What pattern do they share?\n- What was discarded? Avoid repeating those approaches.\n- What crashed? Understand why.\n- How many runs so far? (Escalate strategy accordingly)\n\n**Strategy escalation:**\n- Runs 1-5: Low-hanging fruit (obvious improvements)\n- Runs 6-15: Systematic exploration (vary one parameter)\n- Runs 16-30: Structural changes (algorithm swaps)\n- Runs 30+: Radical experiments (completely different approaches)\n\n### Step 4: Make ONE change\n\nEdit only the target file specified in config.cfg. Change one thing. Keep it simple.\n\n### Step 5: Commit and evaluate\n\n```bash\ngit add {target}\ngit commit -m \"experiment: {short description of what changed}\"\n\npython {skill_path}\u002Fscripts\u002Frun_experiment.py \\\n  --experiment {domain}\u002F{name} --single\n```\n\n### Step 6: Report result\n\nRead the script output. Tell the user:\n- **KEEP**: \"Improvement! {metric}: {value} ({delta} from previous best)\"\n- **DISCARD**: \"No improvement. {metric}: {value} vs best {best}. Reverted.\"\n- **CRASH**: \"Evaluation failed: {reason}. Reverted.\"\n\n### Step 7: Self-improvement check\n\nAfter every 10th experiment (check results.tsv line count), update the Strategy section of program.md with patterns learned.\n\n## Rules\n\n- ONE change per iteration. Don't change 5 things at once.\n- NEVER modify the evaluator (evaluate.py). It's ground truth.\n- Simplicity wins. Equal performance with simpler code is an improvement.\n- No new dependencies.\n","# \u002Far:run — Single Experiment Iteration\n\nRun exactly ONE experiment iteration: review history, decide a change, edit, commit, evaluate.\n\n## Usage\n\n```\n\u002Far:run engineering\u002Fapi-speed              # Run one iteration\n\u002Far:run                                     # List experiments, let user pick\n```\n\n## What It Does\n\n### Step 1: Resolve experiment\n\nIf no experiment specified, run `python {skill_path}\u002Fscripts\u002Fsetup_experiment.py --list` and ask the user to pick.\n\n### Step 2: Load context\n\n```bash\n# Read experiment config\ncat .autoresearch\u002F{domain}\u002F{name}\u002Fconfig.cfg\n\n# Read strategy and constraints\ncat .autoresearch\u002F{domain}\u002F{name}\u002Fprogram.md\n\n# Read experiment history\ncat .autoresearch\u002F{domain}\u002F{name}\u002Fresults.tsv\n\n# Checkout the experiment branch\ngit checkout autoresearch\u002F{domain}\u002F{name}\n```\n\n### Step 3: Decide what to try\n\nReview results.tsv:\n- What changes were kept? What pattern do they share?\n- What was discarded? Avoid repeating those approaches.\n- What crashed? Understand why.\n- How many runs so far? (Escalate strategy accordingly)\n\n**Strategy escalation:**\n- Runs 1-5: Low-hanging fruit (obvious improvements)\n- Runs 6-15: Systematic exploration (vary one parameter)\n- Runs 16-30: Structural changes (algorithm swaps)\n- Runs 30+: Radical experiments (completely different approaches)\n\n### Step 4: Make ONE change\n\nEdit only the target file specified in config.cfg. Change one thing. Keep it simple.\n\n### Step 5: Commit and evaluate\n\n```bash\ngit add {target}\ngit commit -m \"experiment: {short description of what changed}\"\n\npython {skill_path}\u002Fscripts\u002Frun_experiment.py \\\n  --experiment {domain}\u002F{name} --single\n```\n\n### Step 6: Report result\n\nRead the script output. Tell the user:\n- **KEEP**: \"Improvement! {metric}: {value} ({delta} from previous best)\"\n- **DISCARD**: \"No improvement. {metric}: {value} vs best {best}. Reverted.\"\n- **CRASH**: \"Evaluation failed: {reason}. Reverted.\"\n\n### Step 7: Self-improvement check\n\nAfter every 10th experiment (check results.tsv line count), update the Strategy section of program.md with patterns learned.\n\n## Rules\n\n- ONE change per iteration. Don't change 5 things at once.\n- NEVER modify the evaluator (evaluate.py). It's ground truth.\n- Simplicity wins. Equal performance with simpler code is an improvement.\n- No new dependencies.\n",{"name":5,"command":31,"description":7},"\u002Far:run","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering\u002Fautoresearch-agent\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":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill run",{"tool":46,"command":47},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill run",{"tool":49,"command":50},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill run","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fautoresearch-agent\u002Fskills\u002Frun\u002FSKILL.md",true,[],[55,87,112,137,169,189],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":66,"publishedAt":26},"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",[61],{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":26},"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",[],[94,95,96,97,98,99,100,101,74,75,102,103,104,105,106,107,108,109,110,111],"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":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":26},"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,75,128,129,130,131,132,133,134,135,136,86],"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":26},"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":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000032","设计师",[152,153,136,154,155,156,157,158,159,75,160,161,162,163,164,165,166,167,86,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":26},"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":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},[177,153,136,178,179,180,181,182,67,183,159,184,120,185,186,187,103,164,86,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":26},"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":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},[203,204,153,136,178,205,206,71,159,207,208,209,210,211,104,212,213,214,215,86],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]