CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-graph

Creates observability dashboards and graphs from logs, traces, errors, sessions, metrics, and events data by previewing charts inline and saving them to a dashboard.

Quality

72%

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 ./skills/observability/create-graph/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured and highly actionable for an MCP-tool-driven skill, with a clear sequenced workflow and concrete validation checkpoints. Its main defects are a duplicated tool list (Prerequisites vs Capabilities) and a dangling reference to a missing enums.md file that undercuts both actionability and navigation. Fixing the duplication and shipping (or removing) enums.md would resolve both issues.

Suggestions

Remove the duplicated MCP tool list — "Capabilities" repeats "Prerequisites" almost verbatim; keep one (the Prerequisites version with the projectKey note) and delete the other.

Ship the referenced enums.md file in references/ (or inline its enum tables into the body) so the instructions "Use exact enum casing from enums.md" and "See enums.md" can actually be followed.

Add a brief error-recovery note to the workflow (e.g. "if a preview returns empty, re-run get-keys and verify the attribute name") to turn the Common-mistakes list into a feedback loop.

DimensionReasoningScore

Conciseness

The five MCP tools are listed twice with nearly identical descriptions — in "Prerequisites" ("get-dashboards — list existing dashboards; with dashboardId, get the full config...") and again in "Capabilities" — clear duplication that should be tightened. The rest of the body is lean with no over-explanation of concepts Claude already knows, so this matches anchor 3 rather than the "several padded sections" of anchor 2.

3 / 5

Actionability

Gives concrete, executable guidance: exact enum casings ("It's CountDistinct — PascalCase, no underscore"), the required column="" for Count, and the full ISO timestamp format ("2026-03-04T00:00:00Z"). It falls short of anchor 5 because there are no example tool-call payloads and the pointer "Use exact enum casing from enums.md" leads to a file that does not exist in the bundle.

4 / 5

Workflow Clarity

The six-step workflow is clearly sequenced with explicit checkpoints: get-keys before building a query, preview-and-confirm before create-graph, and per-graph confirmation for multiples. It stops short of anchor 5 because there is no explicit error-recovery loop (e.g. what to do when a preview returns empty or the API rejects a call) — failure modes are only listed after the fact in "Common mistakes" rather than wired into the workflow.

4 / 5

Progressive Disclosure

Sections are well-organized, but the body references enums.md twice ("Use exact enum casing from enums.md", "See enums.md") and the bundle contains no such file — a dangling reference the reader cannot follow. Scoring against the actual bundle structure (zero reference files), this matches anchor 3: the reference scheme is broken and enum reference content is only partially inlined in "Common mistakes", which is a navigation failure rather than the minor organization gaps of anchor 4.

3 / 5

Total

14

/

20

Passed

Description

66%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 third-person, with a concrete enumeration of data sources and actions. Its main weakness is the complete absence of any "when to use" trigger guidance, which caps completeness and limits trigger-term quality. Adding an explicit "Use when..." clause would lift it from good to strong.

Suggestions

Add an explicit trigger clause such as "Use when the user asks to visualize logs, traces, errors, sessions, metrics, or events data, or to build an observability dashboard" to fix the completeness gap.

Include a few natural synonym terms users would actually say — e.g. "visualization", "monitoring", "latency", "error rate" — to broaden trigger-term coverage.

Mention one or two more covered capabilities (e.g. duplicating existing graphs or discovering available metrics/keys) to close the minor specificity gaps.

DimensionReasoningScore

Specificity

"Creates observability dashboards and graphs" plus "previewing charts inline and saving them to a dashboard" lists several concrete actions with enumerated data sources (logs, traces, errors, sessions, metrics, events). It falls short of anchor 5 because body capabilities such as duplicating graphs, discovering keys, and listing existing dashboards are not covered.

4 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

Includes natural terms users would say — "dashboards", "graphs", "charts", "logs", "traces", "errors", "metrics" — but misses common variations like "visualization", "monitoring", or "latency". Good coverage with a few natural terms missing, matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Observability dashboards and graphs from logs, traces, errors, sessions, metrics, and events data" carves a distinct niche anchored by the enumerated observability data sources. Generic terms like "graphs", "charts", and "metrics" create minor overlap risk with general charting/dataviz skills, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

launchdarkly/ai-tooling

Path

skills/observability/create-graph/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.