From wicked-garden
Plugin observability and engineer toolchain discovery. Health probes, contract assertions, and hook execution tracing for the plugin ecosystem. Also discovers and queries APM, logging, metrics, and cloud monitoring CLIs available in the engineer's environment. Use when: "check plugin health", "are hooks working", "silent failures", "trace hook execution", "validate contracts", "plugin diagnostics", "check logs", "query metrics", "view traces", "system monitoring", "datadog", "newrelic", "prometheus", "grafana", "splunk", "cloudwatch"
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
Monitor and diagnose the wicked-garden plugin ecosystem — health probes, contract assertions, and hook execution traces.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Monitor and diagnose the wicked-garden plugin ecosystem — health probes, contract assertions, and hook execution traces.
# Check ecosystem health
/wicked-garden:platform:health
# Query recent hook traces
/wicked-garden:platform:traces --tail 20
# Validate script output contracts
/wicked-garden:platform:assert
| Command | Purpose |
|---|---|
/wicked-garden:platform:health | Run health probes against plugins |
/wicked-garden:platform:traces | Query hook execution traces for the session |
/wicked-garden:platform:assert | Validate script outputs against declared schemas |
Validate ecosystem integrity by checking plugin structure, hook bindings, and script availability.
# All plugins
/wicked-garden:platform:health
# Single plugin, machine-readable
/wicked-garden:platform:health --plugin wicked-garden --json
Exit codes: 0 = healthy, 1 = warnings, 2 = failures.
Every hook execution is traced with timing, exit codes, and silent failure detection. Query traces to diagnose issues.
# Last 10 traces
/wicked-garden:platform:traces --tail 10
# Only silent failures (exit 0 but unexpected output)
/wicked-garden:platform:traces --silent-only
# Trace stats
/wicked-garden:platform:traces --stats
Validate that plugin scripts return data matching their declared JSON schemas.
# Run all assertions
/wicked-garden:platform:assert
# Single plugin
/wicked-garden:platform:assert --plugin wicked-garden
Schemas live in schemas/{plugin}/{script}.json.
/wicked-garden:platform:health — check structural integrity/wicked-garden:platform:traces --silent-only — find silent failures/wicked-garden:platform:assert — validate output contracts/wicked-garden:platform:traces --tail 20 — check if hook was invoked/wicked-garden:platform:assert --plugin {name} — check contract complianceDiscover and interact with monitoring CLIs available in the current environment.
# Discover what monitoring tools are installed
/wicked-garden:platform:toolchain
# Query logs with detected CLI
/wicked-garden:platform:toolchain --query "error last 1h"
# Detect by category
/wicked-garden:platform:toolchain --category apm
| Category | Tools Detected |
|---|---|
| APM | datadog-agent, newrelic-cli, dt (Dynatrace) |
| Logging | splunk, elk / elasticsearch, kibana |
| Metrics | promtool (Prometheus), grafana-cli |
| Cloud | aws cloudwatch, gcloud monitoring, az monitor |
Detection uses command -v — no external dependencies.
→ See refs/toolchain-discovery.md for detection patterns and per-tool usage examples.