deep-dive
De la autor
Rigorous multi-agent deep-dive analysis for complex investigative tasks — auditing codebases, evaluating strategies or systems, validating designs, doing open-ended research. Deploys 4–6 specialist agents in parallel across distinct lanes, then synthesis, then adversarial red-team review, then optional patching — producing structured markdown research files plus a plain-English executive briefing with honest 1–10 confidence ratings. ALWAYS invoke when the user says any of "deep dive", "thorough audit", "rigorous analysis", "comprehensive review", "audit this codebase", "analyze the strategy", "evaluate this design", "review this thoroughly", or "research deep dive". Also invoke proactively for any open-ended investigative task involving a codebase, strategy, system design, or research question that warrants 30+ minutes of structured analysis — even when the user doesn't use these exact phrases.
Instalare
npx skills add nelsonwerd/idea-to-ship-skills --skill deep-dive -a claude-code
Se instalează în .claude/skills/deep-dive/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
- Îi cere agentului să-ți ascundă lucruriMediu
De ce 73
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- deep-auditpedrohcgs/claude-code-my-workflowComprehensive adversarial audit of a theory, proof, math/econ paper, codebase, or set of claims — decompose into components, fan out independent skeptics that must return CONCRETE defects, adjudicate every finding with a separate judge, fix all confirmed defects, then re-verify. Use when correctness must be bulletproof and single-pass or round-by-round review is too slow and too shallow. Invoke for "audit this rigorously", "find ALL the bugs/gaps", "make this rock solid", "converge faster on correctness".Știință★ 1.7K
- deep-researchfeiskyer/claude-code-settingsMulti-agent research orchestration: split a research goal into parallel sub-goals, run each via headless `claude -p` subprocesses, aggregate results into a polished report file. Use for systematic web/document research, competitive or industry analysis, batch link/dataset processing, and long-form evidence synthesis. Triggers: "深度调研", "deep research", "wide research", "多 Agent 调研", "系统调研".Știință★ 1.7K
- deep-research-teammalob/nix-configThis skill should be used when the user asks for "deep research", "research team", "comprehensive analysis", "research report", "investigate thoroughly", "compare X vs Y in depth", or needs synthesis across multiple sources with verification. It spawns a coordinated team of researcher agents across multiple rounds, with the lead triaging findings and creating targeted follow-up tasks. Scales from Focused (2 researchers, 1-2 rounds) to Comprehensive (4 researchers, 3-4 rounds with cross-verification). Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.Știință★ 462
- explain0xDarkMatter/claude-modsDeep explanation of complex code, files, or concepts. Dispatches skill-preloaded agents, uses structural search, generates mermaid diagrams. Triggers on: explain, deep dive, how does X work, architecture, data flow.Planificare★ 78
- keyword-deep-diveinhouseseo/superseo-skillsUse when planning to rank for a specific keyword. The agent Googles it, reads the top 10, classifies intent, reads the top 3 competitor pages, and produces a 90-day ranking plan with intent, SERP analysis, and content recommendations.Planificare★ 373
- architectural-analysistestdouble/hanPerforms deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for planning the change its findings imply — use plan-a-change. Not for discovering bounded contexts, ubiquitous language, or where code boundaries diverge from domain boundaries — use ddd-analysis. Not for writing documentation or architectural decision records.Planificare★ 327
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te