Automated summary
This skill fixes TypeScript errors by identifying root causes, applying minimal corrections, and verifying compilation succeeds.
Strengths
- Automated error detection via the TypeScript compiler
- Encourages precise fixes and avoids workarounds like `any`
- Iterative verification process until zero errors
- Guides toward specific types and typed assertions
Limitations
- Depends on TypeScript configuration; errors may be hidden if config is too lenient
- Cannot automatically fix complex structural mismatches; requires human understanding
- Does not cover runtime errors that static typing does not catch
When you need to resolve TypeScript compilation errors in an existing codebase.
When the issue is a logic bug rather than a type error, or when you need to design new complex types from scratch.
Security analysis
SafeThe skill uses only safe commands: 'npx tsc --noEmit' for type checking, along with Read and Edit tools. There is no destructive or exfiltrating behavior, no network requests beyond npm if tsc is not installed, and no execution of arbitrary code.
No concerns found
How this analysis is madeExamples
Run `npx tsc --noEmit` to check for TypeScript errors, then fix each error one by one with minimal changes. Continue until no errors remain.Fix the TypeScript errors in the file src/services/user.ts. Use proper type annotations instead of `any` or `@ts-ignore`.name: fix-types description: Fix TypeScript errors user-invocable: true allowed-tools: Bash(npx tsc *), Read, Edit
Fix TypeScript Errors
Check for Errors
npx tsc --noEmit
Instructions
Review the TypeScript errors above and fix each one:
- Identify the root cause - Understand why the type error is occurring
- Fix with minimal changes - Don't over-engineer; make the smallest change that correctly resolves the issue
- Verify the fix compiles - After fixing, re-run the type check
Guidelines
- Prefer fixing the actual type issue over using
anyor@ts-ignore - If a type assertion is needed, use
aswith a specific type rather thanas any - Consider whether the error reveals a real bug vs. a type definition gap
- Update interfaces/types if the shape has legitimately changed
Verification
After fixing all errors, run the type check again to confirm:
npx tsc --noEmit
Continue until there are no type errors remaining.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/fix-typescript-errors-mm5t8bot/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/fix-typescript-errors-mm5t8bot' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/fix-typescript-errors-mm5t8bot/download' --output '.skill-downloads/fix-typescript-errors-mm5t8bot/SKILL.md.part' && mv '.skill-downloads/fix-typescript-errors-mm5t8bot/SKILL.md.part' '.skill-downloads/fix-typescript-errors-mm5t8bot/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash(npx tsc *), Read, Edit
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/fix-typescript-errors-mm5t8bot/SKILL.md' && test -s '.skill-downloads/fix-typescript-errors-mm5t8bot/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/fix-types' && cp -R '.skill-downloads/fix-typescript-errors-mm5t8bot' '.claude/skills/fix-types'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/fix-typescript-errors-mm5t8bot'openskills read 'fix-typescript-errors-mm5t8bot'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/fix-typescript-errors-mm5t8bot/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.