CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

observability

Agent observability, evals, feedback, and experiments. Use when adding observability dashboards, configuring trace capture, setting up evals, creating A/B experiments, or collecting user feedback on agent responses.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/observability/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

Highly actionable and information-dense, with executable code for every major feature, but it reads as an inlined reference manual rather than a skill overview. Splitting the API/tracking detail into reference files and tightening the SKILL.md core would materially improve token efficiency and navigation.

Suggestions

Move the Tracking Bridge constraints, Live OpenTelemetry span tables, and API endpoint/SQL table listings into reference files (e.g. references/tracking.md, references/api.md) and keep SKILL.md as a concise overview with well-signaled links.

Add explicit validation checkpoints to the workflows that do exist (e.g. verify an experiment is "running" and has assignments before computing results; confirm a promoted eval passes before relying on it as a CI gate).

Trim rationale prose in the inferred-sentiment and failure-report sections to the operative rules, cutting roughly a third of the current body length.

DimensionReasoningScore

Conciseness

The content is project-specific rather than padding with known concepts, but at ~500 lines it includes long inline sections (the Tracking Bridge constraint list, OTel span enumerations, inferred-sentiment failure taxonomy) that noticeably exceed SKILL.md's needs and could be tightened or moved to reference files.

3 / 5

Actionability

Copy-paste ready, complete code throughout: the defineAppConfig observability block, defineEval example, insertExperiment/updateExperiment lifecycle, dashboard route component, plus concrete CLI commands ("agent-native eval promote <runId> --write ...") and full endpoint/SQL/file tables — covering the common cases fully.

5 / 5

Workflow Clarity

Some sequences are clear (experiment lifecycle: insert → status "running" → POST results; promoting a run into a CI eval case), but the document is predominantly a descriptive reference with no validation checkpoints or feedback loops outside "truncated runs fail closed", fitting the steps-present-but-checkpoints-missing anchor.

3 / 5

Progressive Disclosure

Headers and tables give the body real structure, but hundreds of lines of API, SQL, and tracking reference are inlined that clearly belong in separate files, and pointers like "See the Evals doc" / "See the Observability doc" reference documents outside the bundle rather than well-signaled one-level-deep files.

3 / 5

Total

14

/

20

Passed

Description

88%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 strong description: third-person, concise, and explicit about both capabilities and trigger conditions. The only gaps are a few missing natural synonyms (monitoring, telemetry, tracing) and slight overlap risk with adjacent analytics/tracking skills.

DimensionReasoningScore

Specificity

Lists five concrete, specific actions — "adding observability dashboards, configuring trace capture, setting up evals, creating A/B experiments, or collecting user feedback" — with comprehensive coverage of the skill's domain, matching the top anchor; nothing is generic or padded.

5 / 5

Completeness

Explicitly answers both: what ("Agent observability, evals, feedback, and experiments") and when ("Use when adding observability dashboards, configuring trace capture, setting up evals, creating A/B experiments, or collecting user feedback on agent responses") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural terms users would say ("observability dashboards", "trace capture", "evals", "A/B experiments", "user feedback", "agent responses") but omits common synonyms such as "monitoring", "telemetry", "tracing", or "analytics", so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Has a clear agent-observability niche with distinct triggers, but "evals" and "feedback" carry minor overlap risk with closely related testing/tracking skills (the body itself references a separate tracking skill), so it is mostly rather than fully distinct.

4 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (520 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

12

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/observability/SKILL.md

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.