mikeparcewski/wicked-garden-platform-observability
skills/platform/observability/SKILL.md
Use when monitoring or diagnosing the wicked-garden plugin ecosystem — health probes, contract assertions, hook traces, error pattern detection, and APM/logging/metrics toolchain discovery. NOT for distributed tracing across services (use the platform domain skill's traces action) or audit evidence (use platform/audit). Use when: "plugin health", "health probe", "hook didn't fire", "hook traces", "contract assertions", "validate script outputs", "what monitoring tools are installed", "toolchain discovery", or any former /wicked-garden:platform:{plugin-health|assert|toolchain} invocation.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-platform-observabilityInstall 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: Jul 13, 2026, 7:57 AM109.1s3 files scanned
SKILL.md
- name:
- wicked-garden-platform-observability
- description:
- |
- Use when:
- plugin health", "health probe", "hook didn't fire", "hook traces",
- /wicked-garden:
- platform:{plugin-health|assert|toolchain} invocation.
- phase_relevance:
- ["build", "review", "operate"]
- archetype_relevance:
- ["*"]
Observability Skill
Monitor and diagnose the wicked-garden plugin ecosystem — health probes, contract assertions, and hook execution traces. All three pillars run inline (no agent delegation needed).
Quick Start
# Check plugin ecosystem health
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/platform/observability/health_probe.py
# Query recent hook traces (operational log)
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/platform/observability/ops_log_viewer.py --tail 20
# Validate script output contracts
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/platform/observability/assert_contracts.py
Three Pillars
1. Health Probes
Validate ecosystem integrity by checking plugin structure, hook bindings, and script availability.
Run the health probe script inline:
# All plugins
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/platform/observability/health_probe.py
# Single plugin, machine-readable
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/platform/observability/health_probe.py --plugin wicked-garden --json
- Display results grouped by plugin, with severity icons.
- Exit codes:
0= healthy,1= warnings,2= failures. - Show the path to
latest.jsonfor programmatic consumption.
Auth retry (--retry-auth): after the user authenticates a CLI
mid-session, re-run the plugin readiness probes from bootstrap — see
refs/plugin-health.md for the probe invocation and
reporting steps.
2. Hook Traces
Every hook execution is traced with timing, exit codes, and silent failure detection. Query the operational log to diagnose issues via scripts/platform/observability/ops_log_viewer.py:
# Last 10 entries
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/platform/observability/ops_log_viewer.py --tail 10
# Filter by verbosity level (normal | verbose | debug)
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/platform/observability/ops_log_viewer.py --level verbose
# Machine-readable, or a specific session's log
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/platform/observability/ops_log_viewer.py --json --session {ID}
Note: hook-trace viewing is this script, not distributed tracing. For latency/dependency analysis of distributed traces across services, use the
tracesaction of the platform domain skill (skills/platform/SKILL.md).
3. Contract Assertions
Validate that plugin scripts return data matching their declared JSON schemas.
Run the assertion script inline:
# Run all assertions
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/platform/observability/assert_contracts.py
# Single plugin, machine-readable
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/platform/observability/assert_contracts.py --plugin wicked-garden --json
- Display results: pass/fail per script, violation details for failures.
- Note: schemas must exist in
schemas/{plugin}/{script}.jsonbefore assertions can run.
Common Diagnostic Flows
"Something seems broken"
- Run the health probe (pillar 1) — check structural integrity
- Query the ops log (pillar 2) — look for hook entries with exit code != 0 or unexpected output
- Run contract assertions (pillar 3) — validate output contracts
"Hook didn't fire"
- Query the ops log with
--tail 20(pillar 2) — check if the hook was invoked - Look for: missing entries (hook never triggered) or exit code != 0
"Script returns wrong data"
- Run contract assertions with
--plugin {name}(pillar 3) — check contract compliance - Review violation details for schema mismatches
Engineer Toolchain Discovery
Discover monitoring CLIs (APM, logging, metrics, cloud) available in the current environment and run queries against them — inline, no dispatch.
Semantics:
- No query: detect tools per category with
command -vand report what was found, grouped by category with binary path and version. --query "...": route the query to the appropriate detected tool(s) — logging tools search recent logs (last 1h default), metrics tools query matching metrics, APM tools search traces/events, cloud tools query CloudWatch/Stackdriver/Azure logs — and present results side-by-side with tool attribution.--category apm|logging|metrics|cloud: limit both discovery and query execution to that category.- Never fail — discovery is read-only. A tool that errors on query is reported and the rest continue; when nothing is found, report "No monitoring CLIs detected" and suggest installation options.
→ Read("${CLAUDE_PLUGIN_ROOT}/skills/platform/observability/refs/toolchain-discovery.md")
for the detection script, per-tool usage examples, query routing, display
format, and next-step suggestions.
CLI Categories
| Category | Tools Detected |
|----------|---------------|
| APM | datadog-agent, newrelic, dt (Dynatrace) |
| Logging | splunk, elasticsearch, logcli (Loki) |
| Metrics | promtool (Prometheus), grafana-cli, influx |
| Cloud | aws (CloudWatch), gcloud (monitoring), az (Azure Monitor) |
Detection uses command -v — no external dependencies.
Integration
- smaht (domain): Context assembly uses trace data to detect degraded adapters
- crew (domain): Health probes run during execution gates
- DomainStore: Traces stored via DomainStore (local JSON), with SqliteStore for search
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