[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XCBSK7Y7Y2VMHXWJ136RW9":3,"skill-same:01M6XCBSK7Y7Y2VMHXWJ136RW9":67},{"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":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":60},"01M6XCBSK7Y7Y2VMHXWJ136RW9","typescript-typecheck-fallback",null,"Reliably run TypeScript type-checking (npx tsc --noEmit) by using shell_agent as a fallback when run_shell fails due to environment or timeout issues.","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\u002Fshowcase\u002Fskills\u002Ftypescript-typecheck-fallback\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36],"typescript","fallback","typecheck","typescript typecheck fallback","run","issues","shell","environment","npx","as","type","timeout","type-checking","when","2026-11-10 10:12:30",false,"---\nname: typescript-typecheck-fallback\ndescription: Reliably run TypeScript type-checking (npx tsc --noEmit) by using shell_agent as a fallback when run_shell fails due to environment or timeout issues.\n---\n\n# TypeScript Type-Check with shell_agent Fallback\n\nWhen verifying TypeScript compilation as part of a build or validation workflow, `run_shell` may fail with unknown errors due to shell environment issues, missing PATH entries, timeout constraints, or other transient problems. This skill describes a two-step pattern: attempt the check with `run_shell` first, then fall back to `shell_agent` if it fails.\n\n---\n\n## When to Use\n\n- After creating or modifying TypeScript source files and you need to confirm there are no type errors.\n- As part of a CI-like verification step inside an autonomous workflow.\n- Any time `run_shell` returns an unexpected or unclear error for a `tsc` invocation.\n\n---\n\n## Step-by-Step Pattern\n\n### Step 1 — Attempt with `run_shell` (fast path)\n\nTry the direct command first. This is fast and gives immediate output when the environment is well-configured.\n\n```\nrun_shell: npx tsc --noEmit\n```\n\n**Evaluate the result:**\n- ✅ **Exit code 0, no errors** → Type-check passed. Done.\n- ❌ **Exit code non-zero with TypeScript diagnostics** → Real type errors exist; surface them and fix.\n- ⚠️ **Unknown error, timeout, or no useful output** → Proceed to Step 2.\n\n---\n\n### Step 2 — Fall back to `shell_agent` (reliable path)\n\nWhen `run_shell` fails in an ambiguous or environmental way, delegate to `shell_agent` with a natural-language task. `shell_agent` can autonomously:\n- Locate the correct `npx`\u002F`tsc` binary\n- Retry on transient failures\n- Navigate PATH or permission issues\n- Return a structured summary of any type errors\n\n**Task string to pass to `shell_agent`:**\n\n```\nRun `npx tsc --noEmit` in the project root and report all TypeScript type errors found. If there are no errors, confirm the compilation succeeded. If tsc is not available, attempt to install TypeScript locally with `npm install --save-dev typescript` first.\n```\n\n**Evaluate the result:**\n- ✅ **\"No errors found\" \u002F exit 0** → Type-check passed.\n- ❌ **Type errors listed** → Collect and fix the reported diagnostics, then re-run.\n- ⚠️ **`tsconfig.json` missing** → Ensure the file exists in the project root before re-running.\n\n---\n\n## Decision Flowchart\n\n```\nrun_shell(\"npx tsc --noEmit\")\n        │\n        ├─ success (exit 0) ──────────────────► ✅ PASS\n        │\n        ├─ type errors reported ──────────────► ❌ Fix errors, retry\n        │\n        └─ unknown\u002Fenv error ─────────────────► shell_agent(natural-language task)\n                                                        │\n                                                        ├─ success ───► ✅ PASS\n                                                        └─ errors  ───► ❌ Fix & retry\n```\n\n---\n\n## Example Implementation\n\n```python\n# Pseudo-code for an autonomous agent loop\n\nresult = run_shell(\"npx tsc --noEmit\", timeout=60)\n\nif result.exit_code == 0:\n    print(\"TypeScript check passed.\")\n\nelif result.exit_code != 0 and result.stderr contains \"TS\\d+\":\n    # Real TypeScript diagnostics — surface and fix them\n    raise TypeScriptError(result.stderr)\n\nelse:\n    # Ambiguous failure — delegate to shell_agent\n    shell_agent(\n        task=\"Run `npx tsc --noEmit` in the project root and report all TypeScript \"\n             \"type errors found. If there are no errors, confirm compilation succeeded. \"\n             \"If tsc is not available, install it first with `npm install --save-dev typescript`.\"\n    )\n```\n\n---\n\n## Tips\n\n- **Always have a `tsconfig.json`**: `tsc --noEmit` requires a valid config. If none exists, generate one first with `npx tsc --init`.\n- **Set a reasonable timeout**: TypeScript compilation on large projects can take 30–120 seconds. Give `run_shell` at least `timeout=90`.\n- **Scope to changed files when possible**: Use `--project tsconfig.json` or a path glob to limit what tsc checks if only a subset of files changed.\n- **Prefer `shell_agent` for first-time setups**: If the project environment is freshly created and dependencies may not be fully installed, start with `shell_agent` directly to avoid a predictable `run_shell` failure.\n\n---\n\n## Generalizing Beyond TypeScript\n\nThis same fallback pattern applies to any build\u002Flint\u002Ftype-check command that may be sensitive to shell environment:\n\n| Tool | Primary `run_shell` command | `shell_agent` fallback task |\n|---|---|---|\n| TypeScript | `npx tsc --noEmit` | \"Run npx tsc --noEmit and report errors\" |\n| ESLint | `npx eslint src\u002F` | \"Run npx eslint on the src directory and report lint errors\" |\n| Python mypy | `python -m mypy src\u002F` | \"Run mypy on the src directory and report type errors\" |\n| Go build | `go build .\u002F...` | \"Run go build and report compilation errors\" |\n\nThe core principle: **`run_shell` for speed; `shell_agent` for resilience.**","# TypeScript Type-Check with shell_agent Fallback\n\nWhen verifying TypeScript compilation as part of a build or validation workflow, `run_shell` may fail with unknown errors due to shell environment issues, missing PATH entries, timeout constraints, or other transient problems. This skill describes a two-step pattern: attempt the check with `run_shell` first, then fall back to `shell_agent` if it fails.\n\n---\n\n## When to Use\n\n- After creating or modifying TypeScript source files and you need to confirm there are no type errors.\n- As part of a CI-like verification step inside an autonomous workflow.\n- Any time `run_shell` returns an unexpected or unclear error for a `tsc` invocation.\n\n---\n\n## Step-by-Step Pattern\n\n### Step 1 — Attempt with `run_shell` (fast path)\n\nTry the direct command first. This is fast and gives immediate output when the environment is well-configured.\n\n```\nrun_shell: npx tsc --noEmit\n```\n\n**Evaluate the result:**\n- ✅ **Exit code 0, no errors** → Type-check passed. Done.\n- ❌ **Exit code non-zero with TypeScript diagnostics** → Real type errors exist; surface them and fix.\n- ⚠️ **Unknown error, timeout, or no useful output** → Proceed to Step 2.\n\n---\n\n### Step 2 — Fall back to `shell_agent` (reliable path)\n\nWhen `run_shell` fails in an ambiguous or environmental way, delegate to `shell_agent` with a natural-language task. `shell_agent` can autonomously:\n- Locate the correct `npx`\u002F`tsc` binary\n- Retry on transient failures\n- Navigate PATH or permission issues\n- Return a structured summary of any type errors\n\n**Task string to pass to `shell_agent`:**\n\n```\nRun `npx tsc --noEmit` in the project root and report all TypeScript type errors found. If there are no errors, confirm the compilation succeeded. If tsc is not available, attempt to install TypeScript locally with `npm install --save-dev typescript` first.\n```\n\n**Evaluate the result:**\n- ✅ **\"No errors found\" \u002F exit 0** → Type-check passed.\n- ❌ **Type errors listed** → Collect and fix the reported diagnostics, then re-run.\n- ⚠️ **`tsconfig.json` missing** → Ensure the file exists in the project root before re-running.\n\n---\n\n## Decision Flowchart\n\n```\nrun_shell(\"npx tsc --noEmit\")\n        │\n        ├─ success (exit 0) ──────────────────► ✅ PASS\n        │\n        ├─ type errors reported ──────────────► ❌ Fix errors, retry\n        │\n        └─ unknown\u002Fenv error ─────────────────► shell_agent(natural-language task)\n                                                        │\n                                                        ├─ success ───► ✅ PASS\n                                                        └─ errors  ───► ❌ Fix & retry\n```\n\n---\n\n## Example Implementation\n\n```python\n# Pseudo-code for an autonomous agent loop\n\nresult = run_shell(\"npx tsc --noEmit\", timeout=60)\n\nif result.exit_code == 0:\n    print(\"TypeScript check passed.\")\n\nelif result.exit_code != 0 and result.stderr contains \"TS\\d+\":\n    # Real TypeScript diagnostics — surface and fix them\n    raise TypeScriptError(result.stderr)\n\nelse:\n    # Ambiguous failure — delegate to shell_agent\n    shell_agent(\n        task=\"Run `npx tsc --noEmit` in the project root and report all TypeScript \"\n             \"type errors found. If there are no errors, confirm compilation succeeded. \"\n             \"If tsc is not available, install it first with `npm install --save-dev typescript`.\"\n    )\n```\n\n---\n\n## Tips\n\n- **Always have a `tsconfig.json`**: `tsc --noEmit` requires a valid config. If none exists, generate one first with `npx tsc --init`.\n- **Set a reasonable timeout**: TypeScript compilation on large projects can take 30–120 seconds. Give `run_shell` at least `timeout=90`.\n- **Scope to changed files when possible**: Use `--project tsconfig.json` or a path glob to limit what tsc checks if only a subset of files changed.\n- **Prefer `shell_agent` for first-time setups**: If the project environment is freshly created and dependencies may not be fully installed, start with `shell_agent` directly to avoid a predictable `run_shell` failure.\n\n---\n\n## Generalizing Beyond TypeScript\n\nThis same fallback pattern applies to any build\u002Flint\u002Ftype-check command that may be sensitive to shell environment:\n\n| Tool | Primary `run_shell` command | `shell_agent` fallback task |\n|---|---|---|\n| TypeScript | `npx tsc --noEmit` | \"Run npx tsc --noEmit and report errors\" |\n| ESLint | `npx eslint src\u002F` | \"Run npx eslint on the src directory and report lint errors\" |\n| Python mypy | `python -m mypy src\u002F` | \"Run mypy on the src directory and report type errors\" |\n| Go build | `go build .\u002F...` | \"Run go build and report compilation errors\" |\n\nThe core principle: **`run_shell` for speed; `shell_agent` for resilience.**",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","showcase\u002Fskills\u002Ftypescript-typecheck-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":58,"zipAvailable":59},[50,52,55],{"tool":31,"command":51},"npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill typescript-typecheck-fallback",{"tool":53,"command":54},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill typescript-typecheck-fallback",{"tool":56,"command":57},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill typescript-typecheck-fallback","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Ftypescript-typecheck-fallback\u002FSKILL.md",true,[61],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},".skill_id","OTHER","其他",43,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Ftypescript-typecheck-fallback\u002F.skill_id",[68,90,107,115,145,161],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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",[],[75,76,77,23,78,79,80,35,81,82,83,84,33,85,86,87,88,89],"check","write","write special chars ts check","filters","characters","Existing","for","errors","script","output","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":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",[],[97,98,76,88,99,89,100,101,102,103,104,87,105,106,79,81,83],"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":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",[],[114,76,79,29,83,101,87,88,89,81],"write special chars heredoc",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":126,"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",[121],{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[127,128,129,130,131,23,132,133,134,135,136,81,137,138,139,140,141,142,143,144],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"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",[],[152,153,154,155,81,156,106,157,158,159,160],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"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",[],[168,169,170,171,172,173,88,28,174,175],"directory","verify directory structure","structure","verify","access","first","diagnose","file access"]