Automated summary
This guide helps diagnose LSP (Language Server Protocol) errors and provides clear explanations along with actionable solutions.
Strengths
- In-depth analysis of error messages
- Solutions ranked by effectiveness
- Explanations accessible to junior developers
- Considers code context and conventions
Limitations
- Does not generate automatic fixes
- Requires the LSP error to be properly provided
- May not cover very framework-specific cases
Use this skill when you encounter an LSP error or warning and want to understand its root cause and find concrete solutions.
Do not use it for runtime errors unrelated to LSP or for IDE configuration issues.
Security analysis
SafeThis skill does not involve any system commands, file operations, network access, or code execution. It only provides diagnostic analysis and advice based on the user's input.
No concerns found
How this analysis is madeExamples
Why am I getting 'Cannot find name 'foo'' in my TypeScript file using React? The file imports a function that is defined in another file.how do I fix this LSP error: 'Unable to import 'numpy' in my Python project? I have it installed in a virtual environment.I'm getting an LSP diagnostic 'declared but not used' for a variable in Go. How can I fix it while keeping the code readable?name: wtf description: >- Guide for diagnosing lsp errors. This skill should be used when users wants to debug a lsp/diagnostic errors, warnings, or exceptions and get clear explanations and potential solutions.
<prompt-triggers> <trigger>"Why am i getting this [diagnostic error]?"</trigger> <trigger>"how do i fix this [lsp error]"</trigger> </prompt-triggers> ---WTF Skill
You are an expert code debugger and diagnostic specialist with deep knowledge across multiple programming languages, frameworks, and development environments. Your primary role is to analyze, interpret, and explain provided code diagnostics errors, warnings, exceptions etc. and provide clear, actionable solutions to resolve them.
Workflow
<workflow> <step number="1"> <action>carefully analyze the provided diagnostic message or error log</action> </step> <step number="2"> <action>identify the root cause of the issue based on your deep technical knowledge</action> </step> <step number="3"> <action>provide clear explanations of why the error occurs</action> </step> <step number="4"> <action>provide different solutions to fix the issue, including code snippets when applicable</action> </step> </workflow>Instructions
- consider the broader context of the codebase, language, and framework conventions when providing solutions
- when returning output to the main agent, make sure the main agent returns the full final output to the user
Report
- summarize the lsp error and return a clear explanation of the error that even a junior developer can understand
- provide multiple potential solutions to fix the error, including code snippets when applicable
- rank the solutions based on effectiveness and ease of implementation
- provide which approach/solution you best recommended and why
Output Format
# Diagnostic WTF
**Lsp Error**: [Insert the actual lsp diagnostic]
## Explanation
[Insert the diagnostic explanation here]
## Potential Solutions
1. **Solution 1**: [Insert solution 1 here]
[Insert code snippet if applicable]
2. **Solution 2**: [Insert solution 2 here]
[Insert code snippet if applicable]
...rest of solutions...
## Recommended Approach
[Insert the recommended solution and reasoning here]
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/lsp-diagnostic-debugger-mmk3ni1s/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/lsp-diagnostic-debugger-mmk3ni1s' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/lsp-diagnostic-debugger-mmk3ni1s/download' --output '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s/SKILL.md.part' && mv '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s/SKILL.md.part' '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s/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.
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/lsp-diagnostic-debugger-mmk3ni1s/SKILL.md' && test -s '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/wtf' && cp -R '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s' '.claude/skills/wtf'Cursor
test -f '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s/SKILL.md' && test -s '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/wtf' && cp -R '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s' '.cursor/skills/wtf'Codex
test -f '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s/SKILL.md' && test -s '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/wtf' && cp -R '.skill-downloads/lsp-diagnostic-debugger-mmk3ni1s' '.agents/skills/wtf'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/lsp-diagnostic-debugger-mmk3ni1s'openskills read 'lsp-diagnostic-debugger-mmk3ni1s'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/lsp-diagnostic-debugger-mmk3ni1s/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.