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
76%
Does it follow best practices?
Impact
85%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/onboarding/sdk-install/detect/SKILL.mdMonorepo target selection and scoped detection
Monorepo detected
100%
100%
Root not assumed as target
100%
100%
Target selection question noted
40%
40%
Runnable package selected
100%
100%
Scoped detection
100%
100%
Framework identified
100%
100%
Package manager identified
100%
100%
Entrypoint identified
100%
100%
LD search performed
100%
100%
SDK recommendation made
100%
100%
No root-level LD search only
100%
100%
Weak-evidence workspace confidence classification
Weak evidence classification
100%
100%
Weak evidence reasoning
100%
100%
No premature integration
100%
100%
Blocking clarification documented
100%
100%
Multiple lock files noted
100%
100%
Most-recently-modified lock file preferred
16%
0%
LD search performed
100%
100%
LD not found correctly noted
100%
100%
Candidate folders offered
44%
44%
Demo app option mentioned
0%
25%
Next.js dual-SDK and partial LD install detection
Next.js detected
100%
100%
Both surfaces identified
100%
100%
Server entrypoint identified
100%
100%
Client entrypoint identified
100%
100%
LD search terms used
75%
62%
SDK installed detected
100%
100%
Not initialized detected
100%
100%
Decision tree: apply-code-changes
83%
75%
Dual-SDK scope noted
100%
100%
Package manager identified
100%
100%
No install step recommended
30%
20%
24e9c7e
Table of Contents
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.