CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/maple-python-style/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The body is a tight, highly actionable style guide with complete executable examples and clean section organization, assuming Claude's competence throughout. Its only gap is the absence of explicit validation/verification checkpoints for the instrumentation workflow.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's OTel/Python competence; the few prose rationales (inlining the ingest key, preserving existing logging) are project-specific justifications that earn their place rather than generic concept explanations.

3 / 3

Actionability

Provides complete, executable, copy-paste-ready examples for every concern, including a full telemetry.py init module, decorator/context-manager spans, error handling, and FastAPI instrumentation.

3 / 3

Workflow Clarity

Well-organized by concern with a clear ordered init sequence, but offers no validation/verification checkpoints or feedback loops, and the app-instrumentation process is not laid out as an explicit validated workflow.

2 / 3

Progressive Disclosure

Self-contained skill with no bundle files and no need for external references; content is cohesive and navigable via clear section headers, which the rubric permits to score 3 for skills needing no external refs.

3 / 3

Total

11

/

12

Passed

Description

67%

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 and distinctive, clearly scoped to Maple Python OpenTelemetry instrumentation, but it lacks an explicit "Use when..." trigger and leans heavily on implementation jargon over natural user keywords.

Suggestions

Append an explicit trigger clause, e.g. ".Use when instrumenting a Python service for Maple, adding traces/metrics/logs, or onboarding a Python app to Maple."

Soften jargon by adding natural phrasings users would say ("instrument", "tracing", "metrics", "telemetry setup") alongside the API names.

Lead with the user-facing purpose ("Instrument Python services to send traces, metrics, and logs to Maple") before listing the specific style rules.

DimensionReasoningScore

Specificity

Enumerates multiple concrete conventions ("module-scope tracers/meters", "decorators for bounded work", "error spans", "OTLP-bridged logs via LoggingHandler + LoggingInstrumentor", "inline endpoint + ingest key", "no helper-API wrappers") rather than vague language.

3 / 3

Completeness

Clearly answers "what" with detailed style rules but provides no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Carries recognizable domain keywords (Maple, OpenTelemetry, Python, logs) but is dominated by implementation jargon ("OTLP-bridged", "LoggingHandler + LoggingInstrumentor", "ingest key") and omits natural user phrasings like "instrument my Python app for Maple".

2 / 3

Distinctiveness Conflict Risk

"Python OpenTelemetry style for Maple" plus highly specific Maple-scoped rules (inline ingest key, no helper-API wrappers) carves a clear niche unlikely to trigger generic OTel skills.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MapleTechLabs/maple
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.