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.

60

Quality

70%

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 with executable examples, a clearly sequenced workflow, and explicit validation checklists. Its main weakness is repetition of the targeting warning and inline density that could benefit from splitting into reference files.

Suggestions

Consolidate the enabled=False/targeting warning to a single canonical location and reference it rather than restating it in the callout, Step 5, and 'What NOT to Do'.

Move the direct curl/CLI targeting shortcut and the modelConfigKey format list into a references/ file and link to it from SKILL.md to reduce inline length.

Trim the 'What NOT to Do' list to items not already covered inline, or fold unique items into their relevant steps.

DimensionReasoningScore

Conciseness

Mostly efficient and task-focused, but the enabled=False/targeting warning is repeated three times (top callout, Step 5, and 'What NOT to Do') and the 'What NOT to Do' section largely restates earlier guidance, so it could be tightened.

3 / 5

Actionability

Provides copy-paste-ready JSON payloads for both agent and completion modes, concrete curl/CLI commands, exact field names, and specific gotchas (modelName vs name, updateFallthroughVariationOrRollout) covering the common cases.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with an explicit verification checklist in Step 4 and a verbatim user-facing checklist in Step 5, including a feedback loop (verify targeting flip before claiming success).

5 / 5

Progressive Disclosure

Well-organized with clear section headers and one-level references to sibling skills and external docs, but all ~235 lines live inline in SKILL.md with no bundle files, so some content (curl shortcut, modelConfigKey list, edge cases) could be split out.

4 / 5

Total

17

/

20

Passed

Description

58%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 concretely states what the skill does across the create/configure/verify workflow but omits any explicit 'when to use' trigger guidance, capping completeness. It is well-niched to LaunchDarkly with solid specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating or configuring an AI config in LaunchDarkly, choosing agent vs completion mode, or adding model-backed variations.'

Include natural user synonyms/phrasings (e.g. 'AI config', 'LLM config', 'agent config') to improve trigger-term coverage.

Mention the make-servable/targeting step briefly so the description reflects the full workflow scope.

DimensionReasoningScore

Specificity

Lists several concrete actions ('create the config, add variations with models and prompts, and verify the setup', 'choose between agent vs completion mode') with only minor coverage gaps (e.g., making the variation servable is not mentioned).

4 / 5

Completeness

The 'what' is clearly stated but there is no 'Use when...' or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant domain terms ('configs', 'LaunchDarkly', 'agent vs completion mode', 'variations') are present but common synonyms and natural user phrasings are missing, and there is no explicit trigger clause.

3 / 5

Distinctiveness Conflict Risk

The LaunchDarkly AI-config niche is clear and distinct from generic skills, with only minor overlap risk against sibling skills like configs-variations or configs-targeting.

4 / 5

Total

14

/

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.

Validation16 / 16 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.