Name: lightstep
Rating: 52.8 (1 reviews)
Author: membranedev

lightstep

Lightstep integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lightstep data.

Quality

58%

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/lightstep/SKILL.md

Quality

Content

67%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 provides concrete, executable Membrane CLI commands and a clearly sequenced connection workflow with explicit state-based feedback loops, though it carries some concept padding and a bare entity list that could be trimmed.

Suggestions

Trim the introductory paragraph and the 'Lightstep Overview' bullet list, which restate what Lightstep is and list entities without actionable value.

Replace the bare CONNECTION_ID placeholder with a concrete worked example so the action-search and action-run snippets are fully copy-paste runnable.

Consider moving the proxy flag reference table into a separate reference file and keeping only one example inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening paragraph ('Lightstep is an observability platform... Developers and SREs use it to monitor, troubleshoot...') and the bare 'Lightstep Overview' entity list explain concepts Claude already knows and add little actionable value.	3 / 5
Actionability	Concrete, executable commands throughout (login, connection ensure, action list/run, proxy table) with mostly copy-paste-ready examples; minor gaps like the unfilled CONNECTION_ID placeholder keep it just below fully executable.	4 / 5
Workflow Clarity	Clear sequenced workflow (install -> login -> connection ensure -> poll state -> search/run actions) with an explicit state machine and per-state feedback loops for READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR; only minor validation gaps prevent a 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections (install, auth, connecting, searching, popular actions, best practices) with appropriately inlined examples and no bundle files needed; slightly monolithic but navigable, so just below a 5.	4 / 5
	Total	15 / 20 Passed

Description

50%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 third-person, includes an explicit 'Use when' trigger, and is clearly tied to Lightstep, but its action vocabulary is generic and the natural trigger terms users would say are largely absent.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Lightstep capabilities such as 'query spans and traces, inspect dashboards and SLOs, and run workflows'.

Expand the 'Use when' clause to list natural trigger phrases users actually say, e.g. 'when the user asks about Lightstep spans, traces, metrics, dashboards, SLOs, or alerts'.

Add the file/term equivalents (e.g. 'Lightstep', 'spans', 'traces', 'SLOs') so the description surfaces on natural-language requests.

Dimension	Reasoning	Score
Specificity	Names the Lightstep domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and abstract rather than concrete capabilities like querying spans or inspecting traces.	2 / 5
Completeness	Explicit 'what' (manage data/records, automate workflows) and an explicit 'Use when the user wants to interact with Lightstep data' clause are both present, though the 'when' could name more specific triggers.	4 / 5
Trigger Term Quality	Only the proper noun 'Lightstep' and the generic phrase 'interact with Lightstep data' appear; natural terms users would actually say (spans, traces, SLOs, metrics, dashboards) are missing.	2 / 5
Distinctiveness Conflict Risk	Tied to the named Lightstep platform with a clear trigger, so it is mostly distinct from other skills with only minor overlap risk against other observability integrations.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/lightstep/SKILL.md
Commit: f484c82

Reviewed: 6 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.