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

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

85%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 well-structured, actionable onboarding workflow with strong sequencing and validation feedback loops, plus clean progressive disclosure via companion skills. The main gaps are minor redundancy around the inline-key rationale and the absence of a complete inline bootstrap code example.

Suggestions

Consolidate the inline-ingest-key rationale into one place (e.g. Step 0) and reference it from Step 2 and Hard rules instead of restating it, to tighten conciseness.

Add one complete copy-paste-ready bootstrap snippet (e.g. a NodeSDK or @vercel/otel registerOTel example) inline so the core action is executable without opening a companion skill.

Trim conversational asides like 'Done — move on to Step 1' and 'Don't block on signup' that add tokens without adding instructional value.

Dimension	Reasoning	Score
Conciseness	Mostly lean instructional prose for a genuinely complex multi-stack task, but the inline-key rationale is repeated across Step 0, Step 2, and Hard rules, and a few chatty asides ('Done — move on to Step 1', 'Don't block on signup') could be trimmed.	4 / 5
Actionability	Gives concrete commands (claude mcp add, curl smoke test, uv run ...), specific package names, and exact attribute/env keys, but defers the actual bootstrap code shape to companion skills rather than showing a copy-paste-ready bootstrap inline.	4 / 5
Workflow Clarity	Clear Step 0–6 sequence with explicit validation checkpoints (show the service list before starting; Step 4 verifies startup and telemetry egress) and error-recovery feedback loops ('bootstrap that loads but never POSTs is not a partial success — fix it before moving on').	5 / 5
Progressive Disclosure	SKILL.md serves as the overview with per-stack detail deferred one level deep to clearly signaled companion skills (maple-nextjs-style, maple-python-style, etc.) plus an explicit fallback rule; no bundle files exist to verify against, and the section structure is clean.	5 / 5
	Total	18 / 20 Passed

Description

100%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-rounded description that concretely states what the skill does, scopes it to every app and service, and supplies multiple natural trigger phrases. It cleanly satisfies the what/when requirement with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete actions — 'installing OpenTelemetry traces, logs, and metrics across every app and service in the repo' — covering all three telemetry signals with comprehensive scope.	5 / 5
Completeness	Explicitly answers both 'what' (onboard a project to Maple by installing OTel traces/logs/metrics across every app and service) and 'when' via a concrete 'Triggers on requests like...' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Provides five natural trigger phrases users would actually say ('install Maple', 'set up Maple', 'add Maple telemetry', 'onboard this repo to Maple', 'instrument with OpenTelemetry for Maple') with good synonym coverage.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Maple onboarding via OpenTelemetry) with Maple-specific triggers, making conflict with other skills minimal; voice is third person with no first/second-person penalty.	5 / 5
	Total	20 / 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: 6d47ff3

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.