java-lsp-tools Skill
Compiler-accurate Java symbol navigation via the Java Language Server. Use lspjavafindSymbol for Java identifiers and lspjavagetFileStructure for known Java files; prefer them over generic search only for symbol/file-outline navigation. Published by microsoft in vscode-java-dependency.
Decision snapshot
Is this a fit?
Research, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is java-lsp-tools Skill?
Compiler-accurate Java symbol navigation via the Java Language Server. Use lspjavafindSymbol for Java identifiers and lspjavagetFileStructure for known Java files; prefer them over generic search only for symbol/file-outline navigation. Published by microsoft in vscode-java-dependency. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Research
- Research use cases
Declared skill metadata
- Source file: resources/skills/java-lsp-tools/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use java-lsp-tools Skill
- Use it for research.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-java-dependency
- Skill file: resources/skills/java-lsp-tools/SKILL.md
What it does
Compiler-accurate Java symbol navigation via the Java Language Server. Use lspjavafindSymbol for Java identifiers and lspjavagetFileStructure for known Java files; prefer them over generic search only for symbol/file-outline navigation.
Skill instructions
Java LSP Tools Two compiler-accurate tools backed by the Java Language Server (jdtls). They return structured JSON that is easier to interpret than generic search results for Java symbol navigation. Tools lspjavafindSymbol Search for Java symbol definitions (classes, methods, fields) by name across the workspace. Supports partial matching. - Input: { query, limit? } — limit defaults to 20, max 50 - Output: { results: [{ name, kind, container?, file, startLine, endLine, readFileInput, range }], total }; readFileInput is { filePath, offset, limit } for readfile, and file can be passed to lspjavagetFileStructure - Use instead of grepsearch, filesearch, semanticsearch, or searchsubagent when looking for where a Java class/method/field is defined by identifier - When source is needed for a returned symbol, use its readFileInput directly lspjavagetFileStructure Get hierarchical outline of a Java file (classes, methods, fields) with line ranges. - Input: { uri, limit? } — workspace-relative p
Verified compatibility and discovery
Frequently asked questions
What is java-lsp-tools?
java-lsp-tools is a open-source AI agent skill with Copy skill directory. Compiler-accurate Java symbol navigation via the Java Language Server. Use lspjavafindSymbol for Java identifiers and lspjavagetFileStructure for known Java files; prefer them over generic search only for.
Who is java-lsp-tools best for?
java-lsp-tools is best for reusing agent instructions, scripts, and references, research workflows.
How do I install java-lsp-tools?
Install or run java-lsp-tools using Copy skill directory. Check java-lsp-tools for the latest setup command.
Is java-lsp-tools actively maintained?
java-lsp-tools may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
