Name: first-flag
Rating: 61.6 (1 reviews)
Author: launchdarkly

first-flag

Create a boolean first flag, add evaluation, toggle on/off for end-to-end proof. Parent onboarding Step 6; uses MCP, API, or ldcli; optional flag-create skill.

Quality

72%

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/onboarding/first-flag/SKILL.md

Quality

Content

77%

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 a clear, validated workflow and strong error handling. Its main weaknesses are verbosity from parallel multi-language examples and a monolithic structure that could offload reference material into bundle files.

Suggestions

Move the per-SDK demo code blocks (Node/Express, Python/Flask, React, full-stack) into a references file and keep only one representative example inline to improve conciseness and progressive disclosure.

Trim celebratory narration ('wow moment', 'Celebrate the successful integration') to reduce token overhead without losing the proof-point intent.

Consider extracting the Flag-key-behavior-by-SDK table into a reference file so the main body stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and concrete with little concept-explanation, but parallel multi-language demo blocks and celebratory prose ('wow moment', 'Celebrate the successful integration') could be tightened, matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	Provides fully executable curl/ldcli/MCP calls and copy-paste-ready code in multiple languages, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Clear Step 0–6 sequence with explicit validation checkpoints (verify OFF in Step 3, verify ON in Step 5) and an error-handling feedback loop for auth errors, matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	No bundle files exist; sibling references are one-level-deep and clearly signaled, but the ~370-line body is monolithic with multiple full inline demo code blocks that could be split into reference files, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 well-scoped to the LaunchDarkly onboarding first-flag task, but lacks an explicit 'Use when...' trigger and the natural term 'feature flag'. Adding explicit when-guidance and broader trigger phrasing would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when creating your first LaunchDarkly feature flag during SDK onboarding') to satisfy the completeness 'when' requirement.

Include the natural term 'feature flag' and variations like 'create a flag' to improve trigger-term coverage.

Lead with the capability ('Create and verify your first feature flag end-to-end') so the primary action reads as a natural user request.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create a boolean first flag, add evaluation, toggle on/off' — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	The 'what' is explicit but 'when' is only positional ('Parent onboarding Step 6') with no 'Use when...' trigger clause, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Contains relevant terms ('first flag', 'toggle on/off', 'evaluation') but omits the most natural user phrasing 'feature flag' and common variations, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche ('Parent onboarding Step 6', 'MCP, API, or ldcli') making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 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
relative_links	Relative link issues: 6 suspicious	Warning

	Total	15 / 16 Passed

Repository: launchdarkly/ai-tooling
Path: skills/onboarding/first-flag/SKILL.md
Commit: b618549

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