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.

64

Quality

76%

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

85%

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 complete executable examples, clear prescriptive guidance, and clean section organization. The only weakness is moderate verbosity in the longer prose paragraphs, which could be condensed.

Suggestions

Tighten the long sentences in the route-handler and logging guidance into shorter imperatives or a bulleted list of do/don't rules.

Consider splitting the OpenInference/Anthropic instrumentation block into a short note plus an optional reference, since it adds a second large code block beyond the core bootstrap.

DimensionReasoningScore

Conciseness

It assumes Claude's competence and avoids basic-concept padding, but several long prescriptive sentences (the route-handler and logging guidance) could be tightened without losing meaning.

2 / 3

Actionability

Multiple complete, executable TypeScript code blocks (instrumentation.ts, route handler with withSpan, OTel log emission) that are copy-paste ready with real imports and values.

3 / 3

Workflow Clarity

As a style/pattern skill, each action is unambiguous and prescriptive, and the 'Configuration and smoke' section names concrete validation commands (npm run typecheck / build).

3 / 3

Progressive Disclosure

Self-contained with no bundle files or nested references, organized into clear sections (bootstrap, route handlers, configuration and smoke) that are easy to navigate.

3 / 3

Total

11

/

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 distinct, but it omits an explicit 'Use when...' trigger clause and leans on technical-spec phrasing over natural user keywords. Adding trigger guidance and plainer trigger terms would lift completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when...' clause stating when to apply this style (e.g. instrumenting a Next.js/Vercel app for Maple tracing).

Soften technical-spec phrasing with natural trigger terms users would actually say, such as 'tracing', 'telemetry', or 'observability for Next.js'.

Keep the concrete item list but lead with the user-facing intent before the implementation constraints.

DimensionReasoningScore

Specificity

Lists multiple concrete items — 'instrumentation.ts', '@vercel/otel bootstrap', 'native @opentelemetry/api call sites', 'inline endpoint + ingest key', 'no raw NodeSDK replacement' — rather than vague language.

3 / 3

Completeness

It states what the skill does but provides no 'Use when...' or equivalent explicit trigger guidance, so the 'when' side is only implied.

2 / 3

Trigger Term Quality

Domain keywords (Next.js, Vercel, OpenTelemetry, Maple) are present, but the phrasing reads as a technical spec ('@vercel/otel bootstrap', 'native @opentelemetry/api call sites') and omits common natural variations a user might say.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and specific (Maple Next.js/Vercel OpenTelemetry style), with triggers unlikely to collide with other skills.

3 / 3

Total

10

/

12

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.