[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XBX21TS9RBTS37P2HMN8QC":3,"skill-same:01M6XBX21TS9RBTS37P2HMN8QC":68},{"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":25,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":13,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6XBX21TS9RBTS37P2HMN8QC","regulatory-research-fallback",null,"Fallback workflow for regulatory research when web extraction tools fail on government PDFs","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-research-fallback\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,27,28,29,30,31,32,33,34,35,36],"research","regulatory","fallback","regulatory research fallback","research fallback","workflow","web","extraction","Tools","for","when","2026-11-10 10:12:30",false,"---\nname: regulatory-research-fallback\ndescription: Fallback workflow for regulatory research when web extraction tools fail on government PDFs\n---\n\n# Regulatory Research Fallback Workflow\n\nThis skill provides a systematic approach to gathering regulatory\u002Fcompliance information when primary web extraction tools fail on government or regulatory website URLs.\n\n## When to Use This Skill\n\n- `read_webpage` returns \"unknown error\" on .gov or regulatory PDF URLs\n- `search_web` fails to retrieve current regulatory information\n- You need to create compliance checklists or regulatory documentation\n- Primary sources are inaccessible but the task must be completed\n\n## Step-by-Step Procedure\n\n### Step 1: Attempt Primary Source Extraction\n\nFirst, try standard web extraction tools:\n\n```\n1. Use read_webpage on the regulatory URL\n2. Use search_web for supplementary regulatory information\n3. Document which tools failed and with what errors\n```\n\n### Step 2: Activate Fallback - Shell Agent Research\n\nWhen primary tools fail, delegate to shell_agent for secondary research:\n\n```\nTask: \"Research [TOPIC] compliance requirements using available system tools. \nGather information from alternative sources including:\n- State\u002Ffederal regulatory summaries\n- Industry compliance guides\n- Professional association resources\nFocus on actionable checklist items for [SPECIFIC REQUIREMENT]\"\n```\n\nExample shell_agent task for pharmacy compliance:\n```\n\"Research pharmacy compliance requirements for [state]. Gather information \nabout licensing, storage, dispensing, and documentation requirements from \navailable sources. Create structured notes on mandatory compliance areas.\"\n```\n\n### Step 3: Apply Domain Knowledge\n\nWhen sources remain inaccessible, use established domain knowledge:\n\n```\nFor pharmacy compliance, standard areas include:\n- Licensing and registration requirements\n- Controlled substance handling\n- Prescription record-keeping\n- Storage and security protocols\n- Patient counseling requirements\n- Continuing education obligations\n```\n\n### Step 4: Create Documentation with Confidence Levels\n\nStructure output with clear sourcing transparency:\n\n```markdown\n## [Requirement Area]\n\n**Status**: Based on standard regulatory framework (primary sources inaccessible)\n\n**Key Requirements**:\n- [Item 1] - Standard industry requirement\n- [Item 2] - Common regulatory expectation\n- [Item 3] - Best practice guideline\n\n**Note**: Verify with [specific agency] for jurisdiction-specific requirements\n```\n\n### Step 5: Flag Verification Needs\n\nAlways include disclaimers when using fallback approach:\n\n```\n⚠️ **Verification Required**: This checklist was created using secondary \nsources due to primary regulatory website inaccessibility. Please verify \nall requirements with the official [Agency Name] before implementation.\n```\n\n## Key Principles\n\n1. **Persevere through failures** - Tool errors don't mean task failure\n2. **Layer your research** - Try multiple approaches before concluding information is unavailable\n3. **Be transparent** - Clearly mark when information comes from secondary sources\n4. **Provide value anyway** - A best-effort checklist is better than no guidance\n5. **Flag verification needs** - Help users understand what needs official confirmation\n\n## Example Output Structure\n\n```markdown\n# [Compliance Area] Checklist\n\n## Source Transparency\nThis document was created using secondary research methods due to \ninaccessibility of primary regulatory sources. All items should be \nverified with official authorities.\n\n## Core Requirements\n[Checklist items based on standard regulatory framework]\n\n## Verification Steps\n[List of specific items requiring official confirmation]\n\n## Recommended Next Actions\n1. Contact [Agency] for current requirements\n2. Review [Official Publication] when accessible\n3. Consult with [Professional Association] for updates\n```\n\n## Applicable Domains\n\nThis workflow applies to:\n- Pharmacy\u002Fhealthcare compliance\n- Financial regulatory requirements\n- Environmental compliance\n- Building codes and permits\n- Employment law requirements\n- Any jurisdiction-specific regulatory research\n\n---\nname: regulatory-research-fallback\ncategory: workflow\nversion: 1.0\n---","# Regulatory Research Fallback Workflow\n\nThis skill provides a systematic approach to gathering regulatory\u002Fcompliance information when primary web extraction tools fail on government or regulatory website URLs.\n\n## When to Use This Skill\n\n- `read_webpage` returns \"unknown error\" on .gov or regulatory PDF URLs\n- `search_web` fails to retrieve current regulatory information\n- You need to create compliance checklists or regulatory documentation\n- Primary sources are inaccessible but the task must be completed\n\n## Step-by-Step Procedure\n\n### Step 1: Attempt Primary Source Extraction\n\nFirst, try standard web extraction tools:\n\n```\n1. Use read_webpage on the regulatory URL\n2. Use search_web for supplementary regulatory information\n3. Document which tools failed and with what errors\n```\n\n### Step 2: Activate Fallback - Shell Agent Research\n\nWhen primary tools fail, delegate to shell_agent for secondary research:\n\n```\nTask: \"Research [TOPIC] compliance requirements using available system tools. \nGather information from alternative sources including:\n- State\u002Ffederal regulatory summaries\n- Industry compliance guides\n- Professional association resources\nFocus on actionable checklist items for [SPECIFIC REQUIREMENT]\"\n```\n\nExample shell_agent task for pharmacy compliance:\n```\n\"Research pharmacy compliance requirements for [state]. Gather information \nabout licensing, storage, dispensing, and documentation requirements from \navailable sources. Create structured notes on mandatory compliance areas.\"\n```\n\n### Step 3: Apply Domain Knowledge\n\nWhen sources remain inaccessible, use established domain knowledge:\n\n```\nFor pharmacy compliance, standard areas include:\n- Licensing and registration requirements\n- Controlled substance handling\n- Prescription record-keeping\n- Storage and security protocols\n- Patient counseling requirements\n- Continuing education obligations\n```\n\n### Step 4: Create Documentation with Confidence Levels\n\nStructure output with clear sourcing transparency:\n\n```markdown\n## [Requirement Area]\n\n**Status**: Based on standard regulatory framework (primary sources inaccessible)\n\n**Key Requirements**:\n- [Item 1] - Standard industry requirement\n- [Item 2] - Common regulatory expectation\n- [Item 3] - Best practice guideline\n\n**Note**: Verify with [specific agency] for jurisdiction-specific requirements\n```\n\n### Step 5: Flag Verification Needs\n\nAlways include disclaimers when using fallback approach:\n\n```\n⚠️ **Verification Required**: This checklist was created using secondary \nsources due to primary regulatory website inaccessibility. Please verify \nall requirements with the official [Agency Name] before implementation.\n```\n\n## Key Principles\n\n1. **Persevere through failures** - Tool errors don't mean task failure\n2. **Layer your research** - Try multiple approaches before concluding information is unavailable\n3. **Be transparent** - Clearly mark when information comes from secondary sources\n4. **Provide value anyway** - A best-effort checklist is better than no guidance\n5. **Flag verification needs** - Help users understand what needs official confirmation\n\n## Example Output Structure\n\n```markdown\n# [Compliance Area] Checklist\n\n## Source Transparency\nThis document was created using secondary research methods due to \ninaccessibility of primary regulatory sources. All items should be \nverified with official authorities.\n\n## Core Requirements\n[Checklist items based on standard regulatory framework]\n\n## Verification Steps\n[List of specific items requiring official confirmation]\n\n## Recommended Next Actions\n1. Contact [Agency] for current requirements\n2. Review [Official Publication] when accessible\n3. Consult with [Professional Association] for updates\n```\n\n## Applicable Domains\n\nThis workflow applies to:\n- Pharmacy\u002Fhealthcare compliance\n- Financial regulatory requirements\n- Environmental compliance\n- Building codes and permits\n- Employment law requirements\n- Any jurisdiction-specific regulatory research\n\n---\nname: regulatory-research-fallback\ncategory: workflow\nversion: 1.0\n---",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fregulatory-research-fallback","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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill regulatory-research-fallback",{"tool":54,"command":55},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill regulatory-research-fallback",{"tool":57,"command":58},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill regulatory-research-fallback","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fregulatory-research-fallback\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},".skill_id","OTHER","其他",42,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fregulatory-research-fallback\u002F.skill_id",[69,93,110,119,149,165],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":37},"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",[],[76,77,78,79,80,81,82,83,35,84,85,86,87,88,89,90,91,92],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","errors","script","output","type","files","only","template","file","python",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":37},"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",[],[100,101,77,91,102,92,103,104,105,106,107,90,108,109,81,35,85],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification","with",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":37},"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",[],[117,77,81,118,85,104,90,91,92,35],"write special chars heredoc","shell",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":130,"publishedAt":37},"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",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[131,132,133,134,135,79,136,137,138,139,140,35,141,142,143,144,145,146,147,148],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":37},"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",[],[156,157,158,159,35,160,109,161,162,163,164],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":37},"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",[],[172,173,174,175,176,177,91,178,179,180],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]