CtrlK
BlogDocsLog inGet started
Tessl Logo

detect

Detect repository stack for LaunchDarkly SDK onboarding: languages, frameworks, package managers, monorepo targets, entrypoints, existing LD usage. Nested under sdk-install; next is plan.

81

0.98x
Quality

76%

Does it follow best practices?

Impact

85%

0.98x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/onboarding/sdk-install/detect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, well-structured skill that excels at workflow clarity and actionability. The blocking question patterns (D5) are a standout feature that prevents Claude from proceeding without user confirmation at critical decision points. The main weakness is moderate verbosity in the indicator tables, which contain information Claude could largely infer, though they do serve as useful quick-reference checklists.

Suggestions

Consider condensing the language/framework indicator table — Claude already knows that `package.json` means JavaScript and `go.mod` means Go. Focus the table on less obvious mappings (e.g., edge SDKs like Cloudflare Workers, Roku) and let Claude infer the common ones.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy — the large indicator tables for languages, package managers, and monorepo tools contain information Claude largely already knows. The entrypoint patterns section is similarly verbose. However, the decision tree logic and blocking question patterns are genuinely novel and earn their tokens.

2 / 3

Actionability

The skill provides highly concrete, actionable guidance: specific files to look for, exact search strings for existing LD usage, precise blocking question patterns with structured tool calls, and clear branching logic. Every step tells Claude exactly what to do, not just what to think about.

3 / 3

Workflow Clarity

The workflow is exceptionally well-sequenced with numbered steps (1-6), explicit blocking checkpoints (D5 pattern) that halt progress until user confirmation, clear branching logic in section 5a with three classified states, and a comprehensive decision tree at the end. Feedback loops are present (re-run detection after user redirects).

3 / 3

Progressive Disclosure

The skill clearly positions itself within a parent skill hierarchy, references sibling skills (plan, apply, first-flag) with relative paths, and points to external references (SDK recipes). Content is appropriately scoped to detection only, with clear navigation to next steps. No bundle files were provided but the cross-references are well-signaled and one level deep.

3 / 3

Total

11

/

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 excels at specificity and distinctiveness, clearly listing concrete detection targets within a well-defined LaunchDarkly SDK onboarding context. However, it lacks an explicit 'Use when...' clause, and the trigger terms lean toward internal/technical jargon rather than natural user language. The workflow positioning ('Nested under sdk-install; next is plan') is useful for orchestration but doesn't substitute for explicit trigger guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when starting LaunchDarkly SDK installation, setting up feature flags, or when the user asks to integrate LaunchDarkly into their project.'

Include more natural user-facing trigger terms such as 'feature flags', 'SDK setup', 'integrate LaunchDarkly', or 'tech stack detection' to improve matching against user requests.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: detect languages, frameworks, package managers, monorepo targets, entrypoints, and existing LaunchDarkly usage. These are concrete, well-defined capabilities.

3 / 3

Completeness

Clearly answers 'what' (detect repository stack details for LaunchDarkly SDK onboarding), but the 'when' is only implied through context ('Nested under sdk-install; next is plan'). There is no explicit 'Use when...' clause with trigger guidance.

2 / 3

Trigger Term Quality

Includes relevant terms like 'repository stack', 'languages', 'frameworks', 'package managers', 'monorepo', 'entrypoints', and 'LD usage', but these are more technical/internal terms. Missing natural user-facing trigger terms a user might say (e.g., 'detect my tech stack', 'what SDK do I need'). The description reads more like internal documentation than user-facing triggers.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific LaunchDarkly SDK onboarding context, the explicit mention of being nested under sdk-install, and the specific detection targets. Unlikely to conflict with other skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

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.