maple-go-style

Go OpenTelemetry style for Maple: go.opentelemetry.io/otel SDK with otlptracehttp / otlploghttp / otlpmetrichttp exporters, inline endpoint + ingest key, semconv resource attributes including vcs.repository.url.full.

Quality

82%

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

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

An exemplary code-first skill: complete, executable Go covering install through span creation, with only genuinely non-obvious prose. The only soft spot is the absence of an explicit post-setup verification checkpoint and a signal-based shutdown example matching its own guidance.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code plus short, non-obvious facts Claude would not know ('the key is a project-scoped, write-only token (shaped like a Sentry DSN)', 'WithEndpoint takes a host without scheme, uses HTTPS, and appends the default /v1/<signal> path') — no padding and no explanation of concepts Claude already knows.	5 / 5
Actionability	Every section is copy-paste ready: the go get command, a complete Init function with all three providers, the main wiring, and a full span pattern with error recording and status — covering the common cases end to end.	5 / 5
Workflow Clarity	The sequence (install → bootstrap → wire in main → business spans → auto-instrumentation → coexistence) is clear and errors are propagated, but there is no explicit verification step (e.g. confirming telemetry reaches Maple) and the stated 'shut down on signal' is only shown as defer shutdown in the main example.	4 / 5
Progressive Disclosure	Sections are well organized and all inlined content earns its place for a single-file style skill; the auto-instrumentation library list and EU endpoint variants are borderline candidates for a small reference file, keeping it just short of fully optimal.	4 / 5
	Total	18 / 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.

A highly specific, well-differentiated description with concrete technical anchors, weakened mainly by the complete absence of any 'when to use this' trigger guidance. Adding a Use-when clause and a few natural-language synonyms would round it out.

Suggestions

Add an explicit trigger clause, e.g. 'Use when instrumenting a Go service for Maple, setting up OTel exporters, or sending traces/logs/metrics to Maple.'

Include natural user phrasings such as 'tracing', 'instrumenting', or 'observability setup for Go' alongside the SDK/exporter jargon.

Optionally name the observable outcomes (service map, spans, metrics dashboards) so users describing goals rather than SDK details can still trigger the skill.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities — 'go.opentelemetry.io/otel SDK with otlptracehttp / otlploghttp / otlpmetrichttp exporters, inline endpoint + ingest key, semconv resource attributes including vcs.repository.url.full' — matching the comprehensive-coverage anchor with no generic filler.	5 / 5
Completeness	The 'what' is clear and specific (which SDK, which exporters, which attributes), but there is no 'Use when...' clause or equivalent trigger guidance — 'when' is only weakly implied by the Maple brand, which the judging guidelines cap at 3.	3 / 5
Trigger Term Quality	Terms like 'Go', 'OpenTelemetry', 'Maple', and the otlp exporter names are natural for developers setting up telemetry, but common phrasings users would actually say — 'tracing', 'instrumenting', 'spans', 'logs/metrics setup' — are absent, so it sits between the good-coverage and comprehensive-synonym anchors.	4 / 5
Distinctiveness Conflict Risk	'Go OpenTelemetry style for Maple' names a tight niche (language + vendor + telemetry type) with distinct triggers, so it is unlikely to fire for unrelated skills.	5 / 5
	Total	17 / 20 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-go-style/SKILL.md
Commit: 1a03fa7

Reviewed: 10 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.