Name: lumigo
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

lumigo

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

Quality

61%

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

Quality

Content

61%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 highly actionable with concrete Membrane CLI commands and a clear state-driven connection flow, but it opens with unnecessary concept explanation and its step numbering references ('Step 2', '1b') are inconsistent and undefined.

Suggestions

Trim or move the introductory 'Lumigo is a cloud observability platform...' paragraph so the body starts with what to do rather than what Lumigo is, improving token efficiency.

Fix the workflow numbering: define explicit 'Step 1 / Step 2' labels or remove the dangling 'skip to Step 2' and '1b' references so the connection sequence is unambiguous.

Add one fully-resolved worked example (a real connectionId and a sample action run with input/output) to close the placeholder gap and lift actionability toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands and tables, but the opening paragraph explaining what Lumigo is ('Lumigo is a cloud observability platform that helps developers and DevOps teams troubleshoot... It's primarily used by engineers working with AWS Lambda...') is concept padding Claude already knows, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides many concrete, copy-pasteable CLI commands with flags and a proxy-options table, but leaves placeholders like CONNECTION_ID and <actionId> and stops just short of fully worked end-to-end examples, matching 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The connection flow has a real sequence with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but cross-references to an undefined 'Step 2' and a '1b' with no '1a'/'2' make the sequence loosely defined, fitting 'steps listed but checkpoints implicit/sequence gaps'.	3 / 5
Progressive Disclosure	No bundle files exist and the skill is a single well-sectioned file with clear headers (Overview, Install, Authentication, Connecting, Searching actions, Running actions, Proxy, Best practices); structure is good with only minor organization gaps, though it is longer than the under-50-line simple-skill case that would warrant a 5.	4 / 5
	Total	14 / 20 Passed

Description

61%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 correctly names a distinct product and includes a 'Use when' trigger, but its listed actions are generic rather than Lumigo-specific and it lacks the natural trigger terms (traces, dashboards, troubleshooting) users would actually say.

Suggestions

Replace generic actions ('manage data, records, automate workflows') with concrete Lumigo capabilities such as 'query distributed traces, inspect spans, view services and transactions, and read alerts and dashboards'.

Expand the trigger clause with natural phrasing users would say, e.g. 'Use when the user wants to investigate Lumigo traces, spans, alerts, or dashboards, or troubleshoot Lambda/container performance'.

Tighten the 'when' to mention specific observability scenarios (root-cause analysis, monitoring) to lift completeness from 4 to 5.

Dimension	Reasoning	Score
Specificity	It names the domain ('Lumigo integration') but the actions listed — 'Manage data, records, and automate workflows' — are generic and not Lumigo-specific concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Lumigo data') are present, but the 'when' is somewhat generic and could be more specific, fitting the 'both present, when could be more explicit' anchor rather than a 5.	4 / 5
Trigger Term Quality	The only natural keyword is the brand 'Lumigo' in 'Use when the user wants to interact with Lumigo data'; common variations users would say (traces, dashboards, troubleshooting, Lambda monitoring) are absent, so it has some relevant keywords but is missing synonyms and variations.	3 / 5
Distinctiveness Conflict Risk	'Lumigo' is a specific named product and the trigger 'interact with Lumigo data' carves a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	14 / 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/lumigo/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.