CtrlK
BlogDocsLog inGet started
Tessl Logo

maple-nextjs-style

Next.js / Vercel OpenTelemetry style for Maple: instrumentation.ts, @vercel/otel bootstrap, native @opentelemetry/api call sites, inline endpoint + ingest key, no raw NodeSDK replacement.

60

Quality

70%

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-nextjs-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 body is highly actionable with executable, version-aware code and clear opinionated guidance; conciseness and workflow/structure are strong with only minor room to tighten and add an explicit validation feedback loop.

DimensionReasoningScore

Conciseness

Code-forward and opinionated with minimal re-explanation of concepts Claude already knows; a few explanatory sentences earn their place but could be trimmed slightly, matching the 'efficient; minor over-explanation' anchor.

4 / 5

Actionability

Multiple fully executable, copy-paste-ready code blocks (bootstrap, Anthropic/OpenInference instrumentation, route handlers, OTel logging) plus version-specific v1/v2 guidance, matching the 'fully executable; covers common cases' anchor.

5 / 5

Workflow Clarity

Concrete smoke checks (npm run typecheck / build, real request) and explicit do/don't guidance give a clear actionable sequence, but no explicit validate->fix->retry feedback loop; matches the 'clear sequence, most checkpoints present; minor gaps' anchor.

4 / 5

Progressive Disclosure

Well-organized into headed sections with appropriately scoped single-file content and no bundle files to split out; minor organization gaps (e.g. Anthropic instrumentation vs route handlers could be separate references), matching the 'good structure; minor gaps' anchor.

4 / 5

Total

17

/

20

Passed

Description

58%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 technically specific and clearly distinct, but lacks an explicit 'Use when...' trigger clause and natural trigger phrases, capping completeness and trigger-term quality at 3.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when instrumenting a Next.js/Vercel app for Maple traces and logs.'

Include natural user-facing trigger phrases or synonyms (e.g. 'OpenTelemetry setup', 'OTel bootstrap', 'traces and logs') beyond pure technical identifiers.

Surface the supported runtimes/languages scope explicitly so it is distinguishable from a sibling non-Next.js Maple OTel skill.

DimensionReasoningScore

Specificity

Names the domain and several concrete specifics (instrumentation.ts, @vercel/otel bootstrap, native @opentelemetry/api call sites, inline endpoint + ingest key, no NodeSDK replacement), matching the 'several specific actions; minor gaps' anchor; not a comprehensive broad action list so not 5.

4 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause, so per guideline completeness is capped at 3; matches the 'clear what, when missing or weakly implied' anchor.

3 / 5

Trigger Term Quality

Relevant technical keywords (Next.js, Vercel, OpenTelemetry) appear but common variations/synonyms and natural user phrases are missing, matching the 'some relevant keywords but missing variations' anchor; not strong enough for 4.

3 / 5

Distinctiveness Conflict Risk

Niche-specific (Next.js/Vercel OTel for Maple) with low overlap risk against other skills, matching the 'mostly distinct; minor overlap risk' anchor; not a perfectly self-contained trigger set so not 5.

4 / 5

Total

14

/

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.