maple-python-style

Python OpenTelemetry style for Maple: module-scope tracers/meters, decorators for bounded work, error spans, OTLP-bridged logs via LoggingHandler + LoggingInstrumentor, inline endpoint + ingest key, and no helper-API wrappers.

Quality

84%

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

Quality

Content

93%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 excellent, dense style guide: copy-paste-ready code, crisp prescriptive rules, and clean section organization with no filler. The only minor weakness is that the end-to-end adoption sequence is implied by section order rather than stated as an explicit workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and prescriptive — every line is a rule ('Acquire OTel objects at module scope', 'Do not use detached tracer.start_span(...); span.end()') or code, with no explanations of concepts Claude already knows and no padding.	5 / 5
Actionability	Fully executable throughout: a pip install command, a complete copy-paste telemetry.py init module, decorator/context-manager/error-path examples, and a FastAPI instrumentation snippet cover the common cases with real, runnable code.	5 / 5
Workflow Clarity	Each section gives unambiguous guidance and the FastAPI section fixes import ordering ('Import telemetry ... before any other module that needs tracing'), but the overall setup sequence (install → init → instrument) is distributed across sections rather than presented as an explicit ordered workflow with checkpoints.	4 / 5
Progressive Disclosure	The document is a single well-organized style guide with clear section headers, no nested references (the only pointer, to sibling skill maple-onboarding-style, is one level deep), and content appropriately kept inline; navigation is easy.	5 / 5
	Total	19 / 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, well-differentiated description that precisely enumerates the style's rules down to class names, but it omits any 'when to use this' trigger guidance. Adding an explicit use-when clause with natural trigger terms would raise it to the top level.

Suggestions

Append an explicit trigger clause such as 'Use when instrumenting a Python service with OpenTelemetry for Maple, or when the user mentions Maple, tracing, or telemetry setup.'

Include natural user-facing terms users would actually say — 'telemetry', 'instrumentation', 'tracing', 'observability' — to improve trigger term coverage.

Briefly state when NOT to use it (e.g. non-OTel logging setups or other vendors) to further sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities with specific implementation names — 'module-scope tracers/meters', 'error spans', 'OTLP-bridged logs via LoggingHandler + LoggingInstrumentor', 'inline endpoint + ingest key' — covering the style comprehensively with no real gaps, matching the top anchor.	5 / 5
Completeness	It clearly answers 'what' (a prescriptive OTel style for Maple) but contains no 'Use when…' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Good keyword coverage ('Python', 'OpenTelemetry', 'tracers', 'meters', 'spans', 'logs'), but natural user phrasings like 'telemetry', 'instrumentation', 'tracing', or 'observability' are absent, so a few common terms a user would say are missing.	4 / 5
Distinctiveness Conflict Risk	'Python OpenTelemetry style for Maple' carves a clear niche — one vendor, one language, one library — with named components, making it highly distinguishable from other skills with minimal conflict risk.	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-python-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.