maple-java-style

Java OpenTelemetry style for Maple: zero-code Java agent or manual SDK with OTLP HTTP exporters, inline endpoint + ingest key, semconv resource attributes, OTLP-bridged Logback / SLF4J logs.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

76%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.

An exemplary lean, dense skill body: every line is non-obvious configuration guidance with executable commands and code, and the agent-vs-SDK decision is clearly conditioned. The two weak spots are the absence of any validation/verification step in the setup flow and the absence of file-level content splitting for the manual-SDK deep-dive.

Suggestions

Add a short verification step, e.g. 'After startup, check Maple's Traces view for service.name=orders-api, or curl the exporter endpoint and confirm a 200,' to close the workflow feedback loop.

Complete the elided exporter setup for OtlpHttpLogRecordExporter and OtlpHttpMetricExporter (the Logs section depends on the log exporter being wired).

Show the minimal <appender> declaration for logback.xml rather than describing it in prose, or move the manual SDK code block to a reference file and link it from a one-line pointer.

Dimension	Reasoning	Score
Conciseness	Zero padding: the body never explains what OpenTelemetry is and spends every sentence on non-obvious specifics ('The agent appends /v1/traces, /v1/logs, and /v1/metrics to the base endpoint', 'The agent does not read Spring's application.yml'), fully assuming Claude's competence.	5 / 5
Actionability	Fully concrete curl download, copy-paste JVM flag block, and complete Maven coordinates, plus a near-complete SDK init example; minor gaps are the elided log/metric exporters ('… same shape for OtlpHttpLogRecordExporter and OtlpHttpMetricExporter') and the logback.xml appender declaration described but not shown.	4 / 5
Workflow Clarity	The decision flow is well sequenced (agent first; SDK when 'GraalVM native image, embedded JVM, sealed module path'; then log bridging, business spans, coexistence rules), but there is no verification checkpoint, e.g. confirming traces actually reach Maple after setup.	3 / 5
Progressive Disclosure	Well-organized single-file skill with no nested or buried references (no bundle files exist to score against); the ~50-line manual-SDK section with Maven XML and Java code could live in a reference file to keep SKILL.md a leaner overview, which is the one minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

75%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.

A highly specific, lean description that clearly states what the skill covers and is strongly distinctive, but it omits any explicit 'when to use' trigger guidance, and common trigger vocabulary (traces, metrics, instrumentation) is missing. Adding a 'Use when…' clause would lift the two weakest dimensions.

Suggestions

Append a 'Use when…' clause, e.g. 'Use when setting up Maple telemetry for a Java or JVM service, or when the user mentions traces, metrics, or logs for a Java app.'

Include natural trigger synonyms such as 'tracing', 'metrics', 'instrumentation', and 'APM' so users phrasing the need colloquially still match.

Dimension	Reasoning	Score
Specificity	Names multiple concrete capabilities — 'zero-code Java agent', 'manual SDK with OTLP HTTP exporters', 'inline endpoint + ingest key', 'semconv resource attributes', 'OTLP-bridged Logback / SLF4J logs' — with comprehensive coverage of the skill's scope and no vague filler.	5 / 5
Completeness	The 'what' is clear and specific (agent or SDK setup, exporters, inline keys, resource attributes, log bridging), but there is no 'Use when…' clause or equivalent explicit trigger guidance, which caps completeness at 3.	3 / 5
Trigger Term Quality	'Java', 'OpenTelemetry', 'Maple', 'logs', and the 'Logback / SLF4J' synonym pair are natural user terms, but common trigger words a user would say — 'traces', 'metrics', 'tracing', 'instrumentation', 'telemetry' — are absent.	4 / 5
Distinctiveness Conflict Risk	'Java OpenTelemetry style for Maple' carves a narrow, unambiguous niche combining a specific vendor, language, and telemetry stack; it would not plausibly trigger the wrong skill.	5 / 5
	Total	17 / 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-java-style/SKILL.md
Commit: 1a03fa7

Reviewed: 11 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.