deep-analysis
Skill7 starsChanged 20 days agoMITView on GitHub
Runs a long, structured multi-step reasoning chain over the sequential-thinking MCP server, with branching, revision, and explicit hypothesis verification. Reserved for consequential, genuinely open problems whose answer cannot be reached by reading the code — an architecture decision with several defensible options, an unexplained performance bottleneck, technology selection, design trade-offs, or a migration and risk strategy. Because it is slow and token-heavy it is not for questions with one correct answer, factual or syntax lookups, summarizing or explaining existing code, a defect with an obvious cause, or applying a fix already chosen. Prefer /investigate for root-cause work on a reproducible defect, and /diverge when the need is a wide option space rather than one reasoned conclusion.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- Arcadia822/skryatheir own version, first seen Oct 21, 2026
- MaxMiksa/Autonomous-Companytheir own version, first seen Oct 15, 2026
- GregorStocks/mage-benchtheir own version, first seen Oct 8, 2026
- wbh604/UZI-Skilltheir own version, first seen Oct 8, 2026
- MaxMiksa/Auto-Companytheir own version, first seen Oct 2, 2026
- Serennity007/uzi-skilltheir own version, first seen Aug 25, 2026
Used with
Projects with it also use community-led-growth, ph-community-outreach and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
xfstudioSkillmicro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Also in 5 projects that use this
mastepanoskiSkillux-audit-rethink
Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.
Also in 5 projects that use this
ncklrsSkillseo-content-strategist
Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.
Also in 5 projects that use this
hieutrtrSkillcode-review-security
Security-focused code review checklist and automated scanning patterns. Use when reviewing pull requests for security issues, auditing authentication/authorization code, checking for OWASP Top 10 vulnerabilities, or validating input sanitization. Covers SQL injection prevention, XSS protection, CSRF tokens, authentication flow review, secrets detection, dependency vulnerability scanning, and secure coding patterns for Python (FastAPI) and React. Does NOT cover deployment security (use docker-best-practices) or incident handling (use incident-response).
Also in 5 projects that use this
- +6 more from nicepkg
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- wbh604/UZI-Skill★ 7.6ksame name
- MaxMiksa/Auto-Company★ 3.2ksame name
- MaxMiksa/Autonomous-Company★ 3.2ksame name
- nicepkg/auto-company★ 188same name
- GregorStocks/mage-bench★ 69same name
- NikitaDmitrieff/auto-co-meta★ 43same name
- taxueseek/session-digger★ 34same name
- Arcadia822/skrya★ 8same name
- ligenjian001-ai/agent-skills★ 8same name
- microsoft/code-optimizations-skills★ 5same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- api-contract-testingSkill
- browser-testingSkill
- ci-cd-templatesSkill
- code-review-checklistSkill
- context-escalationSkill
- deep-readSkill
- deliverySkill
- deployment-runbookSkill
- divergeSkill
- docker-deploymentSkill
- executeSkill
- experiment-loopSkill
- git-workflowSkill
- handoffSkill
- infrastructure-as-codeSkill
- investigateSkill
- kubernetes-opsSkill
- library-docsSkill
- multi-agent-orchestrationSkill
- observability-stackSkill
- remote-triggersSkill
- repo-contextSkill
- scheduled-tasksSkill
- security-scanSkill
- skill-creatorSkill
- sre-runbooksSkill
- ui-guidelinesSkill
- verified-handoffSkill
- worktree-workflowSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 52
Start the sequential-thinking chain with a clear problem statement and all known constraints.
- Distinctive: line 93
Don't force a conclusion — revise earlier thinking when new evidence contradicts it.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deep Analysis — Structured Reasoning Engine
Multi-step reasoning through the sequential-thinking MCP server. Decomposes complex problems into discrete thinking steps with branching, revision, and hypothesis verification.
When to Use
- Architectural decisions with multiple valid approaches
- Performance diagnosis where the bottleneck is unclear
- Technology selection requiring trade-off evaluation
- Complex debugging (use
/investigatefor full root cause protocol) - System design with many interconnected parts
- Migration strategies with risk assessment
Do NOT use for: Simple lookups, straightforward implementations, well-established patterns, or tasks where the answer is obvious.
Pre-Flight Gate
Activation is decided by the frontmatter description alone — this file is read only AFTER the skill has been selected. Nothing here can prevent over-triggering, so this gate is a post-selection redirect, not a filter.
Before proceeding, check the ABORT conditions below. If any holds, STOP, say in one line which one
fired, and take the redirect instead of starting the chain. Being invoked — including a literal
/deep-analysis or "give me a deep analysis" — does NOT override an ABORT: the phrasing that
selected this skill is not evidence the problem is hard.
| ABORT when the ask is… | Redirect |
| A factual, syntax, or definition lookup — anything with one correct answer | Answer directly |
| Summarizing or explaining existing code | Read the code and answer (/deep-read if it is large) |
| A well-established pattern or a straightforward implementation | Implement it directly |
| A defect with an obvious cause, or a fix the user already chose | Apply the fix directly |
| A reproducible defect whose cause is genuinely unknown | /investigate — 8-phase root cause |
| A wide option space rather than one reasoned conclusion | /diverge first, then return here to converge |
| Answerable by reading the code or running one command | Do that instead |
PROCEED only when no ABORT fired AND the problem is genuinely open — several defensible answers, an architectural or trade-off decision, an unexplained bottleneck, or a design space that must be reasoned through rather than looked up.
Protocol
1. Frame the Problem
Start the sequential-thinking chain with a clear problem statement and all known constraints.
mcp__sequential-thinking__sequentialthinking({
thought: "PROBLEM: <clear statement>. CONSTRAINTS: <known limits>. Let me decompose this...",
thoughtNumber: 1,
totalThoughts: 10, // Initial estimate — adjust as needed
nextThoughtNeeded: true
})2. Reason Through Steps
Each thought builds on the previous. Adjust totalThoughts up or down as understanding deepens.
mcp__sequential-thinking__sequentialthinking({
thought: "Step 2: Analyzing option A. Strengths: ... Weaknesses: ...",
thoughtNumber: 2,
totalThoughts: 10,
nextThoughtNeeded: true
})3. Branch When Alternatives Exist
Explore competing approaches without losing the main thread.
mcp__sequential-thinking__sequentialthinking({
thought: "BRANCH: What if we use approach B instead? Let me evaluate...",
thoughtNumber: 5,
totalThoughts: 12,
nextThoughtNeeded: true,
branchFromThought: 3,
branchId: "approach-B"
})4. Revise When Evidence Changes
Don't force a conclusion — revise earlier thinking when new evidence contradicts it.
mcp__sequential-thinking__sequentialthinking({
thought: "REVISION: My assumption in step 3 was wrong. Evidence shows X instead of Y...",
thoughtNumber: 7,
totalThoughts: 14,
nextThoughtNeeded: true,
isRevision: true,
revisesThought: 3
})5. Conclude with Verification
Final thought must verify the conclusion against the original problem and constraints.
mcp__sequential-thinking__sequentialthinking({
thought: "CONCLUSION: Approach A is recommended because [evidence]. Verified against constraints: [check]. Risks: [list].",
thoughtNumber: 10,
totalThoughts: 10,
nextThoughtNeeded: false
})Key Parameters
| Parameter | Type | Purpose |
thought | string | Current reasoning step |
thoughtNumber | int | Current step (1-based) |
totalThoughts | int | Estimated total steps (adjustable) |
nextThoughtNeeded | bool | false only when truly done |
isRevision | bool | Revising a previous thought |
revisesThought | int | Which thought number to revise |
branchFromThought | int | Branching point for alternatives |
branchId | string | Label for the branch |
needsMoreThoughts | bool | Need more steps than estimated |
Thinking Budget
- Up to 31,999 tokens per reasoning chain
- Typical analyses: 8-15 steps
- Adjust
totalThoughtsdynamically — don't force exactly N steps - Balance depth vs response time
Integration with Other Skills
| Situation | Use |
| Bug with unknown root cause | /investigate (calls deep-analysis in Phase 4) |
| Multi-step implementation goal | /execute (may call deep-analysis for complex sub-tasks) |
| Architecture decision only | /deep-analysis directly |
| Trade-off evaluation only | /deep-analysis directly |
| Option space too narrow — widen before converging | /diverge (divergent complement; widen first, then converge here) |
References
- Reasoning Patterns — hypothesis testing, design space exploration, root cause templates
- Integration Guide — pairing with agents and other skills
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

