Name: create-graph
Rating: 60 (1 reviews)
Author: launchdarkly

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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/observability/create-graph/SKILL.md

Quality

Content

71%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 content is concise, actionable, and workflow-driven with proper preview-before-commit validation. Its chief defect is progressive disclosure: it points to an enums.md file that is not present in the bundle.

Suggestions

Add the referenced enums.md to a references/ directory (or inline the enum values and drop the dangling reference) so the 'See enums.md' pointers resolve.

De-duplicate the tool list between Prerequisites and Capabilities — keep one canonical table and reference it, or merge the sections.

Surface the enum/productType values that matter most (e.g. the Sessions/CountDistinct casing) inline in 'Common mistakes' so the skill is self-contained even if enums.md is not loaded.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no concept over-explanation; the only trim opportunity is that Prerequisites and Capabilities both enumerate the same tool list.	4 / 5
Actionability	Concrete, executable guidance throughout — exact tool names, literal enum strings ('CountDistinct', 'Sessions', column=""), and an ISO date example — with only minor gaps versus copy-paste-ready 5-anchor code.	4 / 5
Workflow Clarity	A clear six-step sequence with an explicit preview→confirm validation checkpoint in step 4 and per-graph confirmation for batch cases; the destructive/batch cap at 3 does not apply because verification is present.	4 / 5
Progressive Disclosure	Sections are well-organized, but the body repeatedly references 'enums.md' ('Use exact enum casing from enums.md', 'See enums.md') and no such file exists in references/, scripts/, or assets/ — a dangling reference that breaks navigation.	3 / 5
	Total	15 / 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, third-person, and distinct, with strong natural trigger terms. Its main weakness is the absence of an explicit 'Use when…' clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when…' trigger clause naming the situations that should invoke this skill (e.g. 'Use when the user wants to visualize observability data, build a LaunchDarkly dashboard, or add a chart to an existing dashboard').

Include natural synonyms or variant phrasings (e.g. 'charts', 'panels', 'visualize logs/metrics') to broaden trigger coverage toward the 5 anchor.

Tighten the action list to non-overlapping verbs so coverage reads as comprehensive rather than several facets of one action.

Dimension	Reasoning	Score
Specificity	Names the observability domain and several concrete actions ('Creates observability dashboards and graphs', 'previewing charts inline', 'saving them to a dashboard'), with minor gaps versus the comprehensive 5-anchor.	4 / 5
Completeness	A clear 'what' is present but there is no 'Use when…' trigger clause, and the rubric guideline caps completeness at 3 when explicit trigger guidance is missing.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('dashboards', 'graphs', 'charts', 'logs', 'traces', 'errors', 'sessions', 'metrics', 'events') that users would say, but no synonyms or file extensions to reach the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	It carves a clear observability-graph niche with distinct triggers; minor overlap risk remains with generic charting/visualization skills rather than the minimal-conflict 5 anchor.	4 / 5
	Total	15 / 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: launchdarkly/ai-tooling
Path: skills/observability/create-graph/SKILL.md
Commit: 0aef88f

Reviewed: 3 days 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.