CtrlK
BlogDocsLog inGet started
Tessl Logo

sdk-install

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

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.

The body is a well-structured orchestrator that efficiently delegates to nested skills with clear sequencing, decision-point semantics, and strong progressive disclosure. Its main limitation is that concrete executable detail and explicit validation checkpoints live in the referenced nested skills rather than inline.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, avoiding explanations of basic concepts and using compact tables and bullets; minor repetition around prerequisites and key handling keeps it just short of a 5.

4 / 5

Actionability

Concrete, actionable orchestration guidance is given: an ordered three-skill table with roles, specific section anchors (e.g. apply/SKILL.md#permission-before-changing-other-dependencies), and edge-case routing; not a 5 because executable detail lives in the nested skills rather than inline.

4 / 5

Workflow Clarity

The detect-plan-apply sequence is clearly ordered with a role table, blocking/non-blocking decision-point semantics, and validation references (compile check, lockfile + entrypoint evidence); minor validation gaps and delegation of the actual checkpoints to nested skills keep it at 4.

4 / 5

Progressive Disclosure

This is a clean overview skill that splits detail into one-level-deep, well-signaled nested skills and shared references (detect/plan/apply SKILL.md, recipes, snippets) with a dedicated References section, making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

58%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 specific and third-person, clearly conveying the install/initialize actions and the detect-plan-apply sequence, but it lacks an explicit 'Use when' trigger and has limited keyword variation. Adding a concrete trigger clause and synonyms would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g. 'Use when onboarding LaunchDarkly and the SDK still needs to be installed and initialized').

Include natural synonyms users might say such as 'set up', 'add', or 'integrate the LaunchDarkly SDK'.

Clarify the 'when' so it does not rely solely on the implied 'during onboarding' context.

DimensionReasoningScore

Specificity

Names the domain (LaunchDarkly SDK) and several concrete actions (install, initialize) plus an explicit three-phase sequence (detect, plan, apply), with only minor coverage gaps; not a 5 because it stops short of comprehensively listing what each phase does.

4 / 5

Completeness

It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, and 'when' is only weakly implied via 'during onboarding', which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant keywords like 'LaunchDarkly SDK', 'install', 'initialize', and 'onboarding' appear, but natural user variations/synonyms (e.g. 'set up', 'add LaunchDarkly', 'integrate SDK') are missing.

3 / 5

Distinctiveness Conflict Risk

The LaunchDarkly SDK install niche is mostly distinct with minimal conflict risk, but it sits within a family of related onboarding skills, so minor overlap with the parent onboarding skill remains.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 14 missing, 10 suspicious

Warning

Total

15

/

16

Passed

Repository
launchdarkly/ai-tooling
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.