maple-audit
Installation
SKILL.md
Maple instrumentation audit
Review an existing OpenTelemetry setup against what Maple actually consumes, produce a findings report, then fix the gaps. This is the counterpart to maple-onboard. That skill installs telemetry from scratch; this one assumes instrumentation exists and checks whether it is right.
Before auditing, read checks.md in this skill's directory. It is the full check registry: check ids, severities, and what each gap breaks in Maple. Every finding you report must cite a check id from it. Never invent attribute keys or conventions that aren't in checks.md or the upstream OTel semconv.
For how to fix what you find, use the companion skills. Don't improvise recipes:
maple-onboarding-stylefor general OTel taste, VCS attributes, log bridges, metrics, LLM conventions.maple-nextjs-style,maple-nodejs-style,maple-python-style,maple-effect-style,maple-go-style,maple-rust-style,maple-java-style,maple-csharp-style,maple-kotlin-stylefor stack-specific bootstrap shapes.
Severity
| Severity | Meaning |
|---|---|
critical |
Breaks a Maple feature outright or is a data risk: missing service.name, hand-stamped status strings (error analytics read zero rows), logs without trace correlation, outbound calls that can't form a service-map edge (no Client span, broken traceparent, DB spans without db.system.name), PII in attributes. |
warn |
The feature works degraded or work is invisible: missing environment/VCS resource attrs, deprecated semconv keys, double-emission, high-cardinality labels or span names, outbound calls left Internal, untraced operations (missing auto-instrumentation for a used framework/driver, business operations and background jobs with no spans). |
info |
Signal-quality improvements: trace-context propagation across async boundaries, span noise, missing metrics, naming style, missing gen_ai.* on LLM calls. |