maple-rust-style

Rust OpenTelemetry style for Maple: opentelemetry + opentelemetry_sdk + opentelemetry-otlp HTTP exporter, tracing-opentelemetry bridge for the tracing crate, inline endpoint + ingest key, semconv resource attributes.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

87%

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

A highly actionable, lean style guide with copy-paste-ready code and good section organization. The only notable gap is the lack of an explicit verification step that telemetry is exporting correctly after bootstrap.

Suggestions

Add a verification checkpoint after init, e.g. emit a test span/log and confirm it appears in Maple before proceeding, to give the workflow an explicit validation loop.

Note how to confirm exporter build errors are surfaced (the init already returns Result) so Claude knows to handle init failure explicitly.

Dimension	Reasoning	Score
Conciseness	Lean and code-driven; it does not explain concepts Claude already knows and the large init block is the skill's core payload rather than padding, so each token earns its place.	3 / 3
Actionability	Provides a complete Cargo.toml dependency block, a copy-paste-ready bootstrap init function, and the main/shutdown wiring — fully executable guidance with no pseudocode.	3 / 3
Workflow Clarity	The sequence (add deps, write init, call from main, shut down providers) is clear, but there are no validation or verification checkpoints confirming telemetry actually exports, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	Single self-contained file organized into clear sections (Cargo.toml, Bootstrap, Bounded business spans, Coexistence) with no nested references and no content that obviously belongs in a separate file.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 specific, well-scoped description that clearly conveys the Maple Rust OpenTelemetry style. Its main gap is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up Rust telemetry for Maple services or when the user mentions OpenTelemetry/OTLP in a Maple Rust project.'

Keep the concrete crate and exporter details but surface the 'when' so Claude knows when to invoke this skill.

Dimension	Reasoning	Score
Specificity	Names multiple concrete components and choices — 'opentelemetry + opentelemetry_sdk + opentelemetry-otlp HTTP exporter', 'tracing-opentelemetry bridge', 'inline endpoint + ingest key', 'semconv resource attributes' — rather than vague language.	3 / 3
Completeness	It clearly states what the skill does (crate set, exporter, bridge, attributes) but lacks a 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Covers natural terms a user would say for this need — 'Rust OpenTelemetry', 'Maple', 'tracing crate', 'HTTP exporter' — with good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	The 'Rust OpenTelemetry style for Maple' niche is narrowly scoped with distinct triggers and is unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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-rust-style/SKILL.md
Commit: 8d347f8

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