maple-onboarding-style

General OpenTelemetry onboarding style for Maple: native APIs, signal quality, inline keys, VCS resource attributes, LLM metrics, and smoke checks.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

75%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 a well-structured, actionable OTel onboarding style guide with executable examples and a clear logical flow ending in a smoke-check validation step. The main gaps are minor: a few justificatory passages could be tightened, full SDK init code is described rather than shown, and the longer subsections could be split into reference files.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes OTel competence (no 'what is OpenTelemetry' padding); Maple-specific rationale like 'project-scoped + write-only (Sentry DSN shaped)' earns its place, fitting 'efficient; minor instances of over-explanation'; not a 5 because a few justificatory sentences could be trimmed.	4 / 5
Actionability	Concrete executable TypeScript examples (withSpan, llmInputTokens.add) and specific attribute/env-var names give mostly copy-paste-ready guidance, matching 'mostly executable guidance; concrete code with minor gaps'; not a 5 because full SDK bootstrap/init code is described rather than shown as a complete block.	4 / 5
Workflow Clarity	Sections follow a logical onboarding order (APIs/naming -> endpoint/key -> VCS attributes -> signals -> LLM metrics -> smoke checks), with the smoke-check section acting as an explicit validation checkpoint, matching 'clear sequence with most checkpoints present'; not a 5 because intermediate validation steps are implicit rather than enumerated as a feedback loop.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested or buried references and no bundle files present, matching 'good structure; most content appropriately placed'; not a 5 because at ~127 lines some detailed subsections (e.g. LLM metrics) could be offloaded to reference files, and it exceeds the under-50-line simple-skill exception.	4 / 5
	Total	16 / 20 Passed

Description

58%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 clearly niched to Maple OTel onboarding, but it omits any explicit 'Use when...' trigger guidance, which caps completeness and weakens trigger-term quality. Adding a concrete trigger clause would lift the two lowest dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when onboarding OpenTelemetry/OTel into a Maple project, or when the user mentions Maple ingest keys, OTel resource attributes, or LLM telemetry setup.'

Add natural synonyms users actually say ('OTel', 'instrumenting', 'tracing setup') alongside the technical terms to improve trigger-term coverage.

Reconsider the leading 'General' qualifier, which slightly broadens the niche and raises overlap risk with generic observability skills.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists several concrete coverage areas ('native APIs, signal quality, inline keys, VCS resource attributes, LLM metrics, and smoke checks'), matching the 'lists several specific actions; minor gaps' anchor; not a 5 because the items are topical areas rather than fully fleshed concrete actions.	4 / 5
Completeness	A clear 'what' is stated ('General OpenTelemetry onboarding style for Maple: ...') but the 'when' is entirely missing with no 'Use when...' clause, which per the guidelines caps completeness at 3; not a 2 because the 'what' is concrete rather than vague.	3 / 5
Trigger Term Quality	Relevant domain terms ('OpenTelemetry', 'Maple', 'onboarding') appear but the phrasing leans technical and lacks the natural trigger variations a user would say, fitting 'some relevant keywords but missing common variations'; not a 4 because no natural 'Use when...' trigger phrases are present.	3 / 5
Distinctiveness Conflict Risk	The Maple-specific OpenTelemetry onboarding niche is clearly distinguished with minimal overlap risk, matching 'mostly distinct; minor overlap risk'; not a 5 because the leading word 'General' and broad OTel scope leave slight overlap with generic observability skills.	4 / 5
	Total	14 / 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-onboarding-style/SKILL.md
Commit: 3cb9193

Reviewed: 1 day 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.