maple-effect-style

Effect-TS OpenTelemetry style for Maple via @maple-dev/effect-sdk: Maple.layer() bootstrap, Effect.withSpan / Effect.annotateCurrentSpan call sites, Effect.log for trace-correlated logging, server / browser / Cloudflare entry points.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

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

The body is lean, fully actionable, and well-structured, with executable examples for every runtime and clear gotcha callouts where traces would silently fail.

Dimension	Reasoning	Score
Conciseness	Lean and technical throughout; it assumes Claude knows OpenTelemetry/Effect and only adds Maple-specific gotchas (env-var fallbacks, flush() requirement), with every line earning its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript for server, Cloudflare, browser, custom spans, logs, and coexistence — concrete rather than abstract guidance.	3 / 3
Workflow Clarity	Sequences the runtime entry-point decision clearly ('Pick the entry point per runtime') with per-runtime sections and explicit gotcha callouts; no destructive/batch operations require validation checkpoints here.	3 / 3
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-organized into focused sections (Install, Bootstrap, Custom spans, Logs, Coexistence) that serve as a clean overview.	3 / 3
	Total	12 / 12 Passed

Description

67%

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

The description is specific and highly distinctive, but it omits an explicit 'Use when' trigger clause and relies on technical vocabulary over natural user phrasing.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers (e.g. 'Use when adding OpenTelemetry tracing or telemetry to an Effect-TS app on Maple').

Surface common user phrasings like 'tracing', 'telemetry', and 'spans' alongside the Effect-native primitive names.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Maple.layer() bootstrap', 'Effect.withSpan / Effect.annotateCurrentSpan call sites', 'Effect.log for trace-correlated logging', and server/browser/Cloudflare entry points — rather than vague language.	3 / 3
Completeness	Clearly answers what the skill does, but there is no explicit 'Use when...' trigger clause, so 'when' is only implied — capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Includes domain terms (OpenTelemetry, Effect-TS, Maple, span, logging) but leans on technical jargon and misses common natural variations a user might say such as 'tracing' or 'telemetry'.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Effect-TS OpenTelemetry for Maple via a named @maple-dev/effect-sdk) with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	10 / 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-effect-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.