Name: launchdarkly
Rating: 56.8 (1 reviews)
Author: membranedev

launchdarkly

Launch Darkly integration. Manage Segments, Projects, Users. Use when the user wants to interact with Launch Darkly data.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/launchdarkly/SKILL.md

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 content is actionable and well-sequenced for the connection workflow, but trades some conciseness for an explanatory intro and keeps the entire API reference inline. Splitting the actions/options into a reference file and trimming the platform explanation would raise the weaker dimensions.

Suggestions

Remove or shrink the opening paragraph that explains what LaunchDarkly/feature management is, since Claude already knows this.

Move the Popular actions table and proxy options into a separate references file (e.g. ACTIONS.md) and link to it from the body.

Add a verification step after create/update/proxy mutation operations (e.g. re-fetch the flag or check the response status) to mirror the connection workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but opens with a paragraph explaining what a feature management platform is and includes some padded phrasing ('This is the fastest way to get a connection', the Agent Types aside) that Claude does not need.	3 / 5
Actionability	Provides copy-paste-ready bash commands for the core flows (login, connection ensure, action list/run, request) plus a Popular actions table and JSON examples, with only minor unresolved placeholders like <id> and <actionId>.	4 / 5
Workflow Clarity	The connection workflow has a clear state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with an explicit re-poll feedback loop, though create/update/proxy mutation steps lack explicit validation checkpoints.	4 / 5
Progressive Disclosure	No bundle files exist and the full 18-row actions table plus proxy option reference is inlined into SKILL.md; the section structure is reasonable but content that would fit a separate reference file is not split out.	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 on solid ground with an explicit 'Use when' clause and a clear product niche, but its 'when' trigger is generic and its action vocabulary reduces to a single 'Manage' verb. Adding concrete trigger phrases ('feature flags', 'rollouts', 'experiments') would lift the lower dimensions.

Suggestions

Replace the generic 'Manage Segments, Projects, Users' with concrete verbs, e.g. 'List, create, and update feature flags, segments, projects, and environments'.

Add natural trigger phrases to the 'Use when' clause, e.g. 'Use when the user wants to manage feature flags, segments, projects, or environments in Launch Darkly'.

Mention 'feature flags' and 'experiments' in the description since they are core LaunchDarkly capabilities the skill covers.

Dimension	Reasoning	Score
Specificity	Names the domain plus three concrete entities ('Segments, Projects, Users') but relies on the single generic verb 'Manage' rather than listing several specific actions, matching the domain-plus-1-2-actions anchor.	3 / 5
Completeness	Provides both a 'what' ('Launch Darkly integration. Manage Segments, Projects, Users.') and an explicit 'when' ('Use when the user wants to interact with Launch Darkly data.'), though the 'when' trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	Includes relevant domain keywords ('Launch Darkly', 'Segments', 'Projects', 'Users') but omits common natural variations users say such as 'feature flags', 'experiments', and 'environments' that the skill actually supports.	3 / 5
Distinctiveness Conflict Risk	Targets a clearly named product niche ('Launch Darkly integration') with distinct triggers and named entities, making conflict with unrelated skills minimal.	5 / 5
	Total	15 / 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/launchdarkly/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.