Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a strong, lean style guide: highly actionable with complete code examples, exact attribute keys, and a verification section that includes real error-recovery loops. Its weaknesses are minor — some verbatim repetition between sections and a couple of long sections (LLM calls, framework notes) that could be offloaded to reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, prescriptive Maple-specific policy with no padding on concepts Claude already knows — every rule ("Don't read OTEL_EXPORTER_OTLP_* env vars", "Do not shell out to git from the running process") is non-obvious. Minor trims exist: "provider setup, exporter construction, log bridging, and framework instrumentation" is repeated verbatim in "Verify export" and "Smoke checks", and the commit-SHA env-var enumeration (VERCEL_GIT_COMMIT_SHA, RAILWAY_GIT_COMMIT_SHA, GITHUB_SHA, SOURCE_COMMIT, GIT_COMMIT, HEROKU_SLUG_COMMIT) runs long, so it sits at anchor 4 rather than 5. | 4 / 5 |
Actionability | Guidance is fully executable: the complete tracer.startActiveSpan try/catch/finally TypeScript example, the MapleBrowser.init(...) snippet with exact options, the exact curl sanity check ("curl -X POST <endpoint>/v1/traces -H \"authorization: Bearer MAPLE_TEST\" ... -d '{}' returns 200"), exact semantic-convention keys (vcs.repository.url.full, gen_ai.usage.cost, maple_ai.session.id), and exact package names cover the common cases copy-paste ready, matching anchor 5. | 5 / 5 |
Workflow Clarity | As a topic-organized style guide it is not an end-to-end sequenced workflow, but the "Verify export" section is a numbered sequence with explicit checkpoints ("Don't ship if the app's own startup is now broken") and a genuine error-recovery feedback loop (401 → try the other region's ingest → prove the path with MAPLE_TEST → disclose in the hand-off). The overall ordering of sections (bootstrap → instrument → verify) stays implicit, which keeps it at anchor 4 rather than 5. | 4 / 5 |
Progressive Disclosure | No bundle files exist, and per-framework detail is appropriately delegated to clearly signaled one-level-deep sibling skills ("see maple-nextjs-style", "see maple-effect-style") rather than inlined. However, the LLM-calls section (~44 lines) and the framework notes are long enough that they could be split into reference files, leaving minor organization gaps that fit anchor 4 rather than a clean anchor 5 split. | 4 / 5 |
Total | 17 / 20 Passed |