CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configs-create

Create and configure configs in LaunchDarkly. Helps you choose between agent vs completion mode, create the config, add variations with models and prompts, and verify the setup.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/agentcontrol/configs-create/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 and workflow-driven, with complete JSON examples, explicit verification steps, and error-recovery guidance covering the most common failure modes. Its main weakness is token efficiency: the same warnings (targeting, modelName, curl/jq) are repeated across multiple sections.

Suggestions

State the enabled=False/targeting warning once (e.g., in the Step 5 section) and reference it briefly elsewhere instead of repeating the full explanation in the intro blockquote, Step 5, and What NOT to Do.

Consolidate the modelName and curl/jq pitfalls into a single 'Common pitfalls' section rather than duplicating them between the workflow steps and What NOT to Do.

DimensionReasoningScore

Conciseness

The content is LaunchDarkly-specific with no filler explaining known concepts, but the enabled=False targeting warning is repeated three times (intro blockquote, Step 5, What NOT to Do) and the modelName and curl/jq warnings each appear twice — noticeable duplication that could be consolidated into one canonical warning.

3 / 5

Actionability

Fully executable throughout: complete copy-paste JSON payloads for both agent and completion mode, exact MCP tool names with field-by-field descriptions, modelConfigKey format examples with valid values, a verification checklist, the config URL pattern, and a ready-to-run targeting JSON call.

5 / 5

Workflow Clarity

The five-step workflow is clearly sequenced with explicit validation checkpoints (Step 4's four-item verification, post-targeting SDK assertions), error-recovery feedback loops (NO MODEL variation -> update-agent-config; jq shape inspection), an edge-case table, and a verbatim checklist to print to the user.

5 / 5

Progressive Disclosure

As a single-file bundle it has no nested references and is well organized with clear section headers, tables, and examples; however, at ~215 lines everything is inline with no overview/detail split — content like the SDK reference list and modelConfigKey examples could live in a reference file, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

66%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 clearly and concretely states what the skill does across the full create-and-verify workflow, but it omits any explicit 'when to use' trigger guidance and uses second-person voice. Adding a Use-when clause with natural synonyms would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to create an AI config in LaunchDarkly, add a variation with a model and prompt, or set up agent/completion mode."

Include natural synonyms users would say, such as "AI config", "model configuration", or "LLM setup", to broaden trigger-term coverage.

Rewrite in third person ("Guides choosing between agent vs completion mode..." instead of "Helps you choose...") to avoid the second-person penalty.

DimensionReasoningScore

Specificity

Lists four concrete actions ("choose between agent vs completion mode", "create the config", "add variations with models and prompts", "verify the setup"), matching the comprehensive-coverage anchor, but "Helps you choose" uses second-person voice, which the rubric penalizes by reducing specificity by 1.

4 / 5

Completeness

The 'what' is clearly answered (create and configure configs with mode choice, variations, and verification), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the judging guidelines cap at 3.

3 / 5

Trigger Term Quality

Natural phrases like "create configs", "LaunchDarkly", "variations", and "models and prompts" are present, but common synonyms such as "AI config" or "model configuration" are missing, placing it between relevant-keywords (3) and comprehensive-synonym (5) coverage.

4 / 5

Distinctiveness Conflict Risk

"configs in LaunchDarkly" carves a clear niche, but the skill family includes closely related siblings (configs-targeting, configs-update, configs-variations) whose descriptions could overlap with the generic "create and configure" phrasing, indicating minor rather than minimal conflict risk.

4 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

launchdarkly/ai-tooling

Path

skills/agentcontrol/configs-create/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.