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.

66

Quality

78%

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

82%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 body is an efficient, highly actionable style guide with executable examples across all major topics and clean section organization. It slightly over-explains rationale in a few places and inlines a large init block that could be split out, but is otherwise strong.

Suggestions

Tighten the rationale prose (e.g. the ingest-key paragraph) to the essential 'why' to improve token efficiency.

Consider moving the full telemetry.py init module into a reference file with a concise inline excerpt, keeping SKILL.md as a tighter overview.

DimensionReasoningScore

Conciseness

Lean and code-forward with no padding on concepts Claude already knows; the few rationale sentences (e.g. justifying inline ingest key over env) earn their place but could be trimmed slightly.

4 / 5

Actionability

Provides copy-paste-ready, executable code for tracers/meters, decorators, context managers, error recording, the full init module, and FastAPI instrumentation, covering the common cases concretely.

5 / 5

Workflow Clarity

Sections are clearly organized by topic (bounded work, error paths, logs, init, metrics, FastAPI) with sequencing guidance like 'Import telemetry before any other module that needs tracing'; no explicit validation checkpoints, but none are needed for a non-destructive style guide.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and no bundle files to navigate; the large inlined init module is central content, though it could arguably live in a reference file.

4 / 5

Total

17

/

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.

The description is specific and well-scoped to a clear niche, listing concrete conventions rather than vague fluff. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when instrumenting a Python service for Maple tracing/logs/metrics.'

Include common natural trigger terms users might say, such as 'tracing', 'instrumentation', or 'spans', alongside the technical names.

DimensionReasoningScore

Specificity

Lists multiple concrete style actions—'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'—giving comprehensive coverage of the skill's conventions.

5 / 5

Completeness

Has a clear, detailed 'what' but no explicit 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Includes accurate technical terms a user needing this skill would say ('OpenTelemetry', 'tracers/meters', 'error spans', 'OTLP-bridged logs'), but misses common natural variations like 'tracing', 'instrumentation', or 'spans' on their own.

4 / 5

Distinctiveness Conflict Risk

The niche 'Python OpenTelemetry style for Maple' is tightly scoped to a specific platform, language, and library, giving it distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

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.

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.