resources/skills/java-lsp-tools/SKILL.md
Compiler-accurate Java symbol navigation via the Java Language Server. Use lsp_java_findSymbol for Java identifiers and lsp_java_getFileStructure for known Java files; prefer them over generic search only for symbol/file-outline navigation.
npx skillsauth add microsoft/vscode-java-dependency java-lsp-toolsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
lsp_java_findSymbolSearch for Java symbol definitions (classes, methods, fields) by name across the workspace. Supports partial matching.
{ query, limit? } — limit defaults to 20, max 50{ results: [{ name, kind, container?, location, range }], total } (~60 tokens); range is L start-endgrep_search, file_search, semantic_search, or search_subagent when looking for where a Java class/method/field is defined by identifierlsp_java_getFileStructureGet hierarchical outline of a Java file (classes, methods, fields) with line ranges.
{ uri } — workspace-relative path. Must be a known path from prior tool results or user input — do not guessL start-end ranges (~100 tokens)read_file when you need to choose a precise line range in a known Java file| Task | Use | Not |
|---|---|---|
| Find class/method/field definition | lsp_java_findSymbol | grep_search |
| See known Java file outline before reading | lsp_java_getFileStructure | read_file full file |
| Search non-Java files (xml, gradle) | grep_search | lsp tools |
| Search string literals or comments | grep_search | lsp tools |
| Explore broad concepts without identifiers | semantic_search or search_subagent | lsp tools |
findSymbol → getFileStructure → read_file (specific lines only)
If findSymbol returns relevant symbols, move forward to getFileStructure or read_file; do not call findSymbol again with the same or similar identifier.
findSymbol returns empty → it already retried internally with a normalized identifier, so do not re-issue the same search. If the result says indexing is in progress, retry once after a short pause; otherwise fall back to grep_searchfileNotFound) → use findSymbol to discover the correct path first; do not guess pathsgrep_search + read_file, don't retry more than oncetools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.