/deep-analysis
Analytical thinking patterns for comprehensive evaluation, code audits, security analysis, and performance reviews. Provides structured templates for thorough investigation with extended thinking support.
$ npx -y skills add nicepkg/auto-company --skill deep-analysis --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/deep-analysis
Context preview
The summary Claude sees to decide when to auto-load this skill.
Analytical thinking patterns for comprehensive evaluation, code audits, security analysis, and performance reviews. Provides structured templates for thorough investigation with extended thinking support.
SKILL.md
deep-analysis.SKILL.mdname: deep-analysis
description: Analytical thinking patterns for comprehensive evaluation, code audits, security analysis, and performance reviews. Provides structured templates for thorough investigation with extended thinking support.
allowed-tools:
- Bash
- Read
- Write
- Edit
- Glob
- Grep
- Task
- WebFetch
- WebSearch
dependencies:
- extended-thinking
- complex-reasoning
triggers:
- analyze
- audit
- review
- assess
- evaluate
- investigate
- deep dive
- comprehensive review
- security analysis
- performance analysis
- code audit
Deep Analysis Skill
Comprehensive analytical templates for thorough investigation, audits, and evaluations leveraging extended thinking capabilities.
When to Use
- **Code audits** requiring systematic review
- **Security assessments** and threat modeling
- **Performance analysis** and optimization planning
- **Architecture reviews** and technical debt assessment
- **Incident post-mortems** and root cause analysis
- **Compliance audits** and risk assessments
Analysis Templates
Code Audit Template
## Code Audit Report
**Repository**: [repo-name]
**Scope**: [files/modules audited]
**Date**: [YYYY-MM-DD]
**Auditor**: Claude + [Human reviewer]
### Executive Summary
[2-3 sentence overview of findings]
### Audit Criteria
- [ ] Code quality and maintainability
- [ ] Security vulnerabilities
- [ ] Performance concerns
- [ ] Test coverage
- [ ] Documentation completeness
- [ ] Dependency health
### Critical Findings
| ID | Severity | Location | Issue | Recommendation |
|----|----------|----------|-------|----------------|
| C1 | Critical | file:line | [Issue] | [Fix] |
| C2 | Critical | file:line | [Issue] | [Fix] |
### High Priority Findings
| ID | Severity | Location | Issue | Recommendation |
|----|----------|----------|-------|----------------|
| H1 | High | file:line | [Issue] | [Fix] |
### Medium Priority Findings
[...]
### Low Priority / Suggestions
[...]
### Metrics
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| Test Coverage | 75% | 80% | ⚠️ |
| Cyclomatic Complexity | 12 | <10 | ⚠️ |
| Technical Debt | 4.2d | <3d | ❌ |
| Security Score | 8/10 | 9/10 | ⚠️ |
### Recommendations
1. **Immediate**: [Critical fixes]
2. **Short-term**: [Within sprint]
3. **Long-term**: [Tech debt reduction]
### Sign-off
- [ ] All critical issues addressed
- [ ] High priority issues have timeline
- [ ] Audit findings documented in backlog
Security Threat Model Template
## Threat Model: [System/Component Name]
**Version**: [1.0]
**Last Updated**: [YYYY-MM-DD]
**Classification**: [Internal/Confidential]
### System Overview
[Brief description of the system being modeled]
### Assets
| Asset | Description | Sensitivity | Owner |
|-------|-------------|-------------|-------|
| User Data | PII, credentials | Critical | Auth Team |
| API Keys | Service credentials | High | DevOps |
| Business Data | Transactions | High | Product |
### Trust Boundaries
┌─────────────────────────────────────────┐ │ External (Untrusted) │ │ [Internet Users] [Third-party APIs] │ └──────────────────┬──────────────────────┘ │ WAF/Load Balancer ┌──────────────────┴──────────────────────┐ │ DMZ (Semi-trusted) │ │ [API Gateway] [CDN] [Public Services] │ └──────────────────┬──────────────────────┘ │ Internal Firewall ┌──────────────────┴──────────────────────┐ │ Internal (Trusted) │ │ [App Servers] [Databases] [Queues] │ └─────────────────────────────────────────┘
### Threat Categories (STRIDE)
#### Spoofing
| Threat | Likelihood | Impact | Mitigation |
|--------|------------|--------|------------|
| Credential theft | Medium | High | MFA, rate limiting |
| Session hijacking | Low | High | Secure cookies, HTTPS |
#### Tampering
| Threat | Likelihood | Impact | Mitigation |
|--------|------------|--------|------------|
| SQL injection | Medium | Critical | Parameterized queries |
| Data modification | Low | High | Integrity checks |
#### Repudiation
[...]
#### Information Disclosure
[...]
#### Denial of Service
[...]
#### Elevation of Privilege
[...]
### Attack Vectors
1. **Vector 1**: [Description]
- Entry point: [Where]
- Technique: [How]
- Mitigation: [Defense]
### Risk Matrix
| Threat | Likelihood | Impact | Risk Score | Priority |
|--------|------------|--------|------------|----------|
| T1 | High | Critical | 9 | P1 |
| T2 | Medium | High | 6 | P2 |
| T3 | Low | Medium | 3 | P3 |
### Security Controls
| Control | Type | Status | Coverage |
|---------|------|--------|----------|
| WAF | Preventive | ✅ Active | External |
| SAST | Detective | ✅ CI/CD | Code |
| DAST | Detective | ⚠️ Partial | Runtime |
| Encryption | Preventive | ✅ Active | Data |
### Recommendations
1. [Priority 1 recommendations]
2. [Priority 2 recommendations]
3. [Priority 3 recommendations]
Performance Analysis Template
## Performance Analysis Report
**System**: [System name]
**Period**: [Date range]
**Environment**: [Production/Staging]
### Executive Summary
[Key findings and recommendations]
### Performance Metrics
#### Response Times
| Endpoint | P50 | P95 | P99 | Target | Status |
|----------|-----|-----|-----|--------|--------|
| /api/users | 45ms | 120ms | 350ms | <200ms | ✅ |
| /api/search | 230ms | 890ms | 2.1s | <500ms | ❌ |
| /api/reports | 1.2s | 3.4s | 8.2s | <2s | ❌ |
#### Throughput
| Service | Current RPS | Peak RPS | Capacity | Utilization |
|---------|-------------|----------|----------|-------------|
| API | 1,200 | 2,400 | 5,000 | 48% |
| Worker | 500 | 800 | 1,000 | 80% |
#### Resource Utilization
| Resource | Average | Peak | Threshold | Status |
|----------|---------|------|-----------|--------|
| CPU | 45% | 78% | 80% | ⚠️ |
| Memory | 62% | 85% | 85% | ⚠️ |
| Disk I/O | 30% | 55%
Read more
name: deep-analysis description: Analytical thinking patterns for comprehensive evaluation, code audits, security analysis, and performance reviews. Provides structured templates for thorough investigation with extended thinking support. allowed-tools: - Bash - Read - Write - Edit - Glob - Grep - Task - WebFetch - WebSearch dependencies: - extended-thinking - complex-reasoning triggers: - analyze - audit - review - assess - evaluate - investigate - deep dive - comprehensive review - security analysis - performance analysis - code audit
Deep Analysis Skill
Comprehensive analytical templates for thorough investigation, audits, and evaluations leveraging extended thinking capabilities.
When to Use
- **Code audits** requiring systematic review
- **Security assessments** and threat modeling
- **Performance analysis** and optimization planning
- **Architecture reviews** and technical debt assessment
- **Incident post-mortems** and root cause analysis
- **Compliance audits** and risk assessments
Analysis Templates
Code Audit Template
## Code Audit Report **Repository**: [repo-name] **Scope**: [files/modules audited] **Date**: [YYYY-MM-DD] **Auditor**: Claude + [Human reviewer] ### Executive Summary [2-3 sentence overview of findings] ### Audit Criteria - [ ] Code quality and maintainability - [ ] Security vulnerabilities - [ ] Performance concerns - [ ] Test coverage - [ ] Documentation completeness - [ ] Dependency health ### Critical Findings | ID | Severity | Location | Issue | Recommendation | |----|----------|----------|-------|----------------| | C1 | Critical | file:line | [Issue] | [Fix] | | C2 | Critical | file:line | [Issue] | [Fix] | ### High Priority Findings | ID | Severity | Location | Issue | Recommendation | |----|----------|----------|-------|----------------| | H1 | High | file:line | [Issue] | [Fix] | ### Medium Priority Findings [...] ### Low Priority / Suggestions [...] ### Metrics | Metric | Value | Target | Status | |--------|-------|--------|--------| | Test Coverage | 75% | 80% | ⚠️ | | Cyclomatic Complexity | 12 | <10 | ⚠️ | | Technical Debt | 4.2d | <3d | ❌ | | Security Score | 8/10 | 9/10 | ⚠️ | ### Recommendations 1. **Immediate**: [Critical fixes] 2. **Short-term**: [Within sprint] 3. **Long-term**: [Tech debt reduction] ### Sign-off - [ ] All critical issues addressed - [ ] High priority issues have timeline - [ ] Audit findings documented in backlog
Security Threat Model Template
## Threat Model: [System/Component Name] **Version**: [1.0] **Last Updated**: [YYYY-MM-DD] **Classification**: [Internal/Confidential] ### System Overview [Brief description of the system being modeled] ### Assets | Asset | Description | Sensitivity | Owner | |-------|-------------|-------------|-------| | User Data | PII, credentials | Critical | Auth Team | | API Keys | Service credentials | High | DevOps | | Business Data | Transactions | High | Product | ### Trust Boundaries
┌─────────────────────────────────────────┐ │ External (Untrusted) │ │ [Internet Users] [Third-party APIs] │ └──────────────────┬──────────────────────┘ │ WAF/Load Balancer ┌──────────────────┴──────────────────────┐ │ DMZ (Semi-trusted) │ │ [API Gateway] [CDN] [Public Services] │ └──────────────────┬──────────────────────┘ │ Internal Firewall ┌──────────────────┴──────────────────────┐ │ Internal (Trusted) │ │ [App Servers] [Databases] [Queues] │ └─────────────────────────────────────────┘
### Threat Categories (STRIDE) #### Spoofing | Threat | Likelihood | Impact | Mitigation | |--------|------------|--------|------------| | Credential theft | Medium | High | MFA, rate limiting | | Session hijacking | Low | High | Secure cookies, HTTPS | #### Tampering | Threat | Likelihood | Impact | Mitigation | |--------|------------|--------|------------| | SQL injection | Medium | Critical | Parameterized queries | | Data modification | Low | High | Integrity checks | #### Repudiation [...] #### Information Disclosure [...] #### Denial of Service [...] #### Elevation of Privilege [...] ### Attack Vectors 1. **Vector 1**: [Description] - Entry point: [Where] - Technique: [How] - Mitigation: [Defense] ### Risk Matrix | Threat | Likelihood | Impact | Risk Score | Priority | |--------|------------|--------|------------|----------| | T1 | High | Critical | 9 | P1 | | T2 | Medium | High | 6 | P2 | | T3 | Low | Medium | 3 | P3 | ### Security Controls | Control | Type | Status | Coverage | |---------|------|--------|----------| | WAF | Preventive | ✅ Active | External | | SAST | Detective | ✅ CI/CD | Code | | DAST | Detective | ⚠️ Partial | Runtime | | Encryption | Preventive | ✅ Active | Data | ### Recommendations 1. [Priority 1 recommendations] 2. [Priority 2 recommendations] 3. [Priority 3 recommendations]
Performance Analysis Template
## Performance Analysis Report **System**: [System name] **Period**: [Date range] **Environment**: [Production/Staging] ### Executive Summary [Key findings and recommendations] ### Performance Metrics #### Response Times | Endpoint | P50 | P95 | P99 | Target | Status | |----------|-----|-----|-----|--------|--------| | /api/users | 45ms | 120ms | 350ms | <200ms | ✅ | | /api/search | 230ms | 890ms | 2.1s | <500ms | ❌ | | /api/reports | 1.2s | 3.4s | 8.2s | <2s | ❌ | #### Throughput | Service | Current RPS | Peak RPS | Capacity | Utilization | |---------|-------------|----------|----------|-------------| | API | 1,200 | 2,400 | 5,000 | 48% | | Worker | 500 | 800 | 1,000 | 80% | #### Resource Utilization | Resource | Average | Peak | Threshold | Status | |----------|---------|------|-----------|--------| | CPU | 45% | 78% | 80% | ⚠️ | | Memory | 62% | 85% | 85% | ⚠️ | | Disk I/O | 30% | 55%
全自主 AI 公司,24/7 不停歇运行 14 个 AI Agent,每个都是该领域世界顶级专家的思维分身。 自主构思产品、做决策、写代码、部署上线、搞营销。没有人类参与。 基于 Claude Code Agent Teams 驱动。 ⚠️ 实验项目 — 还在测试中,能跑但不一定稳定。目前仅支持 macOS。
Other skills on auto-company.
- /agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a
Open skill - /code-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,
Open skill - /cold-email-sequence-generator
Generate personalized cold email sequences (7-14 emails) with A/B test subject lines, follow-up timing recommendations, and integrated social proof. Creates multi-touch campaigns optimized for response rates. Use when users need outbound email campaigns, sales sequences, or lead
Open skill - /community-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
Open skill - /competitive-intelligence-analyst
Use this skill when users need to analyze competitors, monitor market movements, benchmark features/pricing, identify market gaps, or understand competitive positioning. Activates for "what are competitors doing," market analysis, or differentiation strategy.
Open skill - /content-strategy
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For
Open skill

