CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launchdarkly-flag-qualitative-feedback-setup

Integrate LaunchDarkly qualitative user feedback into a JavaScript/TypeScript codebase. Guides framework and design system detection, builds the sendFeedback utility and feedback widget matching existing project patterns. Use when the user wants to add a Give Feedback widget, collect user sentiment tied to feature flags, set up feedback collection, or wire up the $ld:feedback tracking event.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 content is an exemplary structured wizard: fully actionable steps, hard gates with validation and feedback loops, and clean progressive disclosure into real reference files. Its one real weakness is token efficiency — a meta-intro and substantial rule duplication across three summary sections could be consolidated without losing clarity.

Suggestions

Merge the overlapping guidance in Core Principles, What NOT to Do, and the Edge Cases table into a single section — the design-system rule and the one-widget-per-screen rule are each stated three times, and most Edge Cases rows just restate 'handled by Check N'.

Delete the meta-intro paragraph ('You're using a skill that will guide you through... Your job is to...') — the wizard instruction and Step 0 already convey this.

Consider moving the Example Flows section into a references/ file, keeping only one abbreviated example inline, since the decision-tree outcomes are already implied by the step and edge-case guidance.

DimensionReasoningScore

Conciseness

The body is mostly high-value wizard detail, but it is noticeably padded: the meta-intro paragraph ("You're using a skill that will guide you through... Your job is to...") and heavy duplication — the design-system rule and the one-widget-per-screen rule each appear three times across Core Principles, What NOT to Do, and the Edge Cases table, and the Edge Cases rows mostly restate "handled by Check N". It is above the 2 anchor because the bulk (detection signals, event contract, replacement table) earns its tokens, but below 4 because a tightening pass would cut real redundancy.

3 / 5

Actionability

Fully executable guidance throughout: exact package names and search strings ("launchdarkly-js-client-sdk", "createClient(", "<LDProvider"), the concrete "$ld:feedback" event contract with required/optional fields, verifiable template files in references/ (sendFeedback.ts confirmed to match the described truncation limits and flush call), explicit AskUserQuestion option labels/descriptions, and a template-element-to-design-system replacement table. It is not the 4 anchor because there are no meaningful gaps — even edge cases like existing sendFeedback reuse and vanilla JS wiring have concrete steps.

5 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced with explicit STOP gates ("Do not proceed to Step 3 until you have answers to ALL of the following"), per-step verification with feedback loops ("If not found, fix before proceeding"; build failure → fix before continuing), a pre-condition checklist in Step 7, and a re-confirmation loop when the user requests changes. This matches the 5 anchor's explicit validation steps, error-recovery loops, and checklists.

5 / 5

Progressive Disclosure

The body is a well-signaled overview plus inline wizard logic, with bulk material correctly split into one-level-deep references: all five bundle files (sendFeedback.ts, PopoverFeedback.tsx, InlineFeedback.tsx, client-side-sdk-list.md, server-side-sdk-list.md) exist and are linked contextually, plus a Templates table describing each. Not the 4 anchor because organization is clean throughout — the only blemish is the cross-skill link (../launchdarkly-flag-create/SKILL.md) that is not part of this bundle.

5 / 5

Total

18

/

20

Passed

Description

92%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.

A strong description: third-person voice, concrete capability list, and an explicit Use-when clause with natural trigger phrases covering the main ways a user would request this. The only minor gap is a few missing synonyms in the trigger terms.

DimensionReasoningScore

Specificity

The description names multiple concrete actions — "Guides framework and design system detection, builds the sendFeedback utility and feedback widget matching existing project patterns" — covering the integration's deliverables comprehensively. It is not the 4 anchor because no core capability of the integration is left out; the named actions span detection, utility creation, widget creation, and event wiring.

5 / 5

Completeness

Explicitly answers both questions: the "what" ("Integrate LaunchDarkly qualitative user feedback into a JavaScript/TypeScript codebase... builds the sendFeedback utility and feedback widget") and the "when" ("Use when the user wants to add a Give Feedback widget, collect user sentiment tied to feature flags, set up feedback collection, or wire up the $ld:feedback tracking event"). This matches the 5 anchor's clear what + when with concrete trigger phrases; the 4 anchor would require a less explicit 'when'.

5 / 5

Trigger Term Quality

Good natural-language coverage: "add a Give Feedback widget", "collect user sentiment tied to feature flags", "set up feedback collection", "wire up the $ld:feedback tracking event". It falls short of the 5 anchor's comprehensive synonym coverage — phrases like "feedback form" or plain "user feedback on a feature" are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche — LaunchDarkly-specific qualitative feedback tied to feature flags with the distinctive "$ld:feedback" trigger term — so it is unlikely to fire for unrelated feedback or UI skills. Conflict risk with other LaunchDarkly skills is minimal since the triggers are feedback-specific.

5 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

launchdarkly/ai-tooling

Path

skills/feature-flags/launchdarkly-flag-qualitative-feedback-setup/SKILL.md

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.