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

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/maple-go-style/SKILL.md

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 and well-structured, with executable code throughout and a clear bootstrap sequence. Its main weaknesses are a time-sensitive hardcoded semconv version pin and a small inconsistency between the promised signal-based shutdown and the deferred shutdown in code.

Suggestions

Replace the hardcoded `semconv/v1.24.0` import with guidance to use the latest stable semconv package, or move the pinned version into an explicit 'version pin' note so it does not silently age.

Reconcile the 'shut down on signal' statement in the intro with the `defer shutdown(ctx)` pattern in the code, or show the signal-based shutdown snippet.

Consider extracting the long Init block into a `references/bootstrap.go` file referenced from the body, to keep SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — install commands, a single Init function, a wiring snippet, and a span example with minimal prose — but the hardcoded 'semconv/v1.24.0' version pin is time-sensitive and not isolated in a deprecated/old-patterns section, which keeps it off the top anchor.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance: a `go get` block, a complete `Init` function with all three exporters wired, a `main` wiring snippet, and a working span example covering the common instrumentation cases.	5 / 5
Workflow Clarity	A clear sequence is present (Install → Bootstrap → wire from main → bounded spans → auto-instrumentation → coexistence) with shutdown handled, but there is a minor gap: the intro says 'shut down on signal' while the code uses `defer shutdown(ctx)`, and signal-handling is not shown.	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and no nested or buried references; no bundle files exist so there is nothing to offload, but the bootstrap code block is long enough that it sits just below the ideal top anchor rather than at it.	4 / 5
	Total	17 / 20 Passed

Description

62%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 clearly distinct, but it is written as a technical recipe rather than a trigger-oriented description: it lacks a 'Use when...' clause and leans on jargon over natural user phrases.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when instrumenting a Go service for Maple telemetry or when the user asks to set up Maple tracing/logs/metrics in a Go app.'

Soften the jargon with one natural synonym a user would actually say (e.g. 'tracing', 'logs', 'metrics' alongside the otlp exporter package names).

Lead with the capability in plain terms ('Instrument a Go service for Maple tracing, logs, and metrics') before the package-level specifics.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete specifics — 'otlptracehttp / otlploghttp / otlpmetrichttp exporters', 'inline endpoint + ingest key', 'semconv resource attributes including vcs.repository.url.full' — but it describes config shape rather than a comprehensive list of actions, so it sits just below the top anchor.	4 / 5
Completeness	It clearly answers 'what' (Go OTel style for Maple with specific exporters and resource attributes) but has no 'Use when...' or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'Go OpenTelemetry' and 'Maple' are relevant keywords, but the rest is heavy technical jargon (exporter package paths, 'semconv', 'vcs.repository.url.full') with none of the natural phrases a user would actually say like 'instrument my Go service' or 'set up tracing'.	3 / 5
Distinctiveness Conflict Risk	The 'for Maple' scope plus the specific exporter/resource-attribute recipe carves a clear niche that is unlikely to trigger for a generic OpenTelemetry or general Go instrumentation skill.	5 / 5
	Total	15 / 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: 3cb9193

Reviewed: 1 day 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.