CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

65%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with excellent workflow clarity, providing concrete JSON examples, specific MCP tool names, and a well-sequenced multi-step process with validation. However, it is significantly over-verbose — the enabled=False/targeting warning is repeated at least 4 times (top warning, Step 5, checklist, What NOT to Do), and several sections explain things Claude can infer. The content would benefit greatly from deduplication and trimming.

Suggestions

Consolidate the enabled=False/targeting warning to a single prominent location (Step 5) instead of repeating it in the top warning block, Step 5 body, the verbatim checklist, and the 'What NOT to Do' section.

Remove or drastically shorten the top warning block — the same information is covered more actionably in Step 5.

Trim the 'What NOT to Do' section to only items not already covered in the workflow steps, or remove it entirely since the workflow already provides clear guidance.

Consider extracting the targeting shortcut (curl/CLI commands) into a separate referenced file to reduce the main skill's length.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~250+ lines. The giant warning block at the top, repeated explanations of the targeting/enabled=False issue (mentioned at least 4 times), the full verbatim checklist to print, and explanations of concepts Claude can infer (like what agent vs completion mode means structurally) all waste significant tokens. The 'What NOT to Do' section repeats guidance already given in the workflow steps.

1 / 3

Actionability

The skill provides fully executable JSON payloads for both agent and completion modes, concrete curl commands for the targeting shortcut, specific MCP tool names with exact parameter formats, and clear examples of modelConfigKey values. The guidance is copy-paste ready throughout.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (Steps 1-5) with explicit validation checkpoints (Step 4 verification, Step 5 targeting confirmation). It includes feedback loops for error cases (NO MODEL fix, jq shape inspection), a decision matrix for mode selection, and explicitly calls out the most common failure mode with a concrete resolution path.

3 / 3

Progressive Disclosure

The skill references related skills (tools, configs-variations, configs-update, configs-targeting) but all content is inline in one monolithic file. The agent vs completion decision matrix, the modelConfigKey reference, the edge cases table, and the targeting shortcut commands could all be split into referenced files. However, there are no bundle files to split into, and the references to sibling skills are clearly signaled.

2 / 3

Total

9

/

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 does well at specifying concrete actions and is clearly distinctive to LaunchDarkly configuration. However, it lacks an explicit 'Use when...' clause which caps completeness, and uses second person voice ('Helps you'). Adding trigger guidance and adjusting voice would strengthen it.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about creating or configuring LaunchDarkly AI configs, setting up prompt variations, or choosing between agent and completion modes.'

Change 'Helps you choose' to third person voice like 'Guides selection between agent vs completion mode' to match expected description conventions.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'choose between agent vs completion mode', 'create the config', 'add variations with models and prompts', and 'verify the setup'. These are clear, actionable steps.

3 / 3

Completeness

Clearly answers 'what' (create and configure configs in LaunchDarkly with specific steps), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the what.

2 / 3

Trigger Term Quality

Includes 'LaunchDarkly', 'configs', 'agent', 'completion mode', 'variations', 'models', 'prompts' which are relevant but somewhat technical. Missing common user phrasings like 'feature flags', 'AI config', or 'LLM configuration'. Also uses second person 'Helps you' which is a minor voice issue.

2 / 3

Distinctiveness Conflict Risk

Very specific to LaunchDarkly config creation with distinct terminology like 'agent vs completion mode', 'variations with models and prompts'. Unlikely to conflict with other skills due to the specific product and workflow focus.

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.