CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/maple-effect-style/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The content is highly actionable with copy-paste executable examples for every runtime and a clear, well-sectioned structure. It is mostly concise, with only minor over-explanation in the env-var/auto-detection prose.

DimensionReasoningScore

Conciseness

Lean body dominated by executable code with genuinely non-obvious notes (e.g., ingest-key no-op behavior); the auto-detection/env-var paragraph could be tightened but is efficient overall.

4 / 5

Actionability

Copy-paste ready, fully executable examples for server, Cloudflare, and browser entry points plus spans, logs, and coexistence — covering the common cases concretely.

5 / 5

Workflow Clarity

Clear sequencing of entry-point selection per runtime with explicit must-dos (e.g., 'ctx.waitUntil(telemetry.flush(env))'); no destructive or batch operations require validation feedback loops.

4 / 5

Progressive Disclosure

No bundle files exist, so all content lives inline in a single ~144-line doc, but it is well-organized into clearly signaled sections (Install, Bootstrap, Custom spans, Logs, Coexistence).

4 / 5

Total

17

/

20

Passed

Description

75%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.

The description is specific and highly distinctive with concrete named APIs and runtimes, but it lacks an explicit 'Use when…' trigger clause, which caps its completeness. Trigger-term coverage is strong but leans technical rather than conversational.

Suggestions

Append an explicit 'Use when…' clause naming natural user phrases (e.g., 'Use when instrumenting an Effect app with Maple tracing, adding spans, or wiring OpenTelemetry for Effect').

Add conversational synonyms users would actually say — 'tracing', 'spans', 'OTLP' — alongside the API names to improve trigger-term quality.

DimensionReasoningScore

Specificity

Lists multiple concrete named APIs — 'Maple.layer() bootstrap', 'Effect.withSpan / Effect.annotateCurrentSpan call sites', 'Effect.log for trace-correlated logging' — plus three explicit runtimes, giving comprehensive coverage.

5 / 5

Completeness

Has a clear 'what' (the style and concrete call sites), but there is no 'Use when…' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Good keyword coverage ('Effect-TS', 'OpenTelemetry', 'Maple', '@maple-dev/effect-sdk') but jargon-heavy and missing natural synonyms a user might say like 'tracing' or 'spans'.

4 / 5

Distinctiveness Conflict Risk

Combines the narrow 'Maple' + 'Effect-TS' + 'OpenTelemetry' + specific SDK niche, making it clearly distinguishable with minimal conflict risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MapleTechLabs/maple
Reviewed

Table of Contents

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.