Name: plan
Rating: 61.6 (1 reviews)
Author: launchdarkly

plan

Generate a minimal LaunchDarkly SDK integration plan from detected stack: choose SDK type(s), dual-SDK server+client when required, files to change, env conventions. Nested under sdk-install; follows detect, precedes apply.

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/sdk-install/plan/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 and clearly sequenced with explicit gating checkpoints, reflecting a well-structured planning workflow. It is somewhat repetitive across the plan/present sections and keeps a large reference-style table inline rather than splitting it into a verified local reference file.

Suggestions

Consolidate the overlapping "Plan the changes" and "Present the plan" sections to remove repeated env-var and file-change guidance.

Move the large Project-Type/SDK-Type/Key-Type table into a referenced reference file (and verify the file exists in the skill bundle) so SKILL.md stays a lean overview.

Confirm the cited ../../references/sdk/recipes.md and snippets/ paths resolve within the skill bundle, or restructure them as one-level-deep local references.

Dimension	Reasoning	Score
Conciseness	The body is instruction-dense with no concept padding, but "Plan the changes" and "Present the plan" overlap and env-var guidance repeats across sections, so it could be tightened beyond level 3.	2 / 3
Actionability	Provides a concrete Project-Type/SDK-Type/Key-Type table, exact package names (e.g. launchdarkly-react-client-sdk, LaunchDarkly.ServerSdk), named env vars, and specific entrypoint examples, giving copy-ready actionable guidance.	3 / 3
Workflow Clarity	Clear sequenced flow (Choose SDK -> Dual SDK -> Plan changes -> Present plan) with explicit checkpoints such as the two-package/two-entrypoint completion gate, the D6 non-blocking gate, and blocking rules for ambiguous entrypoints.	3 / 3
Progressive Disclosure	Sectioning and signaled sibling/reference links exist, but the large SDK-selection table and dual-SDK track spec are inline in SKILL.md, and the cited references (recipes.md, snippets/) are not verifiable local bundle files, keeping it below level 3.	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 a distinct LaunchDarkly SDK planning niche, but it lacks an explicit user-facing trigger ("Use when...") and leans on internal-flow terminology rather than natural user keywords. This caps completeness and trigger term quality at the mid level.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up LaunchDarkly feature flags in a detected stack and an SDK install plan is needed."

Replace internal-flow phrasing ("detected stack", "follows detect, precedes apply") with natural terms users would say, such as "feature flags", "add LaunchDarkly", or "SDK onboarding plan".

Lead with the user-facing capability (planning a LaunchDarkly SDK setup) before the flow-positioning detail.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("choose SDK type(s)", "dual-SDK server+client when required", "files to change", "env conventions") rather than vague language, matching the level-3 anchor.	3 / 3
Completeness	The "what" is explicit, but there is no "Use when..." clause or equivalent trigger guidance; per the rubric guideline a missing trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant keywords like "LaunchDarkly SDK integration plan" appear, but the terms skew technical/internal-flow ("detected stack", "follows detect, precedes apply") and miss natural user phrasings like "feature flags" or "set up LaunchDarkly", so it is not level 3.	2 / 3
Distinctiveness Conflict Risk	Scoped to a LaunchDarkly SDK integration-planning niche nested in an sdk-install flow ("follows detect, precedes apply"), giving it a clear niche unlikely to conflict with other skills.	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: 17 suspicious	Warning

	Total	15 / 16 Passed

Repository: launchdarkly/ai-tooling
Path: skills/onboarding/sdk-install/plan/SKILL.md
Commit: 1dfe5b8

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.