maple-onboard

Onboard a project to Maple by installing OpenTelemetry traces, logs, and metrics across every app and service in the repo. Triggers on requests like 'install Maple', 'set up Maple', 'add Maple telemetry', 'onboard this repo to Maple', 'instrument with OpenTelemetry for Maple'.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, opinionated onboarding workflow with strong sequencing, explicit validation, and concrete stack-specific guidance. It loses a little on conciseness to repetition and on actionability because bootstrap code lives in companion skills rather than inline.

Suggestions

Consolidate the inline-key rationale (currently restated in Step 0, Step 2 bootstrap rules, and Hard rules) into one canonical location and reference it elsewhere to trim repeated tokens.

Include one minimal inline bootstrap snippet (e.g. a @vercel/otel registerOTel or NodeSDK example) so the most common stack is copy-pasteable without opening a companion skill.

State the coexist-with-existing-vendors rule once canonically (Step 2 or Hard rules) rather than restating it across sections.

Dimension	Reasoning	Score
Conciseness	The body is dense with opinionated, actionable rules rather than concept explanation, but the inline-key rationale (Sentry DSN analogy) and the coexist-with-vendors point are repeated across Step 0, Step 2, and Hard rules — minor padding that keeps it below the lean 5 anchor.	4 / 5
Actionability	Highly concrete — specific package names (@opentelemetry/sdk-node, @vercel/otel), exact resource attribute keys, named env vars, and copy-paste curl/mcp commands — but the actual per-stack bootstrap code is deferred to companion skills with no inline snippet, leaving a minor gap versus the fully copy-paste-ready 5 anchor.	4 / 5
Workflow Clarity	A clear Step 0–6 sequence with explicit validation in Step 4 (run dev/build, confirm telemetry leaves the process) and a feedback loop ('A bootstrap that loads but never POSTs is not a partial success. Fix it before moving on.'), plus a Step 1 user-confirmation checkpoint and a Hard-rules checklist.	5 / 5
Progressive Disclosure	Well-organized into clearly-labeled steps with one-level-deep, clearly-signaled references to companion style skills for per-stack detail; no bundle files exist in this skill to verify referenced paths against, and a fair amount of cross-stack config detail is inlined, placing it just below the 5 anchor.	4 / 5
	Total	17 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-constructed description that pairs a clear capability statement with explicit, natural trigger phrasing. It answers what and when concretely and occupies a distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions — 'installing OpenTelemetry traces, logs, and metrics across every app and service in the repo' — but a single core verb (installing) applied to three signals rather than multiple distinct action verbs, so it sits below the comprehensive 5 anchor.	4 / 5
Completeness	Explicitly answers both: what ('Onboard a project to Maple by installing OpenTelemetry traces, logs, and metrics across every app and service in the repo') and when ('Triggers on requests like ...') with concrete trigger phrases, matching the 5 anchor exactly.	5 / 5
Trigger Term Quality	Five explicit natural trigger phrases — 'install Maple', 'set up Maple', 'add Maple telemetry', 'onboard this repo to Maple', 'instrument with OpenTelemetry for Maple' — give comprehensive synonym coverage of phrasings a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The distinctive 'Maple' name anchors every trigger phrase to a clear niche, making it unlikely to fire for a generic OTel or unrelated skill — minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: MapleTechLabs/maple
Path: skills/maple-onboard/SKILL.md
Commit: 3cb9193

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.