CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

82%

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

SKILL.md
Quality
Evals
Security

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.

The content is an exemplary, dense style guide: complete executable code, crate-specific gotchas Claude would not know, and explicit error-handling and coexistence guidance with no filler. The only notable gaps are a missing post-setup verification step and no use of external reference files for secondary detail.

DimensionReasoningScore

Conciseness

The body is lean and almost entirely non-obvious knowledge: version pairing rules ("pair tracing-opentelemetry with the release built for it (0.33 for 0.32)"), the blocking-client requirement ("The async reqwest-client panics there with 'there is no reactor running'"), and the TLS gap ("opentelemetry-otlp builds reqwest without default TLS"). There is no padding or explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Fully executable, copy-paste-ready guidance: a complete Cargo.toml dependency block, a full bootstrap function, the main() call/shutdown pattern, and an instrumented span example with concrete field syntax. The guidance covers the common cases (traces, logs, metrics, error handling, coexistence with existing exporters).

5 / 5

Workflow Clarity

The sections imply a clear, correct sequence — dependencies, bootstrap module, call from main with shutdown on exit, then instrument business spans — with explicit error-handling checkpoints ("A telemetry setup error is logged, never fatal"). It falls short of 5 only because there is no explicit verification step (e.g., how to confirm telemetry is arriving in Maple) after setup.

4 / 5

Progressive Disclosure

No bundle files exist and the body is well-organized into four clearly headed sections (Cargo.toml, Bootstrap, Bounded business spans, Coexistence), each appropriately placed. It is not a 5 under the rubric's simple-skill exception because the body exceeds 50 lines and some secondary detail (e.g., coexistence rules, exporter configuration notes) could be split into a reference file.

4 / 5

Total

18

/

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 specific, dense with concrete technical detail, and highly distinct thanks to the Maple + Rust OpenTelemetry niche. Its main weakness is the missing explicit "when to use" trigger clause, which caps completeness and slightly weakens trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g., "Use when instrumenting a Rust service with tracing/OpenTelemetry to send telemetry to Maple, or when the user mentions Maple, OTel, or telemetry setup in Rust."

Add natural synonyms users would say — "telemetry", "observability", "instrumentation", "OTel" — to improve trigger-term coverage.

Consider mentioning log and metric export (via opentelemetry-appender-tracing) alongside traces so the capability list is comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete components and choices — "opentelemetry + opentelemetry_sdk + opentelemetry-otlp HTTP exporter", "tracing-opentelemetry bridge for the tracing crate", "inline endpoint + ingest key", "semconv resource attributes" — which map to specific, actionable capabilities rather than vague claims. It stops short of a 5 because the items are components of a style rather than an exhaustive set of actions (e.g., logs/metrics export via opentelemetry-appender-tracing is not mentioned).

4 / 5

Completeness

The "what" is clear and specific (a Rust OpenTelemetry style for Maple with named components), but there is no "Use when..." clause or equivalent explicit trigger guidance; when the skill should be used is only weakly implied by the topic naming. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural-term coverage: "Rust", "OpenTelemetry", "tracing", "Maple", "HTTP exporter", "ingest key" are words a user with this need would plausibly say. A few natural variations are missing — "telemetry", "observability", "instrumentation", "OTel" — which keeps it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The pairing of "Maple" with "Rust OpenTelemetry" carves out a clear niche, making false triggers unlikely for unrelated skills. It is not a 5 because generic OpenTelemetry or Rust telemetry requests could still match this skill's terms in the absence of an explicit "use when the project targets Maple" trigger.

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-rust-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.