[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XBWYKBCDFK55212C8TE24Z":3,"skill-same:01M6XBWYKBCDFK55212C8TE24Z":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":13,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6XBWYKBCDFK55212C8TE24Z","regulatory-fallback-research",null,"Handle tool failures when researching regulatory\u002Fgovernment content by using fallback methods and domain knowledge","UF-gzj\u002Fopenspace-claude-evolution","UF-gzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272393507?v=4","01M6XBCZB755P01VVYGQWPYZY3","01M6XBCZFJA5AREA17WGETA3FW",0,"MIT","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fregulatory-fallback-research\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32],"research","regulatory","fallback","regulatory fallback research","content","knowledge","tool","methods","domain","when","2026-11-10 10:12:30",false,"---\nname: regulatory-fallback-research\ndescription: Handle tool failures when researching regulatory\u002Fgovernment content by using fallback methods and domain knowledge\n---\n\n# Regulatory\u002FGovernment Content Research with Fallback Strategy\n\n## Overview\n\nWhen researching regulatory, government, or compliance-related content, primary sources (official websites, PDFs, regulatory databases) often become inaccessible due to tool failures, access restrictions, or technical issues. This skill provides a resilient workflow to complete research tasks despite these obstacles.\n\n## When to Use This Skill\n\nUse this workflow when:\n- You need to research regulatory\u002Fgovernment content (FDA, CMS, DEA, state boards, etc.)\n- Primary source tools (read_webpage, search_web) return 'unknown error' or fail repeatedly\n- You need to produce compliance documentation, checklists, or regulatory summaries\n\n## Step-by-Step Procedure\n\n### Step 1: Attempt Primary Source Access\n\nFirst, try to access official sources directly:\n\n```\n1. Use read_webpage on known regulatory URLs\n2. Use search_web for specific regulatory queries\n3. Attempt read_file on any available PDFs or documents\n```\n\n**Expected outcomes:**\n- Success: Proceed with content extraction\n- 'unknown error' or repeated failures: Document the failure and proceed to Step 2\n\n### Step 2: Deploy Shell Agent for Secondary Research\n\nWhen primary tools fail, use shell_agent for alternative information gathering:\n\n```\nshell_agent task: \"Research [topic] compliance requirements using alternative sources. \nSearch for summaries, guides, or cached versions of regulatory information. \nFocus on established compliance frameworks and best practices.\"\n```\n\n**Strategies for shell_agent:**\n- Request research from multiple angles (state vs federal, industry guides, etc.)\n- Ask for aggregated information from secondary sources\n- Request compliance checklist templates from industry resources\n\n### Step 3: Apply Domain Knowledge\n\nWhen both primary and secondary research tools fail:\n\n```\n1. Acknowledge the tool limitations explicitly\n2. State you will proceed using established domain knowledge\n3. Create content based on well-known regulatory frameworks\n```\n\n**Key domains to leverage:**\n- **Pharmacy compliance**: HIPAA, OBRA-90, controlled substance handling, prescription verification, drug storage, patient counseling\n- **Healthcare compliance**: OSHA, HIPAA privacy\u002Fsecurity, Medicare\u002FMedicaid billing, infection control\n- **General regulatory**: Documentation requirements, audit trails, staff training, record retention\n\n### Step 4: Produce Deliverables Despite Limitations\n\nContinue to completion:\n\n```\n1. Create required outputs (checklists, summaries, documentation)\n2. Note any limitations due to inaccessible sources\n3. Recommend verification against current official sources\n4. Structure content for easy updating when sources become available\n```\n\n## Code Examples\n\n### Example: Handling Multiple Tool Failures\n\n```\n# Document failures transparently\n\"Note: Primary regulatory sources (FDA.gov, state board websites) \nreturned access errors. Content compiled from established \ncompliance frameworks and industry standards.\"\n\n# Proceed with domain knowledge\ncreate_pharmacy_checklist(\n    categories=[\"prescription_handling\", \"controlled_substances\", \n                \"patient_counseling\", \"record_keeping\"],\n    basis=\"OBRA-90 and standard pharmacy practice guidelines\"\n)\n\n# Add verification disclaimer\n\"Recommendation: Verify all requirements against current state \nboard regulations before implementation.\"\n```\n\n### Example: Shell Agent Fallback Query\n\n```\nshell_agent task: \"Gather pharmacy compliance requirements from \nsecondary sources including:\n1. Industry association guidelines (NCPDP, ASHP)\n2. Academic pharmacy practice resources\n3. State board examination study materials\n4. Compliance training program outlines\n\nCompile into structured checklist format.\"\n```\n\n## Best Practices\n\n1. **Never abandon the task** - Tool failures are common with government sites; persist using available methods\n\n2. **Be transparent** - Always document which sources were inaccessible and what basis you used instead\n\n3. **Structure for updates** - Create modular content that can be easily revised when sources become available\n\n4. **Prioritize safety-critical items** - When uncertain, include conservative compliance measures\n\n5. **Recommend verification** - Always advise end-users to verify against current official sources\n\n## Common Failure Scenarios\n\n| Failure | Fallback Action |\n|---------|-----------------|\n| read_webpage 'unknown error' | Try search_web, then shell_agent |\n| search_web 'unknown error' | Try shell_agent research task |\n| shell_agent timeout\u002Ffailure | Proceed with domain knowledge |\n| All tools fail | Use established domain knowledge, document limitations |\n\n## Quality Criteria\n\nYour output is successful when:\n- [ ] All required deliverables are produced\n- [ ] Tool failures are documented transparently\n- [ ] Content is based on verifiable regulatory frameworks\n- [ ] Verification recommendations are included\n- [ ] Content structure allows easy updates\n\n---\nname: regulatory-fallback-research\ndescription: Handle tool failures when researching regulatory\u002Fgovernment content by using fallback methods and domain knowledge\n---","# Regulatory\u002FGovernment Content Research with Fallback Strategy\n\n## Overview\n\nWhen researching regulatory, government, or compliance-related content, primary sources (official websites, PDFs, regulatory databases) often become inaccessible due to tool failures, access restrictions, or technical issues. This skill provides a resilient workflow to complete research tasks despite these obstacles.\n\n## When to Use This Skill\n\nUse this workflow when:\n- You need to research regulatory\u002Fgovernment content (FDA, CMS, DEA, state boards, etc.)\n- Primary source tools (read_webpage, search_web) return 'unknown error' or fail repeatedly\n- You need to produce compliance documentation, checklists, or regulatory summaries\n\n## Step-by-Step Procedure\n\n### Step 1: Attempt Primary Source Access\n\nFirst, try to access official sources directly:\n\n```\n1. Use read_webpage on known regulatory URLs\n2. Use search_web for specific regulatory queries\n3. Attempt read_file on any available PDFs or documents\n```\n\n**Expected outcomes:**\n- Success: Proceed with content extraction\n- 'unknown error' or repeated failures: Document the failure and proceed to Step 2\n\n### Step 2: Deploy Shell Agent for Secondary Research\n\nWhen primary tools fail, use shell_agent for alternative information gathering:\n\n```\nshell_agent task: \"Research [topic] compliance requirements using alternative sources. \nSearch for summaries, guides, or cached versions of regulatory information. \nFocus on established compliance frameworks and best practices.\"\n```\n\n**Strategies for shell_agent:**\n- Request research from multiple angles (state vs federal, industry guides, etc.)\n- Ask for aggregated information from secondary sources\n- Request compliance checklist templates from industry resources\n\n### Step 3: Apply Domain Knowledge\n\nWhen both primary and secondary research tools fail:\n\n```\n1. Acknowledge the tool limitations explicitly\n2. State you will proceed using established domain knowledge\n3. Create content based on well-known regulatory frameworks\n```\n\n**Key domains to leverage:**\n- **Pharmacy compliance**: HIPAA, OBRA-90, controlled substance handling, prescription verification, drug storage, patient counseling\n- **Healthcare compliance**: OSHA, HIPAA privacy\u002Fsecurity, Medicare\u002FMedicaid billing, infection control\n- **General regulatory**: Documentation requirements, audit trails, staff training, record retention\n\n### Step 4: Produce Deliverables Despite Limitations\n\nContinue to completion:\n\n```\n1. Create required outputs (checklists, summaries, documentation)\n2. Note any limitations due to inaccessible sources\n3. Recommend verification against current official sources\n4. Structure content for easy updating when sources become available\n```\n\n## Code Examples\n\n### Example: Handling Multiple Tool Failures\n\n```\n# Document failures transparently\n\"Note: Primary regulatory sources (FDA.gov, state board websites) \nreturned access errors. Content compiled from established \ncompliance frameworks and industry standards.\"\n\n# Proceed with domain knowledge\ncreate_pharmacy_checklist(\n    categories=[\"prescription_handling\", \"controlled_substances\", \n                \"patient_counseling\", \"record_keeping\"],\n    basis=\"OBRA-90 and standard pharmacy practice guidelines\"\n)\n\n# Add verification disclaimer\n\"Recommendation: Verify all requirements against current state \nboard regulations before implementation.\"\n```\n\n### Example: Shell Agent Fallback Query\n\n```\nshell_agent task: \"Gather pharmacy compliance requirements from \nsecondary sources including:\n1. Industry association guidelines (NCPDP, ASHP)\n2. Academic pharmacy practice resources\n3. State board examination study materials\n4. Compliance training program outlines\n\nCompile into structured checklist format.\"\n```\n\n## Best Practices\n\n1. **Never abandon the task** - Tool failures are common with government sites; persist using available methods\n\n2. **Be transparent** - Always document which sources were inaccessible and what basis you used instead\n\n3. **Structure for updates** - Create modular content that can be easily revised when sources become available\n\n4. **Prioritize safety-critical items** - When uncertain, include conservative compliance measures\n\n5. **Recommend verification** - Always advise end-users to verify against current official sources\n\n## Common Failure Scenarios\n\n| Failure | Fallback Action |\n|---------|-----------------|\n| read_webpage 'unknown error' | Try search_web, then shell_agent |\n| search_web 'unknown error' | Try shell_agent research task |\n| shell_agent timeout\u002Ffailure | Proceed with domain knowledge |\n| All tools fail | Use established domain knowledge, document limitations |\n\n## Quality Criteria\n\nYour output is successful when:\n- [ ] All required deliverables are produced\n- [ ] Tool failures are documented transparently\n- [ ] Content is based on verifiable regulatory frameworks\n- [ ] Verification recommendations are included\n- [ ] Content structure allows easy updates\n\n---\nname: regulatory-fallback-research\ndescription: Handle tool failures when researching regulatory\u002Fgovernment content by using fallback methods and domain knowledge\n---",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fregulatory-fallback-research","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution","https:\u002F\u002Fgithub.com\u002FUF-gzj","2026-04-16 09:31:03",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill regulatory-fallback-research",{"tool":50,"command":51},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill regulatory-fallback-research",{"tool":53,"command":54},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill regulatory-fallback-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fregulatory-fallback-research\u002FSKILL.md",true,[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},".skill_id","OTHER","其他",42,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fregulatory-fallback-research\u002F.skill_id",[65,90,107,116,146,162],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":33},"01M6XCCXD3NCM2YKR3WNGBASPC","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","output","type","files","only","template","file","python",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":33},"01M6XCCT7E3J922Q345PBGSHPN","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[97,98,73,88,99,89,100,101,102,103,104,87,105,106,77,80,82],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification","with",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":33},"01M6XCCMQX1R8B6FECWB3P63T7","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[114,73,77,115,82,101,87,88,89,80],"write special chars heredoc","shell",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"publishedAt":33},"01M6XCCG41M994JJEX6VN52PEP","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[128,129,130,131,132,75,133,134,135,136,137,80,138,139,140,141,142,143,144,145],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":33},"01M6XCCCHWNKG2W4VH9E6A10HF","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[153,154,155,156,80,157,106,158,159,160,161],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":33},"01M6XCC7X8PKMR2DEW91XGHYSV","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[169,170,171,172,173,174,88,175,176,177],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]