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

83%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a tight, executable reference implementation that assumes Claude's competence and wastes few tokens. Sections are logically ordered and self-contained, making it easy to follow from install to runtime instrumentation.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward with no padding explaining what OpenTelemetry is; prose like 'Go does not have framework-level auto-discovery' adds only non-obvious, earned context.	3 / 3
Actionability	Provides copy-paste-ready install commands and a complete, executable Init() implementation wiring all three exporters, plus a concrete span example and main() wiring.	3 / 3
Workflow Clarity	Ordered sections (Install → Bootstrap → Wire from main → Bounded spans → Auto-instrumentation → Coexistence) give a clear sequencing, and the setup is non-destructive so missing validation checkpoints do not cap the score.	3 / 3
Progressive Disclosure	Single self-contained file with well-organized, clearly headed sections and no nested references; no bundle files are needed or referenced for this style/bootstrap skill.	3 / 3
	Total	12 / 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 well-differentiated, naming the exact SDK, exporters, and resource attributes involved. Its main weakness is the absence of an explicit 'Use when...' trigger, which leaves the invocation context implicit.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when instrumenting a Go service to ship traces, logs, and metrics to Maple.'

Broaden trigger terms with natural variations users would say, such as 'tracing', 'telemetry', 'instrument Go service', or 'Maple ingest'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete configurations — 'otlptracehttp / otlploghttp / otlpmetrichttp exporters, inline endpoint + ingest key, semconv resource attributes including vcs.repository.url.full' — rather than vague language.	3 / 3
Completeness	It clearly states what the skill does (SDK + exporter + resource attribute setup) but provides no 'Use when...' clause or equivalent explicit trigger guidance, so the 'when' is only implied.	2 / 3
Trigger Term Quality	'Go OpenTelemetry style for Maple' surfaces relevant keywords a user might say, but coverage is thin and lacks common natural variations like 'tracing', 'logs', 'metrics', or 'instrument Go service'.	2 / 3
Distinctiveness Conflict Risk	'Go OpenTelemetry style for Maple' carves a clear, narrow niche with distinct triggers that are unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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: 8d347f8

Reviewed: about 12 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.