[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBA1HDBXTCR5DPZKX1RT5M":3,"skill-same:01M6KBA1HDBXTCR5DPZKX1RT5M":59},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6KBA1HDBXTCR5DPZKX1RT5M","loop",null,"Start an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling.","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\u002Floop\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30],"start","experiment loop","user","autonomous","experiment","daily","scheduling","ar","monthly","with","for","weekly","2026-11-10 10:12:30",false,"---\nname: \"loop\"\ndescription: \"Start an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling.\"\ncommand: \u002Far:loop\n---\n\n# \u002Far:loop — Autonomous Experiment Loop\n\nStart a recurring experiment loop that runs at a user-selected interval.\n\n## Usage\n\n```\n\u002Far:loop engineering\u002Fapi-speed             # Start loop (prompts for interval)\n\u002Far:loop engineering\u002Fapi-speed 10m         # Every 10 minutes\n\u002Far:loop engineering\u002Fapi-speed 1h          # Every hour\n\u002Far:loop engineering\u002Fapi-speed daily       # Daily at ~9am\n\u002Far:loop engineering\u002Fapi-speed weekly      # Weekly on Monday ~9am\n\u002Far:loop engineering\u002Fapi-speed monthly     # Monthly on 1st ~9am\n\u002Far:loop stop engineering\u002Fapi-speed        # Stop an active loop\n```\n\n## What It Does\n\n### Step 1: Resolve experiment\n\nIf no experiment specified, list experiments and let user pick.\n\n### Step 2: Select interval\n\nIf interval not provided as argument, present options:\n\n```\nSelect loop interval:\n  1. Every 10 minutes  (rapid — stay and watch)\n  2. Every hour         (background — check back later)\n  3. Daily at ~9am      (overnight experiments)\n  4. Weekly on Monday   (long-running experiments)\n  5. Monthly on 1st     (slow experiments)\n```\n\nMap to cron expressions:\n\n| Interval | Cron Expression | Shorthand |\n|----------|----------------|-----------|\n| 10 minutes | `*\u002F10 * * * *` | `10m` |\n| 1 hour | `7 * * * *` | `1h` |\n| Daily | `57 8 * * *` | `daily` |\n| Weekly | `57 8 * * 1` | `weekly` |\n| Monthly | `57 8 1 * *` | `monthly` |\n\n### Step 3: Create the recurring job\n\nUse `CronCreate` with this prompt (fill in the experiment details):\n\n```\nYou are running autoresearch experiment \"{domain}\u002F{name}\".\n\n1. Read .autoresearch\u002F{domain}\u002F{name}\u002Fconfig.cfg for: target, evaluate_cmd, metric, metric_direction\n2. Read .autoresearch\u002F{domain}\u002F{name}\u002Fprogram.md for strategy and constraints\n3. Read .autoresearch\u002F{domain}\u002F{name}\u002Fresults.tsv for experiment history\n4. Run: git checkout autoresearch\u002F{domain}\u002F{name}\n\nThen do exactly ONE iteration:\n- Review results.tsv: what worked, what failed, what hasn't been tried\n- Edit the target file with ONE change (strategy escalation based on run count)\n- Commit: git add {target} && git commit -m \"experiment: {description}\"\n- Evaluate: python {skill_path}\u002Fscripts\u002Frun_experiment.py --experiment {domain}\u002F{name} --single\n- Read the output (KEEP\u002FDISCARD\u002FCRASH)\n\nRules:\n- ONE change per experiment\n- NEVER modify the evaluator\n- If 5 consecutive crashes in results.tsv, delete this cron job (CronDelete) and alert\n- After every 10 experiments, update Strategy section of program.md\n\nCurrent best metric: {read from results.tsv or \"no baseline yet\"}\nTotal experiments so far: {count from results.tsv}\n```\n\n### Step 4: Store loop metadata\n\nWrite to `.autoresearch\u002F{domain}\u002F{name}\u002Floop.json`:\n\n```json\n{\n  \"cron_id\": \"{id from CronCreate}\",\n  \"interval\": \"{user selection}\",\n  \"started\": \"{ISO timestamp}\",\n  \"experiment\": \"{domain}\u002F{name}\"\n}\n```\n\n### Step 5: Confirm to user\n\n```\nLoop started for {domain}\u002F{name}\n  Interval: {interval description}\n  Cron ID: {id}\n  Auto-expires: 3 days (CronCreate limit)\n\n  To check progress: \u002Far:status\n  To stop the loop:  \u002Far:loop stop {domain}\u002F{name}\n\n  Note: Recurring jobs auto-expire after 3 days.\n  Run \u002Far:loop again to restart after expiry.\n```\n\n## Stopping a Loop\n\nWhen user runs `\u002Far:loop stop {experiment}`:\n\n1. Read `.autoresearch\u002F{domain}\u002F{name}\u002Floop.json` to get the cron ID\n2. Call `CronDelete` with that ID\n3. Delete `loop.json`\n4. Confirm: \"Loop stopped for {experiment}. {n} experiments completed.\"\n\n## Important Limitations\n\n- **3-day auto-expiry**: CronCreate jobs expire after 3 days. For longer experiments, the user must re-run `\u002Far:loop` to restart. Results persist — the new loop picks up where the old one left off.\n- **One loop per experiment**: Don't start multiple loops for the same experiment.\n- **Concurrent experiments**: Multiple experiments can loop simultaneously ONLY if they're on different git branches (which they are by default — each experiment gets `autoresearch\u002F{domain}\u002F{name}`).\n","# \u002Far:loop — Autonomous Experiment Loop\n\nStart a recurring experiment loop that runs at a user-selected interval.\n\n## Usage\n\n```\n\u002Far:loop engineering\u002Fapi-speed             # Start loop (prompts for interval)\n\u002Far:loop engineering\u002Fapi-speed 10m         # Every 10 minutes\n\u002Far:loop engineering\u002Fapi-speed 1h          # Every hour\n\u002Far:loop engineering\u002Fapi-speed daily       # Daily at ~9am\n\u002Far:loop engineering\u002Fapi-speed weekly      # Weekly on Monday ~9am\n\u002Far:loop engineering\u002Fapi-speed monthly     # Monthly on 1st ~9am\n\u002Far:loop stop engineering\u002Fapi-speed        # Stop an active loop\n```\n\n## What It Does\n\n### Step 1: Resolve experiment\n\nIf no experiment specified, list experiments and let user pick.\n\n### Step 2: Select interval\n\nIf interval not provided as argument, present options:\n\n```\nSelect loop interval:\n  1. Every 10 minutes  (rapid — stay and watch)\n  2. Every hour         (background — check back later)\n  3. Daily at ~9am      (overnight experiments)\n  4. Weekly on Monday   (long-running experiments)\n  5. Monthly on 1st     (slow experiments)\n```\n\nMap to cron expressions:\n\n| Interval | Cron Expression | Shorthand |\n|----------|----------------|-----------|\n| 10 minutes | `*\u002F10 * * * *` | `10m` |\n| 1 hour | `7 * * * *` | `1h` |\n| Daily | `57 8 * * *` | `daily` |\n| Weekly | `57 8 * * 1` | `weekly` |\n| Monthly | `57 8 1 * *` | `monthly` |\n\n### Step 3: Create the recurring job\n\nUse `CronCreate` with this prompt (fill in the experiment details):\n\n```\nYou are running autoresearch experiment \"{domain}\u002F{name}\".\n\n1. Read .autoresearch\u002F{domain}\u002F{name}\u002Fconfig.cfg for: target, evaluate_cmd, metric, metric_direction\n2. Read .autoresearch\u002F{domain}\u002F{name}\u002Fprogram.md for strategy and constraints\n3. Read .autoresearch\u002F{domain}\u002F{name}\u002Fresults.tsv for experiment history\n4. Run: git checkout autoresearch\u002F{domain}\u002F{name}\n\nThen do exactly ONE iteration:\n- Review results.tsv: what worked, what failed, what hasn't been tried\n- Edit the target file with ONE change (strategy escalation based on run count)\n- Commit: git add {target} && git commit -m \"experiment: {description}\"\n- Evaluate: python {skill_path}\u002Fscripts\u002Frun_experiment.py --experiment {domain}\u002F{name} --single\n- Read the output (KEEP\u002FDISCARD\u002FCRASH)\n\nRules:\n- ONE change per experiment\n- NEVER modify the evaluator\n- If 5 consecutive crashes in results.tsv, delete this cron job (CronDelete) and alert\n- After every 10 experiments, update Strategy section of program.md\n\nCurrent best metric: {read from results.tsv or \"no baseline yet\"}\nTotal experiments so far: {count from results.tsv}\n```\n\n### Step 4: Store loop metadata\n\nWrite to `.autoresearch\u002F{domain}\u002F{name}\u002Floop.json`:\n\n```json\n{\n  \"cron_id\": \"{id from CronCreate}\",\n  \"interval\": \"{user selection}\",\n  \"started\": \"{ISO timestamp}\",\n  \"experiment\": \"{domain}\u002F{name}\"\n}\n```\n\n### Step 5: Confirm to user\n\n```\nLoop started for {domain}\u002F{name}\n  Interval: {interval description}\n  Cron ID: {id}\n  Auto-expires: 3 days (CronCreate limit)\n\n  To check progress: \u002Far:status\n  To stop the loop:  \u002Far:loop stop {domain}\u002F{name}\n\n  Note: Recurring jobs auto-expire after 3 days.\n  Run \u002Far:loop again to restart after expiry.\n```\n\n## Stopping a Loop\n\nWhen user runs `\u002Far:loop stop {experiment}`:\n\n1. Read `.autoresearch\u002F{domain}\u002F{name}\u002Floop.json` to get the cron ID\n2. Call `CronDelete` with that ID\n3. Delete `loop.json`\n4. Confirm: \"Loop stopped for {experiment}. {n} experiments completed.\"\n\n## Important Limitations\n\n- **3-day auto-expiry**: CronCreate jobs expire after 3 days. For longer experiments, the user must re-run `\u002Far:loop` to restart. Results persist — the new loop picks up where the old one left off.\n- **One loop per experiment**: Don't start multiple loops for the same experiment.\n- **Concurrent experiments**: Multiple experiments can loop simultaneously ONLY if they're on different git branches (which they are by default — each experiment gets `autoresearch\u002F{domain}\u002F{name}`).\n",{"name":5,"command":36,"description":7},"\u002Far:loop","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering\u002Fautoresearch-agent\u002Fskills\u002Floop",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":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill loop",{"tool":51,"command":52},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill loop",{"tool":54,"command":55},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill loop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fautoresearch-agent\u002Fskills\u002Floop\u002FSKILL.md",true,[],[60,91,116,141,173,193],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":71,"publishedAt":31},"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",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,29],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":31},"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",[],[98,99,100,101,102,103,104,105,79,80,106,107,108,109,110,111,112,113,114,115],"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":31},"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",[],[123,124,125,126,127,128,129,130,131,80,132,133,134,135,136,137,138,139,140,29],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"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":155,"publishedAt":31},"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",[147,152],{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":153,"categoryName":154,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000032","设计师",[156,157,140,158,159,160,161,162,163,80,164,165,166,167,168,169,170,171,29,172],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":180,"publishedAt":31},"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",[179],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},[181,157,140,182,183,184,185,186,72,187,163,188,124,189,190,191,107,168,29,192],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":206,"publishedAt":31},"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",[199,202,205],{"categoryNo":200,"categoryName":201,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":203,"categoryName":204,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},[207,208,157,140,182,209,210,76,163,211,212,213,214,215,108,216,217,218,219,29],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]