Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/typescript-check
TypeScript type checking via tsc --noEmit with actionable error output.
Passed 12 of 16 test cases with the skill, and 7 of 16 without it.
and 6 more in the full report
8 fixed8 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact command is used in Step 1 to verify whether a TypeScript configuration file exists in the root or immediate subdirectories?
| Checked | Without skill | With skill |
|---|---|---|
| The response provides the command ls tsconfig.json 2>/dev/null || ls */tsconfig.json 2>/dev/null. | Missed | Passed |
The instructions your model reads when the skill loads.
Read-only type validation. Follow repository instructions and package scripts; preserve project compiler settings. Do not fix code, change configuration, or install dependencies for a check-only request.
tsconfig.json, including src/, app/, and packages/. In a monorepo, use the package affected by the task or the repository's aggregate check. Ask only when the target cannot be inferred. If no config exists, report the missing configuration and stop.npx tsc --noEmit 2>&1, or npx tsc --noEmit --project path/to/tsconfig.json 2>&1 for a selected config. Capture output and exit code. Zero means pass; nonzero may mean type errors or a tool/configuration failure—report which.file:line:column, TS####, and the message. Retain complete logs; show useful failure details instead of all successful output.npm install typescript --save-dev within dependency setup.node --version; when Node/npm and local TypeScript exist, use npm exec tsc -- --noEmit. Otherwise report the missing toolchain.--skipLibCheck: skips declaration-file checking; use only when configured or requested, not to hide failures.--strict: adds strict checks; enable only when requested or configured.--incremental: may write build-info cache files; enable only when permitted, not for a strictly read-only run.--project; do not claim equivalent coverage from a narrower check.When running the full JavaScript/TypeScript check sequence, lint first, type-check next, then run tests with vitest-runner or the repository test command.
test cases passed, vs 7 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.