analyze
Use for generic analysis with structured output — readability, complexity, risk, performance, churn, dep health. Multiple sub-modes; pick or detect.
What this skill does
# analyze
Generic analysis with structured output. Multiple sub-modes for different angles.
## Modes
- `readability` — Flesch-Kincaid for prose; cognitive load for code
- `complexity` — cyclomatic, cognitive, nesting depth
- `risk` — combines complexity + churn + coverage gaps
- `performance` — hotspots from profiling
- `churn` — files most-modified per timeframe
- `dep-health` — outdated deps, security advisories, abandoned packages
- `naming` — naming consistency vs conventions
- `surface-area` — public API breadth vs use depth
User picks (or skill picks based on phrasing).
## Method
1. **Mode pick.**
2. **Run measurement.**
- Code analysis tools per mode (e.g. `eslint --rule complexity` for complexity)
- `git log --shortstat` for churn
- `npm audit` for dep health
3. **Rank.** Top 10 by mode-relevant score.
4. **Recommend** (don't auto-fix).
## Output shape (example: complexity)
```
Mode: complexity
Top 10:
#1 src/payment/processor.ts:14 function processPayment
Cyclomatic: 24
Cognitive: 38
Lines: 185
Recommend: extract validatePayment, settleCharge as separate fns
#2 src/auth/middleware.ts:42 function authenticate
...
Distribution:
Functions with complexity > 10: 7
Functions with complexity > 20: 2
Average: 4.3
```
## Rules
- **Mode-appropriate metric.** Don't run cognitive complexity for prose readability.
- **Real measurement, not estimate.** Use tools.
- **Recommendations actionable.** Name the refactor.
- **Don't auto-fix.** Surface; let user act.
## Anti-patterns
- Mode mismatch (readability of code = wrong tool)
- Aggregate scores without per-item breakdown
- "High complexity" without naming the function
- Recommendations that are too generic ("refactor this")
## When NOT to use
- Specific concern (use the targeted skill — `/empathy`, `/optimize`, `/security`)
- Tiny codebase (manual judgement faster)
## Subagent dispatch
- `Explore` for breadth
- `Bash` for tool invocations
- `general-purpose` for synthesis
## Value over native CC
CC will analyse on request. CC won't naturally pick the mode-appropriate metric or surface ranked findings with concrete recommendations. The mode-discipline IS the value.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.