CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sdk-install

Install and initialize the correct LaunchDarkly SDK during onboarding by running nested skills in order: detect, plan, apply. Parent onboarding Step 4 is first flag.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/onboarding/sdk-install/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A well-structured orchestrator skill: it sequences three nested skills unambiguously, keeps its body to summaries and rules while delegating detail one level deep, and handles edge cases (dual-SDK, monorepo, already-installed) with specific instructions. The main improvement areas are tightening a few dense passages and briefly surfacing the error-recovery/validation loops that currently live only in the nested skills.

Suggestions

Tighten the densest passages — the SDK-key prerequisites bullet and the observability-plugin paragraph — by splitting them into short bullets or moving detail to the apply/observability references they already point to.

Add a one-line error-recovery note in the workflow (e.g. what to do when the apply compile check fails) so the feedback loop is visible at this level rather than only inside apply/SKILL.md.

Ship the skill for review with its bundle (detect/, plan/, apply/, references/) so referenced paths can be verified; the review directory contained only SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly lean for an orchestrator skill — compact tables, short bullets, details delegated to nested skills — but a few spots could be trimmed: the dense SDK-key prerequisites bullet with layered parentheticals, the long single-sentence observability-plugin paragraph, and the repeated "don't skip ahead to the first flag" message in both the intro and "After Step 3". This matches anchor 4 (minor over-explanation), not anchor 5 (every token earns its place).

4 / 5

Actionability

Concrete, executable guidance throughout: exact variable names ("LAUNCHDARKLY_SDK_KEY", "LAUNCHDARKLY_MOBILE_KEY") with their LaunchDarkly UI sources, an ordered table of the three nested skills with roles, and specific rules ("Never hardcode keys", "Do NOT batch tool calls across blocking boundaries", dependency changes only with explicit approval). It is anchor 4 rather than 5 because the actual code/commands live in the referenced nested skills and references, not here.

4 / 5

Workflow Clarity

The 1→2→3 sequence is explicit with roles, a short-circuit path via the detect decision tree, well-defined blocking/non-blocking decision boundaries, and signaled validation checkpoints ("compile check", "lockfile + entrypoint evidence" for dual-SDK). It falls short of anchor 5 because feedback loops for error recovery are delegated to the nested skills rather than described even briefly here.

4 / 5

Progressive Disclosure

A clear overview with well-signaled, one-level-deep references — detect/plan/apply SKILL.md files, SDK recipes, snippets, observability-plugin, and the parent skill — consolidated again in a References section, with only summaries (key-types table) kept inline and bulk detail split out. This matches anchor 5. Note: no bundle files were present in the review directory, so the referenced paths could not be verified on disk, but the structure as written is exemplary.

5 / 5

Total

17

/

20

Passed

Description

75%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.

A solid, third-person description that names concrete actions and an explicit usage context, and carves out a distinct LaunchDarkly-install niche. Its main weaknesses are terseness in the trigger guidance ("during onboarding" rather than a "Use when..." clause with natural trigger phrases) and missing common synonyms like "integrate" or "set up".

Suggestions

Add an explicit trigger clause with natural user phrasing, e.g. "Use when the user wants to install, integrate, or set up the LaunchDarkly SDK in their project during onboarding."

Include a couple of common synonyms/domain terms ("integrate", "set up", "feature flags") so the description matches how users naturally ask for this work.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Install and initialize the correct LaunchDarkly SDK", "running nested skills in order: detect, plan, apply" — with the niche explicitly named. Minor gaps in coverage (no mention of env wiring, recipes, or observability), so it falls at anchor 4 rather than the comprehensive anchor 5, and above anchor 3 since it goes beyond 1-2 actions.

4 / 5

Completeness

Both are answered: the what ("Install and initialize the correct LaunchDarkly SDK... by running nested skills in order") is clear, and the when ("during onboarding") is explicit but terse — no "Use when..." phrasing and the trigger context could be more specific, fitting anchor 4. Not anchor 3, since the when is stated rather than merely implied.

4 / 5

Trigger Term Quality

Good keyword coverage of natural terms — "LaunchDarkly SDK", "install", "initialize", "onboarding", "flag" — but common variations a user would actually say ("integrate", "set up", "feature flags", language/framework names) are missing, matching anchor 4 rather than the synonym-rich anchor 5.

4 / 5

Distinctiveness Conflict Risk

"LaunchDarkly SDK" establishes a clear niche and "Parent onboarding Step 4 is first flag" distinguishes it from sibling onboarding steps, but there is minor overlap risk with closely related LaunchDarkly skills (parent onboarding, observability plugin, first-flag), matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 14 missing, 11 suspicious

Warning

Total

15

/

16

Passed

Repository

launchdarkly/ai-tooling

Path

skills/onboarding/sdk-install/SKILL.md

Reviewed

Table of Contents

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.