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.

72

1.19x
Quality

81%

Does it follow best practices?

Impact

100%

1.19x

Average score across 1 eval scenario

SecuritybySnyk

Passed

No findings from the security scan

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.

The body is highly actionable with clear workflow sequencing and explicit validation checkpoints. Minor conciseness trims and slightly tighter organization of the inline detection tables would push it to full marks.

DimensionReasoningScore

Conciseness

Largely efficient tables and actionable guidance that assume Claude's competence, with minor over-explanation in the restated 'weak evidence' examples and redundant STOP lines that could be trimmed.

4 / 5

Actionability

Fully actionable for a detection task: specific indicator files, per-stack entrypoint paths, exact search terms, and copy-ready structured-question prompts covering common cases.

5 / 5

Workflow Clarity

Clear numbered sequence (1 through 6, confirmation, decision tree) with explicit BLOCKING validation checkpoints and feedback loops (re-run detection after user input).

5 / 5

Progressive Disclosure

Well-organized with clearly signaled one-level-deep references (recipes.md, parent/sibling SKILL.md); no bundle directory exists, and the bulk detection tables are reasonably inlined rather than split out.

4 / 5

Total

18

/

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.

The description is specific and distinctive with comprehensive capability coverage, but it omits an explicit 'Use when...' trigger clause, which caps completeness. Adding natural user-voice trigger guidance would raise the trigger and completeness scores.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when onboarding a LaunchDarkly SDK into a repository or when the user asks to detect the project stack').

Include common user-voice synonyms in the trigger phrasing (e.g., 'identify the tech stack', 'which SDK fits this repo') to improve trigger term quality.

DimensionReasoningScore

Specificity

Lists multiple concrete detection actions with comprehensive coverage: 'languages, frameworks, package managers, monorepo targets, entrypoints, existing LD usage', matching the comprehensive anchor 5.

5 / 5

Completeness

Has a clear 'what' but only weakly implies 'when' via 'onboarding'/'Nested under sdk-install'; per guidelines a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage including synonyms ('LaunchDarkly', 'LD') and stack terms, but lacks natural user-voice trigger phrasing such as 'Use when...', matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

Targets a distinct LaunchDarkly SDK onboarding-detection niche scoped by 'Nested under sdk-install', giving minimal conflict risk per anchor 5.

5 / 5

Total

17

/

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: 11 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.