leanbusqts/analyze
skills/analyze/SKILL.md
Understand the current state, flows, and issues before making changes.
$ install --global
skillsauthnpx skillsauth add leanbusqts/agent47 analyzeInstall 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: Apr 30, 2026, 7:06 AM7.8s1 file scanned
SKILL.md
- name:
- analyze
- description:
- Understand the current state, flows, and issues before making changes.
- compatibility:
- Designed for skills-compatible coding agents.
- category:
- analysis
- tags:
- [analysis, discovery, diagnostics]
- applies_to:
- [frontend, backend, cli, scripts, mobile]
- priority:
- core
- agents:
- [universal, codex]
- repo_shapes:
- [app, library, cli, scripts, monorepo]
Analyze
Objective
- Map current behavior and constraints.
- Identify problems, risks, and missing context.
When to use
- Before proposing fixes or features.
- When debugging or evaluating existing code/flows.
Inputs
- User request and acceptance criteria.
- AGENTS.md, rules, specs (if any), and relevant code/tests/logs.
- Observed symptoms or failures.
Process
- Summarize the goal and observed behavior.
- Locate relevant code/tests and note gaps or contradictions.
- Identify probable causes or risk areas.
- List what evidence or data is missing.
- Propose next actions (investigation or plan) without changing code.
Outputs
- Findings (what is known).
- Risks/unknowns (what is missing).
- Proposed next steps or plan.
Edge cases
- If information is insufficient, stop and ask for specific inputs.
- Do not change code in this skill; stay diagnostic.
Related Skills
leanbusqts/cli-design
tools
VerifiedTrustedCommunity
Design or refine command surfaces, output contracts, and preview flows for CLI tools.
2SKILL.mdUpdated May 1, 2026
leanbusqts/troubleshoot
tools
VerifiedTrustedCommunity
Isolate root causes and propose targeted fixes with clear validation steps.
2SKILL.mdUpdated May 1, 2026
leanbusqts/spec-clarify
tools
VerifiedTrustedCommunity
Ask targeted questions to clarify scope, edge cases, and acceptance before coding.
2SKILL.mdUpdated May 1, 2026
leanbusqts/review
tools
VerifiedTrustedCommunity
Inspect changes for correctness, risks, and regressions before accepting them.
2SKILL.mdUpdated May 1, 2026