maple-kotlin-style

Kotlin (Ktor, Spring Boot) OpenTelemetry style for Maple: zero-code Java agent or manual SDK with OTLP HTTP exporters, inline endpoint + ingest key, semconv resource attributes, OTLP-bridged logs.

Quality

85%

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

87%

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

A concise, highly actionable reference with executable agent and SDK examples and clean section organization. The main gap is the lack of an explicit sequenced workflow with validation checkpoints — it reads as a style reference rather than a guided procedure.

Suggestions

Add a short ordered procedure (e.g. 1. pick agent vs manual SDK by build type, 2. apply endpoint/key/resource flags, 3. verify traces arrive at Maple, 4. confirm logs carry trace_id) with an explicit validation/verification checkpoint.

Include a concrete verification command or check (e.g. how to confirm a span reached Maple or inspect trace_id in a log line) to close the feedback loop on the telemetry setup.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it explains only Maple-specific decisions ("inline endpoint + ingest key", "don't move them behind unset env vars", "Don't replace the user's existing logger") without re-explaining what OTel/Kotlin/JVM are, matching the level-3 anchor.	3 / 3
Actionability	It provides a copy-paste-ready agent invocation with concrete flags and a complete Kotlin SDK initializer plus a runnable span example, satisfying the level-3 anchor of fully executable, specific code.	3 / 3
Workflow Clarity	The sections are topical reference snippets rather than a sequenced multi-step process, and no validation/checkpoint feedback loop is given; only the coexistence note "Test the combination once before shipping" hints at verification, so it sits at level 2 (sequence/structure present but checkpoints missing) rather than level 3.	2 / 3
Progressive Disclosure	The body is a single short, well-organized file (~50 lines) with no bundle files needed and no nested references; per the rubric's simple-skills note, that earns a 3 even without external file references.	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 what the skill does and is unlikely to conflict with other skills. Its one weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness at 2.

Suggestions

Append an explicit trigger clause, e.g. "Use when instrumenting a Kotlin (Ktor/Spring Boot) service for Maple, or when the user mentions OpenTelemetry, OTLP, or tracing/logs for a Kotlin/JVM project."

Add common trigger phrasings users might say ("tracing", "telemetry", "spans", "trace_id") alongside the framework names to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities — "zero-code Java agent or manual SDK", "OTLP HTTP exporters", "inline endpoint + ingest key", "semconv resource attributes", "OTLP-bridged logs" — matching the level-3 anchor of multiple specific actions.	3 / 3
Completeness	It answers "what does this do" thoroughly but contains no "Use when..." clause or equivalent explicit trigger guidance, which the rubric says caps completeness at 2; it is not level 1 because the "what" is strong, and not level 3 because the "when" is entirely missing.	2 / 3
Trigger Term Quality	Natural terms a user would actually say are present ("Kotlin", "Ktor", "Spring Boot", "OpenTelemetry", "logs"); not merely internal jargon, so it sits at the good-coverage level rather than the partial-coverage level 2.	3 / 3
Distinctiveness Conflict Risk	The Maple/Kotlin/(Ktor, Spring Boot)/OpenTelemetry niche is sharply scoped with distinct triggers and is very unlikely to fire for an unrelated skill.	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-kotlin-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.