alexei-led/smart-explore
dist/pi/skills/smart-explore/SKILL.md
Token-efficient local code navigation and extraction. Use when exploring a known file or bounded module outline, finding a known symbol in a scoped area, or extracting exact function/type bodies with smart_outline, smart_search, and smart_unfold. NOT for repo-wide structural pattern search, architecture or trace-flow questions, ast-grep/codegraph/GitNexus evidence, or broad caller/implementation maps.
$ install --global
skillsauthnpx skillsauth add alexei-led/claude-code-config smart-exploreInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 2, 2026, 2:18 AM304.3s1 file scanned
SKILL.md
- description:
- Token-efficient local code navigation and extraction. Use when exploring
- name:
- smart-explore
<!-- Pi platform guidance -->
<!-- Use Pi tool names exactly: read, bash, edit, write, ask_user_question, structured_output, todo, Agent, get_subagent_result, steer_subagent, web_search, web_answer, web_research. -->
<!-- Use Agent, get_subagent_result, and steer_subagent for delegated work. -->
<!-- Use ctx7 or npx ctx7@latest through bash when Context7 documentation lookup is required. -->
Smart Explore in Pi
Use cheap local structure before reading large files. The goal is a tight outline or exact extraction from a known area, not repo-wide codebase search.
Boundary
Use this skill for:
- known-file outlines
- known-module outlines
- bounded symbol lookup
- exact function, method, class, or type extraction
- read-next ranges after another search/review tool narrowed the area
Do not use this skill for repo-wide structural patterns, ast-grep rules, trace-flow, "how does X work", zoom-out maps, all-callers searches, codegraph, GitNexus, or architecture evidence. Use a dedicated repo-wide search or architecture-analysis workflow first; return here only after the scope is a known file, module, or symbol.
Tool Order
- Language-native outline tools when available.
rgfor exact text or symbol fallback in a bounded scope.fdfor candidate file discovery when the path is missing.readafter narrowing.
Workflow
- Confirm the scope is a known file, known module, or bounded symbol. If not, use a dedicated repo-wide workflow first.
- Use
fdonly to find candidate files or language roots. - Use
rgfor imports, declarations, and exact symbol text inside the bounded scope. - Use language-native tools when available:
- Python:
python -m ast,ruff,pyright - Go:
go list,go test,go doc,gofmt -wonly when editing - TypeScript:
tsc --noEmit,bun test
- Python:
- Read only relevant ranges or small files.
- Return an outline with exact paths and line references.
Commands
fd '\.(go|py|ts|tsx|js|jsx)$' src
rg -n 'class |def |func |export |interface |type ' src/module
rg -n 'UserService|createUser' src/module
Output Contract
## Smart Explore
### Scope
<known file/module/symbol>
### Files
- `path` — why it matters
### Symbols
- `path:line` — symbol and role
### Edges
- caller -> callee or import relationship
### Read Next
1. `path:line-range` — reason
Related Skills
alexei-led/writing-shell
tools
VerifiedTrustedCommunity
Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, TypeScript, Go, web code, or infrastructure operations.
33SKILL.mdUpdated Jun 5, 2026
alexei-led/spec-flow
tools
VerifiedTrustedCommunity
Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview.
33SKILL.mdUpdated Jun 5, 2026
alexei-led/operating-infra
testing
VerifiedTrustedCommunity
Author, inspect, troubleshoot, and review infrastructure across IaC, Kubernetes, cloud resources, containers, CI/CD, and Linux hosts. Use when changing Terraform/OpenTofu, Kubernetes, Helm, Kustomize, Dockerfiles, GitHub Actions, AWS, GCP, Cloud Run, BigQuery, IAM, logs, instances, or service health. NOT for deploy/apply/rollback workflows (see deploying-infra). NOT for shell scripts or generic command pipelines (see writing-shell).
33SKILL.mdUpdated Jun 5, 2026
alexei-led/configuring-git-hygiene
development
VerifiedTrustedCommunity
Configure safe git workflow hygiene: pre-commit/pre-push hooks, Gitleaks secret scanning, .gitignore rules, local git config, and guardrails. Use when setting up git hooks, gitleaks/git leaks, staged pre-commit checks, pre-push validation, core.hooksPath, .gitignore, or git config best practices. NOT for creating commits (use committing-code), cleaning branches/worktrees (use cleanup-git), or creating worktrees (use using-git-worktrees).
33SKILL.mdUpdated Jun 5, 2026