Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Navigate code with IDE features and run proactive LSP diagnostics on files/folders/batches.
Install Pi Lens Lsp Navigation
$ npx skills add apmantza/pi-lens --skill pi-lens-lsp-navigation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install apmantza/pi-lens pi-lens-lsp-navigation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/apmantza/pi-lens.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pi-lens-lsp-navigation .claude/skills/pi-lens-lsp-navigation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pi-lens-lsp-navigation" agent skill from https://github.com/apmantza/pi-lens/tree/master/skills/pi-lens-lsp-navigation into .claude/skills/pi-lens-lsp-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pi-lens-lsp-navigation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/apmantza/pi-lens/tree/master/skills/pi-lens-lsp-navigationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add apmantza/pi-lens --skill pi-lens-lsp-navigation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install apmantza/pi-lens pi-lens-lsp-navigation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/apmantza/pi-lens.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pi-lens-lsp-navigation .agents/skills/pi-lens-lsp-navigation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pi-lens-lsp-navigation" agent skill from https://github.com/apmantza/pi-lens/tree/master/skills/pi-lens-lsp-navigation into .agents/skills/pi-lens-lsp-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pi-lens-lsp-navigation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add apmantza/pi-lens --skill pi-lens-lsp-navigation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install apmantza/pi-lens pi-lens-lsp-navigation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/apmantza/pi-lens.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pi-lens-lsp-navigation .cursor/skills/pi-lens-lsp-navigation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pi-lens-lsp-navigation" agent skill from https://github.com/apmantza/pi-lens/tree/master/skills/pi-lens-lsp-navigation into .cursor/skills/pi-lens-lsp-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pi-lens-lsp-navigation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/apmantza/pi-lens.git --path skills/pi-lens-lsp-navigation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add apmantza/pi-lens --skill pi-lens-lsp-navigation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install apmantza/pi-lens pi-lens-lsp-navigation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/apmantza/pi-lens.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pi-lens-lsp-navigation .gemini/skills/pi-lens-lsp-navigation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pi-lens-lsp-navigation" agent skill from https://github.com/apmantza/pi-lens/tree/master/skills/pi-lens-lsp-navigation into .gemini/skills/pi-lens-lsp-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pi-lens-lsp-navigation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install apmantza/pi-lens pi-lens-lsp-navigationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add apmantza/pi-lens --skill pi-lens-lsp-navigation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/apmantza/pi-lens.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pi-lens-lsp-navigation .github/skills/pi-lens-lsp-navigation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pi-lens-lsp-navigation" agent skill from https://github.com/apmantza/pi-lens/tree/master/skills/pi-lens-lsp-navigation into .github/skills/pi-lens-lsp-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pi-lens-lsp-navigation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add apmantza/pi-lens --skill pi-lens-lsp-navigation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install apmantza/pi-lens pi-lens-lsp-navigation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/apmantza/pi-lens.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pi-lens-lsp-navigation .opencode/skills/pi-lens-lsp-navigation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pi-lens-lsp-navigation" agent skill from https://github.com/apmantza/pi-lens/tree/master/skills/pi-lens-lsp-navigation into .opencode/skills/pi-lens-lsp-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pi-lens-lsp-navigation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pi-lens-lsp-navigation- GitHub stars
- 466
- Token cost
- ~1.6k tokens
- SKILL.md length
- 669 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Navigate code with IDE features and run proactive LSP diagnostics on files/folders/batches.
- Development work in your project
- SKILL.md covers Aggregate-tool hosts, Diagnostics, Navigation (Code Intelligence) and Call Hierarchy Pattern, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pi Lens Lsp Navigation is an agent skill from apmantza/pi-lens. Navigate code with IDE features and run proactive LSP diagnostics on files/folders/batches. Use as PRIMARY for code intelligence and type/error checks.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: Real-time code feedback for pi — LSP, linters, formatters, structural analysis. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/pi-lens-lsp-navigation”
What it can do on your machine
Read from SKILL.md and the folder at commit db92612. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pi Lens Lsp Navigation loads about 1.6k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 669 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from apmantza/pi-lens at commit db92612, republished under its MIT licence (© apmantza). 669 words, ~1,608 tokens.
Download SKILL.mdSave it as
.claude/skills/pi-lens-lsp-navigation/SKILL.md (or your agent's skills folder).- name
- pi-lens-lsp-navigation
- description
- Navigate code with IDE features and run proactive LSP diagnostics on files/folders/batches. Use as PRIMARY for code intelligence and type/error checks.
LSP Navigation and Diagnostics
Use lsp_navigation as PRIMARY for code intelligence. Use lens_diagnostics with source=lsp as PRIMARY for proactive type/error checks. Do NOT use grep/glob/ast-grep first for code intelligence.
Aggregate-tool hosts
Some hosts expose pi-lens through a single aggregate tool — lens(action=...) — instead of registering the standalone names below. On those hosts:
- Proactive checks:
lens({ action: "lsp_diagnostics", ... })— same parameters as the table below; the cached-report entry point maps tolens({ action: "diagnostics", ... }). - If
lsp_navigationis not among the aggregate's actions, do not call the standalone name: use the host's structural search funnel (symbol_search→module_report→read_symbol) or theast-grepCLI for navigation instead.
Diagnostics
Use lens_diagnostics with source=lsp before builds/tests or after touching several files:
| Need | Tool call |
|---|---|
| Check one file | lens_diagnostics({ source: "lsp", scope: "paths", paths: ["src/file.ts"] }) |
| Check a folder | lens_diagnostics({ source: "lsp", scope: "workspace", path: "src/", severity: "error" }) |
| Check exact touched files | lens_diagnostics({ source: "lsp", scope: "paths", paths: ["src/a.ts", "src/b.ts"] }) |
| Slow server (Rust, Java) | lens_diagnostics({ source: "lsp", scope: "paths", paths: files, waitMs: 2000 }) |
| Include warnings | lens_diagnostics({ source: "lsp", scope: "paths", paths: files, severity: "all" }) |
Prefer explicit paths batches after multi-file edits — bounded concurrency, no unrelated directory noise.
Parameter reference
lens_diagnostics accepts source: "session" | "lsp" and scope: "paths" | "workspace". Use mode: "delta" for the current turn, "all" for the cache-only session view, or "full" for an active scan. path selects one file or directory; paths filters a batch. severity is "error", "warning", or "all"; serverScope is "primary" or "all".
For mode: "full", refreshRunners: "cached" | "cheap" | "all" | "none" (or false/true) controls project analyzers. The first three string modes can launch a fresh heavyweight analyzer pass, bounded by the slowest runner's roughly 180-second ceiling; none disables it. maxProjectFiles limits cheap project runners, maxLspFiles limits the LSP sweep, and includeGenerated: true includes generated-name paths. These three limits apply to full scans. concurrency and waitMs tune LSP batches.
Show full SKILL.md (366 more words)Show less
Navigation (Code Intelligence)
| Question | Operation | Parameters |
|---|---|---|
| Where is this defined? | definition | path, line, character |
| Where is this symbol's type defined? | typeDefinition | path, line, character |
| Where is this declared (vs defined)? | declaration | path, line, character |
| Find all usages | references | path, line, character |
| What type is this? | hover | path, line, character |
| Call signature | signatureHelp | path, line, character (at arg position) |
| Symbols in this file | documentSymbol | path |
| Find symbol across project | workspaceSymbol | query + path (strongly recommended) |
| Quick fixes available | codeAction | path, line, character, endLine, endCharacter |
| Rename symbol safely | rename | path, line, character, newName |
| Who implements this? | implementation | path, line, character |
| Who calls this function? | prepareCallHierarchy → incomingCalls | path, line, character |
| What does this call? | prepareCallHierarchy → outgoingCalls | path, line, character |
| What commands does the server offer? | capabilities | (optional path) — lists advertised commands |
| Run a server command (e.g. organize imports) | executeCommand | command (+ commandArguments); dry-run unless apply:true |
The operation values are definition, typeDefinition, declaration, references, hover, signatureHelp, documentSymbol, findSymbol, workspaceSymbol, codeAction, rename, rename_file, implementation, prepareCallHierarchy, incomingCalls, outgoingCalls, executeCommand, workspaceDiagnostics, and capabilities.
For findSymbol, pass query; optionally narrow with kinds, exactMatch, topLevelOnly, and maxResults. rename_file uses newFilePath. symbol resolves a character automatically; character: -1 requests automatic resolution, and symbol#N selects a numbered symbol when the result lists one. callHierarchyItem is the object returned by prepareCallHierarchy and is required by the incoming/outgoing follow-up calls.
Call Hierarchy Pattern
// Step 1
lsp_navigation(operation="prepareCallHierarchy", path="src/api.ts", line=42, character=10)
// → returns callHierarchyItem
// Step 2
lsp_navigation(operation="incomingCalls", callHierarchyItem=<item from step 1>)
lsp_navigation(operation="outgoingCalls", callHierarchyItem=<item from step 1>)Operational Notes
definitionreturns nothing? The file may not be open/indexed yet. Read it first, then retry.workspaceSymbolempty? Always passpath. Unscoped queries are best-effort and frequently return nothing. If TypeScript returns "No Project", open the scoped file first.references— query from the definition site for full cross-file coverage; usage-site queries can be partial.signatureHelp— only valid at call-site argument positions; declaration positions return empty.workspaceDiagnostics— tracked push snapshot only, not an active check. Uselens_diagnosticswithsource=lspwhen you need fresh results.codeAction— distinguishquickfixfrom generic refactors ("Move to new file"). Generic refactors are not error fixes.prepareCallHierarchy— server-capability dependent; if unsupported, skip incoming/outgoing calls.
When NOT to Use LSP Navigation
| Task | Use Instead |
|---|---|
Find patterns (console.log) | ast_grep_search |
| Find text / TODOs | grep |
| Find files by name | glob |
| Read file content | read |
Golden Rule
Code intelligence → lsp_navigation first. Type/error validation → lens_diagnostics source=lsp first. Text/pattern search → grep/ast-grep.
© apmantza, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/pi-lens-lsp-navigation of apmantza/pi-lens.
Open the folder on GitHubat commit db92612
Compare with similar skills
Pi Lens Lsp Navigation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pi Lens Lsp Navigation this skillapmantza/pi-lens | 466 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from apmantza/pi-lens
Pi Lens Ast Grep
apmantza/pi-lens
A skill your agent uses when searching or replacing code patterns - use ast-grep instead of text search for semantic accuracy
Pi Lens Write Ast Grep Rule
apmantza/pi-lens
A skill your agent uses when writing a new pi-lens ast-grep rule YAML file — covers schema, drop path, gotchas, and NAPI runner constraints
Pi Lens Write Tree Sitter Rule
apmantza/pi-lens
A skill your agent uses when writing a new pi-lens tree-sitter query rule YAML file — covers schema, S-expression syntax, capture names, predicates, and gotchas
Release QA
apmantza/pi-lens
Run the pi-lens release-readiness QA pass — witness the feature × modality matrix against a real pi, count coverage, and issue a ship / ship-with-caveats / don't-ship / blocked line.
Retro
apmantza/pi-lens
Run the pi-lens retrospective — turn a session, an incident, or a merged bug fix into environment changes (checks, hooks, contract lines, deletions), classified mechanical-vs-judgement, each with…
Related
Categories
Questions about Pi Lens Lsp Navigation
What does Pi Lens Lsp Navigation do?
Navigate code with IDE features and run proactive LSP diagnostics on files/folders/batches. Pi Lens Lsp Navigation is an agent skill from apmantza/pi-lens. Navigate code with IDE features and run proactive LSP diagnostics on files/folders/batches.
When should I use Pi Lens Lsp Navigation?
Pi Lens Lsp Navigation fits situations like: development work in your project.
How do I install Pi Lens Lsp Navigation in Claude Code?
Run `npx skills add apmantza/pi-lens --skill pi-lens-lsp-navigation -a claude-code`. Or copy the skill folder (skills/pi-lens-lsp-navigation in apmantza/pi-lens) into .claude/skills/pi-lens-lsp-navigation in your project. Claude Code loads it when a task matches its description.
How do I install Pi Lens Lsp Navigation in Codex?
Run `npx skills add apmantza/pi-lens --skill pi-lens-lsp-navigation -a codex`. Or copy the skill folder (skills/pi-lens-lsp-navigation in apmantza/pi-lens) into .agents/skills/pi-lens-lsp-navigation in your project. Codex loads it when a task matches its description.
Can I use Pi Lens Lsp Navigation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add apmantza/pi-lens --skill pi-lens-lsp-navigation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pi-lens-lsp-navigation, .gemini/skills/pi-lens-lsp-navigation, .github/skills/pi-lens-lsp-navigation and .opencode/skills/pi-lens-lsp-navigation in your project.
What does Pi Lens Lsp Navigation need to run?
SKILL.md names no scripts, command-line tools or credentials: Pi Lens Lsp Navigation is instructions for the agent only.
Does Pi Lens Lsp Navigation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pi Lens Lsp Navigation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pi Lens Lsp Navigation use?
Pi Lens Lsp Navigation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pi Lens Lsp Navigation use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pi Lens Lsp Navigation?
Skills that share tags, products or a category with Pi Lens Lsp Navigation: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pi Lens Lsp Navigation?
apmantza (a GitHub user) maintains it in apmantza/pi-lens, which has 466 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 11, 2026.
Source: apmantza/pi-lens on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.