CtrlK
BlogDocsLog inGet started
Tessl Logo

sematext/sematext-otel

Wire a service's OpenTelemetry (OTel) output to Sematext Cloud for observability and monitoring. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext or sending telemetry to Sematext.

79

Quality

99%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

100%Weight 40%Scale 1-3

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

A high-quality onboarding skill body: actionable env-var artifacts, a sequenced workflow with a verification loop, and Sematext-specific gotchas that Claude would not already know. Hard agent constraints (never handle tokens, never run sudo) are clearly stated and reinforce safe behavior.

DimensionReasoningScore

Conciseness

Lean and domain-specific — the prose teaches only Sematext particulars Claude would not know (X-API-TOKEN vs Bearer, region-bound tokens, agent ports) and omits generic OTel concepts; every table and block earns its place.

3 / 3

Actionability

Copy-paste-ready env-var blocks with placeholders intact, an exact endpoint/protocol matrix, per-signal port table, and literal sudo commands — fully executable guidance rather than description.

3 / 3

Workflow Clarity

Clear Triage → Assemble → Point → Verify sequence with an explicit validation checkpoint ("confirm data lands within 60s") and a retry feedback loop ("loop until it does… if two passes produce no data, drop to the narrowest test").

3 / 3

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized into clear sections and signals one-level-deep external references via the per-language path table and the e2e table, with no nested pointer chains.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 strong description: third-person voice, concrete capabilities, explicit invoke-when trigger, and a distinct niche. It avoids fluff and over-claims while naming the key decision axes (region, App-type, flow, signals).

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Wire a service's OpenTelemetry (OTel) output to Sematext Cloud", "produces the exact env-var block", "points at a runnable reference example" — matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers both what (wire OTel output, produce env-var block, point at reference) and when via the "Invoke when instrumenting a new app for Sematext or sending telemetry to Sematext" trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — "OpenTelemetry (OTel)", "Sematext Cloud", "observability and monitoring", "instrumenting a new app", "sending telemetry" — with good variation.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Sematext OTel onboarding) with Sematext-specific triggers, making it unlikely to fire for unrelated telemetry skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 suspicious

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents