mikeparcewski/traces
skills/platform/traces/SKILL.md
Distributed tracing analysis for performance investigation and service dependency mapping. Analyze latency breakdowns, identify bottlenecks, map service calls, and correlate slow requests with code changes. Use when: "trace analysis", "distributed tracing", "latency investigation", "slow requests", "service dependencies", "performance tracing"
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden tracesInstall 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 19, 2026, 4:09 AM100.2s4 files scanned
SKILL.md
- name:
- traces
- description:
- |
- Use when:
- trace analysis", "distributed tracing", "latency investigation", "slow requests", "service dependencies", "performance tracing
Distributed Tracing Analysis Skill
Analyze distributed traces for performance investigation and service dependency mapping.
When to Use
- Latency investigation
- Performance bottleneck detection
- Service dependency mapping
- Slow request analysis
- Cross-service debugging
- User asks "traces", "latency", "slow", "performance"
Tracing Analysis Approach
1. Discover Tracing Sources
Use capability-based discovery:
# Discover available integrations via capability detection
# Scan for tracing capabilities by analyzing server descriptions:
# - tracing capability: Dedicated distributed tracing systems
# - apm capability: APM tools that include distributed tracing
# - telemetry capability: Unified observability with tracing support
2. Query Trace Data
For each discovered source:
- Slow traces (>SLO threshold)
- Error traces
- Service operation latencies
- Request volume by endpoint
- Service-to-service call patterns
3. Analyze Latency Breakdown
For slow traces:
- Total request duration
- Time spent in each service
- Database query time
- External API call time
- Queue/async processing time
- Network/serialization overhead
4. Map Service Dependencies
Build dependency graph:
- Service call chains
- Synchronous vs asynchronous calls
- Fan-out patterns
- Critical path services
5. Identify Bottlenecks
See refs/bottlenecks-detection.md and refs/bottlenecks-resolution.md for detailed patterns.
Common bottleneck types:
- N+1 query patterns: Many sequential DB calls
- Slow external calls: Third-party API latency
- Database bottlenecks: Long query times
- Sequential processing: Parallelizable operations
- Resource contention: Lock waits, queue depth
6. Correlate with Code
Use wicked-garden:search to find:
- Database queries in slow services
- External API calls
- Synchronous operations that could be async
- Missing caching opportunities
Integration Discovery
| Capability | What to Look For | Provides | |------------|------------------|----------| | tracing | Distributed tracing, span collection, trace analysis | Distributed traces, span details | | apm | Performance monitoring with distributed tracing | Traces with performance context | | telemetry | Unified observability with traces and metrics | Unified traces and metrics |
Fallback: Analyze code for call patterns via wicked-garden:search (database calls, HTTP clients, async operations).
Output Format
Provide trace analysis with:
- Performance summary (slow traces, latency percentiles)
- Service dependency map (tree view with timing)
- Bottleneck analysis (latency, type, root cause)
- Optimization opportunities (quick wins vs long-term)
See refs/bottlenecks-detection.md and refs/bottlenecks-resolution.md for detailed output templates.
Common Performance Patterns
See refs/bottlenecks-detection.md and refs/bottlenecks-resolution.md for detailed analysis of:
N+1 Query Pattern
Sequential database queries in a loop. Fix with batch queries or JOIN.
Synchronous External Calls
Waiting for external APIs sequentially. Fix with Promise.all or async processing.
Missing Caching
Repeated identical queries. Fix with caching layer (Redis, in-memory).
Database Query Inefficiency
Slow database operations. Fix with indexes, query optimization, pagination.
Resource Contention
Lock waits or queue delays. Fix with reduced lock scope, optimistic locking.
Service Dependency Analysis
Critical Path Detection
Identify services on critical path (required for request completion). Focus optimization here.
Fan-Out Pattern Detection
Single request triggers many downstream calls. Risk of amplified load and cascading failures.
Circular Dependency Detection
Service A calls B calls A (cycle). Risk of infinite loops and complex debugging.
See refs/dependencies.md for detailed dependency analysis patterns.
Integration with engineering
When bottlenecks identified, engage wicked-garden:engineering:backend with trace context, code locations, and optimization recommendations.
Integration with wicked-crew
During build phase:
- Capture baseline latency metrics
- Monitor post-deployment latency
- Alert on p95 increases >20%
- Recommend rollback if critical path slows
Emit events:
observe:trace:slow:warningobserve:correlation:found:success
Notes
- Focus on p95/p99, not averages (outliers matter)
- Identify critical path first (highest impact)
- Consider parallelization opportunities
- External calls often biggest bottleneck
- Add instrumentation if spans missing
- Correlate slow traces with error traces
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026