CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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, @maple-dev/browser on the client.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

75%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 a strong, dense style guide: fully executable code for server, client, logs, and LLM instrumentation, with genuinely non-obvious version and ecosystem gotchas. Its weaknesses are duplicated version-compatibility notes and version-conditional details scattered through prose, plus an inlined second bootstrap example that could be deferred or trimmed.

Suggestions

State the @vercel/otel v1/v2 logRecordProcessor (singular vs plural) guidance once — it currently appears in both the prose after the first example and the Route handlers section — ideally in a short "Version compatibility" subsection.

Consolidate version-conditional details (@vercel/otel 1.x/2.x, older @opentelemetry/sdk-logs signatures, Next.js 15.3+, OTel JS 3.x overrides) into one place so the main flow stays lean and the version notes are easy to maintain.

Trim the second full bootstrap example to just the deltas from the first (instrumentations, logRecordProcessors) instead of repeating the exporter and registerOTel boilerplate.

DimensionReasoningScore

Conciseness

The body mostly avoids padding and assumes competence (no basic OTel/Next.js explanations), but it includes tightening targets: the @vercel/otel v1/v2 logRecordProcessor note is stated twice in near-identical words ("If the installed types are v1, use `logRecordProcessor` (singular)" and "`@vercel/otel@1.x` takes `logRecordProcessor` (singular), `@vercel/otel@2.x` takes `logRecordProcessors` (plural)"), and version-conditional details ("@vercel/otel 2.x", "Next.js 15.3+", "OpenTelemetry JS 3.x", older sdk-logs releases) are woven through prose rather than consolidated. Per the guidelines, inline version-specific information penalizes conciseness unless placed in a dedicated compat/deprecated section, so this fits anchor 3 ("mostly efficient but could be tightened") better than anchor 4.

3 / 5

Actionability

Every section ships complete, executable TypeScript with real imports: the registerOTel bootstrap, the OpenInference + log-exporter variant, the native @opentelemetry/api route handler with span status and metrics, the instrumentation-client.ts init, and the api-logs emit call. The examples are copy-paste ready and cover the common cases (server bootstrap, LLM instrumentation, route spans, structured logs, client init), matching anchor 5.

5 / 5

Workflow Clarity

The flow is clearly sequenced — server bootstrap, route-handler spans, client init, then inline config — and includes explicit validation: "Smoke-check with tools already in the repo (`npm run typecheck`, `npm run build`), plus a real app request where practical" and "Check the installed `.d.ts`" for the log-processor form. It stops short of anchor 5's feedback loops/error-recovery checkpoints (no fix-and-revalidate cycle for a failing smoke check), and is not a destructive/batch workflow, so no cap applies.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the body is well-organized with clear sections (bootstrap, Route handlers, Client side, Configuration and smoke) at ~150 lines. Cross-references to sibling skills are clearly signaled ("Navigation spans, error boundaries and linking the page load to the server render are in `maple-frontend-tracing` (`frameworks/nextjs.md`); follow it rather than this minimal init"), and detail is appropriately deferred to them. Minor gap: the advanced OpenInference variant is a second full bootstrap example inlined in the main file, so structure is good but not the ideal split of anchor 5.

4 / 5

Total

16

/

20

Passed

Description

66%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 highly specific and technically dense, naming exact files, packages, and constraints that make it largely self-describing and distinct. Its main weakness is the absence of any explicit 'Use when...' trigger guidance and of common natural synonyms like tracing or observability, leaving the 'when' only implied.

Suggestions

Add an explicit trigger clause, e.g. "Use when instrumenting a Next.js app on Vercel for Maple tracing — setting up instrumentation.ts, exporters, or client-side telemetry."

Include natural synonyms users would say, such as "tracing", "telemetry", "observability", and "monitoring", alongside the package names.

Briefly disambiguate from sibling skills (e.g. note that non-Next.js apps follow maple-onboarding-style and frontend details live in maple-frontend-tracing) to reduce overlap risk.

DimensionReasoningScore

Specificity

The description enumerates concrete, verifiable elements — "instrumentation.ts", "@vercel/otel bootstrap", "native @opentelemetry/api call sites", "inline endpoint + ingest key", "no raw NodeSDK replacement", "@maple-dev/browser on the client" — which is several specific items with only minor gaps. It falls short of anchor 5 because these are named components/technologies rather than comprehensive concrete actions (no verbs describing what the skill does with them), and it is above anchor 3's "1-2 concrete actions".

4 / 5

Completeness

The "what" is clear and concrete (Next.js/Vercel OpenTelemetry instrumentation style for Maple), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied by the technology names. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3; it cannot score 4 without an explicit 'when'.

3 / 5

Trigger Term Quality

Natural keywords a user would say are present: "Next.js", "Vercel", "OpenTelemetry", "instrumentation.ts", "Maple". A few common variations are missing — "tracing", "telemetry", "observability", "monitoring" — which keeps it out of anchor 5's comprehensive synonym coverage, but coverage is clearly better than anchor 3's partial set.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and narrow (Maple + Next.js/Vercel + OpenTelemetry instrumentation), so it is mostly distinct with minimal conflict risk against generic skills. However, the skill body references sibling skills ("maple-onboarding-style", "maple-frontend-tracing") covering adjacent Maple instrumentation territory, and the description does not disambiguate against them — minor overlap risk with closely related skills, fitting anchor 4 rather than anchor 5.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

MapleTechLabs/maple

Path

skills/maple-nextjs-style/SKILL.md

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.