maple-nodejs-style

Plain Node.js (Express, Fastify, Hono, Bun) OpenTelemetry style for Maple: NodeSDK + --import bootstrap, native @opentelemetry/api call sites, inline endpoint + ingest key, OTLP HTTP exporters.

Quality

85%

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

87%

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

A tightly written, fully actionable Node.js OpenTelemetry skill: executable code throughout, no wasted tokens, and clean single-file organization. Its main gap is the absence of a verification checkpoint to confirm telemetry is actually reaching Maple.

Suggestions

Add an explicit validation step, e.g. after bootstrap check a trace arrives at the Maple UI or run a quick request and confirm logs carry a trace_id, so the workflow has a feedback loop.

Clarify the onboarding handoff: the 'MAPLE_KEY is set by maple-onboard skill' note would benefit from a one-line 'if missing, run maple-onboard first' checkpoint.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — it skips explaining what OpenTelemetry or the frameworks are and goes straight to executable bootstrap, rule, and handler code, with every line earning its place.	3 / 3
Actionability	Provides complete, executable TypeScript and a concrete bootstrap command ('node --import ./telemetry.js app.js'), plus copy-paste-ready handler and instrumentation snippets.	3 / 3
Workflow Clarity	The single bootstrap-then-run sequence is present, but there is no validation or verification checkpoint (e.g. confirming traces reach Maple), and these batch/deployment operations warrant a feedback loop per the scoring notes.	2 / 3
Progressive Disclosure	A short, well-organized single-file skill with clear sections (Bootstrap rules, Route handlers, Logs, Coexistence) and no bundle files — appropriate for a skill under 50 lines with no need for external references.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 precise, technically concrete description that nails specificity and distinctiveness, but it omits any explicit 'Use when...' trigger guidance, so it only implies the activation conditions rather than stating them. Adding a when-to-use clause would round it out.

Suggestions

Append an explicit trigger clause, e.g. 'Use when instrumenting a Node.js (Express, Fastify, Hono, or Bun) service to send telemetry to Maple via OTLP.'

Keep the named framework list but surface the most common phrasing a user would say (e.g. 'tracing', 'logs', 'metrics to Maple') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, specific actions: 'NodeSDK + --import bootstrap', 'native @opentelemetry/api call sites', 'inline endpoint + ingest key', and 'OTLP HTTP exporters' — no vague language.	3 / 3
Completeness	Clearly answers 'what' but lacks an explicit 'when/Use when' trigger clause, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Includes natural terms users would actually say — 'Node.js', 'Express, Fastify, Hono, Bun', 'OpenTelemetry', and 'Maple' — covering the relevant frameworks and the named platform.	3 / 3
Distinctiveness Conflict Risk	A narrow, well-defined niche (Maple + Node.js OpenTelemetry style) with distinct named frameworks makes it unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 12 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-nodejs-style/SKILL.md
Commit: 8d347f8

Reviewed: about 13 hours 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.