CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

onboarding

Scripted onboarding for LaunchDarkly: quiet execution, fixed sequence, SDK install, first flag with a live reveal, MCP offered afterwards. Enforces step completion before advancing and redirects drift. Use when adding LaunchDarkly, setting up or integrating feature flags in a project, SDK integration, or 'onboard me'.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

An unusually actionable orchestration skill: concrete commands, URL templates, JSON interaction forms, explicit sequencing with validation checkpoints and fallback paths for every failure mode. Its main weaknesses are mild redundancy in the voice/quietness guidance spread across several sections and a reference structure that is two levels deep in places and depends on nested skills installed at runtime rather than present in the bundle.

Suggestions

Consolidate the repeated 'work silently / keep user-facing messages short' guidance (Voice and Tone, Rules, Speaking to the user, Kickoff) into a single section, since the same principle is stated four times.

Flatten the reference chain where possible — e.g. have SKILL.md link directly to the relevant snippets/ detail file for the detected stack instead of routing through the recipes.md index — and clarify in the References section that mcp-configure and sdk-install are runtime-installed nested skills, not local bundle files.

DimensionReasoningScore

Conciseness

The body is dense, directive prose with no explanations of concepts Claude already knows, using token-efficient tables and ready-to-use JSON forms. However, the 'stay quiet / keep messages short' principle is restated across four sections (Voice and Tone, Rules, Speaking to the user, Kickoff) and 'Forbidden in user-facing output' overlaps earlier rules — minor instances of over-explanation that could be trimmed, fitting the 4 anchor rather than the every-token-earns-its-place 5.

4 / 5

Actionability

Guidance is fully executable: exact branch name 'launchdarkly-onboarding', complete URL templates ('https://app.launchdarkly.com/projects/{projectKey}/flags/new?key={flagKey}'), runnable 'npx skills add launchdarkly/ai-tooling --skill ... -y --agent <detected-agent>' commands, 'lsof -ti :3000,4000,5173', copy-paste JSON question forms, a fast-path table giving package/install/env-var/entrypoint/init per scaffold, and named MCP tool calls with parameters. Copy-paste ready and covering the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

A fixed Step 0-4 sequence is explicitly enforced ('Do not advance until the current stage is done'), with validation checkpoints ('Do not proceed until initialization is verified', keep the dev server running until the user sees the flag flip) and genuine feedback loops for error recovery (duplicate-key conflict -> get-flags -> adopt the existing flag; npx failure -> cached copy -> inline config; no MCP or API token -> dashboard-link fallback; a three-part drift redirection protocol; ordered resume detection). This matches the 5 anchor's explicit validation with error-recovery loops.

5 / 5

Progressive Disclosure

The References section maps each file to its step, and the local bundle files (references/sdk/recipes.md, references/sdk/observability-plugin.md, references/sdk/snippets/) all exist and are well signaled. But references are not strictly one level deep (SKILL.md -> recipes.md index -> snippets/*.md detail, and sdk-install/SKILL.md -> sdk-install/apply/SKILL.md), and the nested mcp-configure/sdk-install skills are absent from the local bundle, fetched at runtime via npx — good structure with minor organization gaps, fitting the 4 anchor rather than the clean one-level-deep 5.

4 / 5

Total

18

/

20

Passed

Description

87%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 strong description: it names the product and concrete capabilities in third person, and pairs them with an explicit 'Use when' clause containing natural trigger phrases. Trigger coverage is good though not exhaustive of synonyms, and a couple of capability phrases describe style rather than actions.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'SDK install, first flag with a live reveal, MCP offered afterwards', 'Enforces step completion before advancing and redirects drift' — but phrases like 'quiet execution' are design traits rather than actions, and coverage has minor gaps (no mention of account/signup handling or demo scaffolding). Not a 5 because coverage is not comprehensive; clearly above the 1-2-actions level of 3.

4 / 5

Completeness

Explicitly answers both 'what' (scripted onboarding: SDK install, first flag with live reveal, MCP offered afterwards, sequence enforcement, drift redirection) and 'when' with a concrete 'Use when...' clause naming multiple triggers including the literal 'onboard me'. This matches the anchor for a clear, explicit what-and-when with concrete trigger phrases; the 4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

'adding LaunchDarkly', 'setting up or integrating feature flags', 'SDK integration', and "'onboard me'" are natural phrases a user would say when they need this skill. Missing a few common variations (e.g. 'LaunchDarkly SDK', singular 'feature flag', 'flag setup'), so it falls short of the comprehensive synonym coverage of a 5 but is well above the 3 anchor.

4 / 5

Distinctiveness Conflict Risk

'Scripted onboarding for LaunchDarkly' carves out a clear niche with distinct, product-named triggers; the only conceivable overlap is with other LaunchDarkly-specific skills, which is minimal conflict risk. Matches the 5 anchor; the 4 anchor's 'minor overlap risk with closely related skills' is not a better fit given the product is named throughout.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 missing, 9 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 5 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

launchdarkly/ai-tooling

Path

skills/onboarding/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.