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

Fix and improve this skill with Tessl

tessl review fix ./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 well-structured, highly actionable detection skill with excellent workflow clarity and progressive disclosure. The blocking question patterns ensure Claude never proceeds without user confirmation on ambiguous decisions, and the decision tree covers all edge cases comprehensively. The main weakness is moderate verbosity in the reference tables and repeated blocking question boilerplate, though this is a minor issue given the complexity of the task.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy — the extensive indicator tables for languages, package managers, and monorepo tools are useful reference material but could be more compact. The entrypoint patterns section is thorough but borders on verbose for information Claude largely already knows. The blocking question patterns are repeated multiple times with similar boilerplate.

2 / 3

Actionability

The skill provides highly concrete, actionable guidance: specific files to look for, exact search strings for existing LD usage, clear blocking question patterns with explicit tool usage instructions, and precise decision tree outcomes with links to next steps. Every section tells Claude exactly what to do.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (sections 1-6 plus SDK confirmation and decision tree), with explicit validation checkpoints via the D5 blocking questions. Section 5a introduces a robust classification step with three states and clear branching logic, including feedback loops (re-run detection after user clarification). The decision tree at the end provides comprehensive routing for all outcomes.

3 / 3

Progressive Disclosure

The skill clearly positions itself within a larger hierarchy (nested under sdk-install, links to plan, apply, first-flag, and SDK recipes). References are one level deep and well-signaled with relative paths. The content appropriately stays focused on detection while pointing to other skills for subsequent steps.

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 is strong on specificity and distinctiveness, clearly enumerating what it detects and anchoring it to the LaunchDarkly SDK onboarding workflow. However, it lacks an explicit 'Use when...' clause, and the trigger terms lean technical/internal rather than matching natural user language. The workflow positioning info ('Nested under sdk-install; next is plan') serves orchestration but doesn't substitute for explicit trigger guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when starting LaunchDarkly SDK installation and the repository's tech stack needs to be identified.'

Include more natural trigger terms a user might say, such as 'detect tech stack', 'analyze project setup', 'identify SDK requirements', or 'what language/framework is my project using'.

DimensionReasoningScore

Specificity

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

3 / 3

Completeness

Clearly answers 'what does this do' (detect repository stack details for LaunchDarkly SDK onboarding), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the workflow context ('Nested under sdk-install; next is plan'), which is internal orchestration info rather than trigger guidance.

2 / 3

Trigger Term Quality

Includes some 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', 'analyze my project').

2 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific LaunchDarkly SDK onboarding context, the enumerated detection targets, and the workflow positioning ('nested under sdk-install'). 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.