[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XBXM83TQ3DTGTXMQT4ZTTX":3,"skill-same:01M6XBXM83TQ3DTGTXMQT4ZTTX":66},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":13,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M6XBXM83TQ3DTGTXMQT4ZTTX","research-fallback-robust",null,"Handle web research failures with explicit error recognition and domain-specific fallback strategies","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\u002Fresearch-fallback-enhanced\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34],"research","fallback","research fallback robust","research fallback","web","web research","domain","domain-specific","strategies","error","recognition","with","2026-11-10 10:12:30",false,"---\nname: research-fallback-robust\ndescription: Handle web research failures with explicit error recognition and domain-specific fallback strategies\n---\n\n# Research Fallback Workflow\n\nThis skill provides a workflow for handling tasks that require external research when web search or webpage reading tools fail due to network issues or tool unavailability.\n\n## When to Use\n\n- Task requires external research (legal analysis, market research, technical documentation, anatomical\u002Fmedical information, etc.)\n- Web search or webpage reading tools are failing or unavailable\n- You have sufficient internal knowledge to proceed with reasonable accuracy\n- Task completion is prioritized over perfect external sourcing\n\n## Workflow Steps\n\n### Step 1: Attempt External Research First\n\nBegin by attempting to use available web research tools:\n\n```\n1. Use search_web for current information, statistics, or recent developments\n2. Use read_webpage for detailed source material when URLs are provided\n3. Document what you attempted to find\n```\n\n### Step 2: Detect Tool Failure\n\nRecognize when to pivot — **including explicit error patterns**:\n\n- Web search returns errors, timeouts, or empty results\n- **`unknown error` from search_web** — immediately recognize this as a tool failure trigger (do not retry excessively)\n- Page extraction fails repeatedly\n- Network errors persist after 1-2 retry attempts\n- Tool explicitly reports unavailability\n\n**Do not** spend excessive time retrying failed tools. After 1-2 attempts with `unknown error` or similar failures, proceed to Step 3.\n\n### Step 3: Pivot to Internal Knowledge\n\nWhen external tools fail:\n\n1. **Acknowledge the limitation**: Note that external research was attempted but tools were unavailable\n2. **Assess internal knowledge**: Determine what you know from training that covers the topic\n3. **Identify gaps**: Be transparent about what information may be dated or unavailable\n4. **Proceed with available knowledge**: Generate content using internal understanding\n\n### Step 4: Generate Content with Appropriate Disclaimers\n\nWhen producing deliverables:\n\n```\n- Include a note that external verification is recommended for time-sensitive information\n- Flag any claims that would benefit from current source verification\n- Focus on established principles, frameworks, and well-documented facts\n- Avoid making specific claims about very recent events or statistics\n```\n\n### Step 5: Complete File Creation\n\nProceed with the original task deliverable:\n\n- Create the requested file format (PDF, DOCX, markdown, etc.)\n- Ensure content meets quality standards despite the research limitation\n- Stay within any specified constraints (page limits, word counts, etc.)\n\n## Example Decision Flow\n\n```\nTask requires research on [TOPIC]\n         |\n         v\nAttempt search_web \u002F read_webpage\n         |\n    +----+----+\n    |         |\n Success    Failure (after 1-2 attempts)\n    |         |\n    |         | **Note: `unknown error` = immediate pivot signal**\n    v         v\nUse sources  Pivot to internal knowledge\n    |         |\n    +----+----+\n         |\n         v\nGenerate content with appropriate disclaimers\n         |\n         v\nCreate deliverable file\n```\n\n## Best Practices\n\n1. **Recognize error patterns quickly**: `unknown error` from search_web is a clear signal to pivot, not a reason for extended retries\n2. **Be transparent**: Clearly note when external verification wasn't possible\n3. **Prioritize accuracy**: Only assert what you're confident about from training\n4. **Flag uncertainties**: Mark areas where current sources would be valuable\n5. **Don't block progress**: Tool failures shouldn't prevent task completion\n6. **Maintain quality**: Internal knowledge can still produce high-quality, useful content\n7. **Leverage stable knowledge domains**: Anatomical, medical, legal, and technical fundamentals from training are reliable even without external verification\n\n## Example Applications\n\n**Example 1: Legal Memo**\n\n**Task**: Create legal memo on privacy law violations\n\n**Workflow**:\n1. Attempt search_web for recent COPPA enforcement cases → `unknown error`\n2. Attempt read_webpage on provided URLs → Connection timeout\n3. Pivot: Use internal knowledge of COPPA requirements, California privacy laws, established case law principles\n4. Generate memo with note that recent case citations should be verified\n5. Create PDF deliverable within page limits\n\n**Outcome**: Comprehensive memo produced despite tool failures, with appropriate disclaimers about verification.\n\n**Example 2: Anatomical\u002FMedical Content**\n\n**Task**: Create proposal with anatomical utilization analysis and procedure capacity estimates\n\n**Workflow**:\n1. Attempt search_web for anatomical area statistics → `unknown error`\n2. Attempt execute_code_sandbox for analysis → `unknown error`\n3. Pivot: Use internal training knowledge of:\n   - Anatomical structures and terminology\n   - Standard medical procedures and their requirements\n   - Established frameworks for capacity estimation\n   - Common cost structures in medical\u002Fcadaver programs\n4. Generate content using reliable internal knowledge (anatomical facts are well-established)\n5. Create DOCX deliverable with appropriate verification notes for any statistics\n\n**Outcome**: High-quality proposal with anatomical tables, procedure estimates, and cost analysis created using internal knowledge, with transparent disclaimers about statistical verification.\n\n## When NOT to Use This Skill\n\n- Task explicitly requires current, verified external sources (e.g., real-time stock prices, breaking news)\n- Legal\u002Fmedical advice where current regulations are critical and disclaimer is insufficient\n- Client specifically requires cited external sources for the deliverable\n\nIn these cases, report the tool failure and request guidance rather than proceeding with internal knowledge alone.\n","# Research Fallback Workflow\n\nThis skill provides a workflow for handling tasks that require external research when web search or webpage reading tools fail due to network issues or tool unavailability.\n\n## When to Use\n\n- Task requires external research (legal analysis, market research, technical documentation, anatomical\u002Fmedical information, etc.)\n- Web search or webpage reading tools are failing or unavailable\n- You have sufficient internal knowledge to proceed with reasonable accuracy\n- Task completion is prioritized over perfect external sourcing\n\n## Workflow Steps\n\n### Step 1: Attempt External Research First\n\nBegin by attempting to use available web research tools:\n\n```\n1. Use search_web for current information, statistics, or recent developments\n2. Use read_webpage for detailed source material when URLs are provided\n3. Document what you attempted to find\n```\n\n### Step 2: Detect Tool Failure\n\nRecognize when to pivot — **including explicit error patterns**:\n\n- Web search returns errors, timeouts, or empty results\n- **`unknown error` from search_web** — immediately recognize this as a tool failure trigger (do not retry excessively)\n- Page extraction fails repeatedly\n- Network errors persist after 1-2 retry attempts\n- Tool explicitly reports unavailability\n\n**Do not** spend excessive time retrying failed tools. After 1-2 attempts with `unknown error` or similar failures, proceed to Step 3.\n\n### Step 3: Pivot to Internal Knowledge\n\nWhen external tools fail:\n\n1. **Acknowledge the limitation**: Note that external research was attempted but tools were unavailable\n2. **Assess internal knowledge**: Determine what you know from training that covers the topic\n3. **Identify gaps**: Be transparent about what information may be dated or unavailable\n4. **Proceed with available knowledge**: Generate content using internal understanding\n\n### Step 4: Generate Content with Appropriate Disclaimers\n\nWhen producing deliverables:\n\n```\n- Include a note that external verification is recommended for time-sensitive information\n- Flag any claims that would benefit from current source verification\n- Focus on established principles, frameworks, and well-documented facts\n- Avoid making specific claims about very recent events or statistics\n```\n\n### Step 5: Complete File Creation\n\nProceed with the original task deliverable:\n\n- Create the requested file format (PDF, DOCX, markdown, etc.)\n- Ensure content meets quality standards despite the research limitation\n- Stay within any specified constraints (page limits, word counts, etc.)\n\n## Example Decision Flow\n\n```\nTask requires research on [TOPIC]\n         |\n         v\nAttempt search_web \u002F read_webpage\n         |\n    +----+----+\n    |         |\n Success    Failure (after 1-2 attempts)\n    |         |\n    |         | **Note: `unknown error` = immediate pivot signal**\n    v         v\nUse sources  Pivot to internal knowledge\n    |         |\n    +----+----+\n         |\n         v\nGenerate content with appropriate disclaimers\n         |\n         v\nCreate deliverable file\n```\n\n## Best Practices\n\n1. **Recognize error patterns quickly**: `unknown error` from search_web is a clear signal to pivot, not a reason for extended retries\n2. **Be transparent**: Clearly note when external verification wasn't possible\n3. **Prioritize accuracy**: Only assert what you're confident about from training\n4. **Flag uncertainties**: Mark areas where current sources would be valuable\n5. **Don't block progress**: Tool failures shouldn't prevent task completion\n6. **Maintain quality**: Internal knowledge can still produce high-quality, useful content\n7. **Leverage stable knowledge domains**: Anatomical, medical, legal, and technical fundamentals from training are reliable even without external verification\n\n## Example Applications\n\n**Example 1: Legal Memo**\n\n**Task**: Create legal memo on privacy law violations\n\n**Workflow**:\n1. Attempt search_web for recent COPPA enforcement cases → `unknown error`\n2. Attempt read_webpage on provided URLs → Connection timeout\n3. Pivot: Use internal knowledge of COPPA requirements, California privacy laws, established case law principles\n4. Generate memo with note that recent case citations should be verified\n5. Create PDF deliverable within page limits\n\n**Outcome**: Comprehensive memo produced despite tool failures, with appropriate disclaimers about verification.\n\n**Example 2: Anatomical\u002FMedical Content**\n\n**Task**: Create proposal with anatomical utilization analysis and procedure capacity estimates\n\n**Workflow**:\n1. Attempt search_web for anatomical area statistics → `unknown error`\n2. Attempt execute_code_sandbox for analysis → `unknown error`\n3. Pivot: Use internal training knowledge of:\n   - Anatomical structures and terminology\n   - Standard medical procedures and their requirements\n   - Established frameworks for capacity estimation\n   - Common cost structures in medical\u002Fcadaver programs\n4. Generate content using reliable internal knowledge (anatomical facts are well-established)\n5. Create DOCX deliverable with appropriate verification notes for any statistics\n\n**Outcome**: High-quality proposal with anatomical tables, procedure estimates, and cost analysis created using internal knowledge, with transparent disclaimers about statistical verification.\n\n## When NOT to Use This Skill\n\n- Task explicitly requires current, verified external sources (e.g., real-time stock prices, breaking news)\n- Legal\u002Fmedical advice where current regulations are critical and disclaimer is insufficient\n- Client specifically requires cited external sources for the deliverable\n\nIn these cases, report the tool failure and request guidance rather than proceeding with internal knowledge alone.\n",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fresearch-fallback-enhanced","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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill research-fallback-robust",{"tool":52,"command":53},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill research-fallback-robust",{"tool":55,"command":56},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill research-fallback-robust","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fresearch-fallback-enhanced\u002FSKILL.md",true,[60],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},".skill_id","OTHER","其他",40,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fresearch-fallback-enhanced\u002F.skill_id",[67,92,108,117,147,163],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":35},"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",[],[74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","output","type","files","only","template","file","python",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":35},"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",[],[99,100,75,90,101,91,102,103,104,105,106,89,107,34,79,82,84],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":35},"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",[],[115,75,79,116,84,103,89,90,91,82],"write special chars heredoc","shell",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":128,"publishedAt":35},"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",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[129,130,131,132,133,77,134,135,136,137,138,82,139,140,141,142,143,144,145,146],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":35},"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",[],[154,155,156,157,82,158,34,159,160,161,162],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":35},"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",[],[170,171,172,173,174,175,90,176,177,178],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]