CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configs-update

Update, retire, and delete LaunchDarkly configs and their variations. Use when you need to modify config properties, change model parameters, update instructions or messages, take unused configs out of service, or permanently remove them.

Quality

87%

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

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.

Highly actionable content with precise MCP tool invocations, a well-sequenced workflow, and strong safety gating around irreversible deletions. The main weakness is redundancy — the intro restates the description and key cautions are repeated multiple times, which inflates token cost without adding guidance.

Suggestions

Remove the opening paragraph that restates the description and workflow, letting the Prerequisites/Core Principles sections carry that framing.

State 'Configs cannot be archived' once (e.g., in Core Principles) and remove the three repeat mentions in Step 2, the retire section, and What NOT to Do.

Consolidate the repeated confirm:true / 'suggest turning targeting off first' guidance into a single confirmation convention defined before the workflow steps.

DimensionReasoningScore

Conciseness

The body is dense and operational with no filler concept explanations, but it could be tightened: the opening paragraph restates the description, 'Configs cannot be archived' appears four times, and the confirm:/suggest-targeting-off guidance repeats across sections.

3 / 5

Actionability

For an instruction-only skill it gives fully executable guidance: exact MCP tool names, resource values, and parameters ('get-agent-configs' with configKey and section: "health", 'update-agent-config' with resource: "targeting", on: false, confirm: true, maintainerId, modelConfigKey, defaultVariationKey), covering update, retire, delete, restore, and verify.

5 / 5

Workflow Clarity

A clear three-step sequence (assess health/state, make the change, verify) with an explicit verification step, error-recovery guidance ('Flag any issues or rollback if needed'; retry-by-verifying instead of trusting the echo), and destructive operations gated behind explicit user confirmation.

5 / 5

Progressive Disclosure

A single well-sectioned SKILL.md (no bundle files exist) with a clearly signaled external docs link and a Related Skills section; structure is good and content is appropriately placed, but at ~95 lines with no progressive-disclosure split it sits just below the top anchor.

4 / 5

Total

17

/

20

Passed

Description

88%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: concrete, third-person, and complete with an explicit 'Use when...' trigger clause covering the full update/retire/delete lifecycle. Keyword coverage is good but could add synonyms like 'decommission' that the body already uses, and some triggers blur into the sibling variations skill.

DimensionReasoningScore

Specificity

Names the domain ('LaunchDarkly configs and their variations') and enumerates multiple concrete actions — update, retire, delete, 'modify config properties', 'change model parameters', 'update instructions or messages', 'take unused configs out of service' — comprehensively covering the config lifecycle in third-person voice.

5 / 5

Completeness

Clearly answers both 'what' (first sentence listing the three lifecycle operations) and 'when' (an explicit 'Use when you need to...' clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('modify config properties', 'change model parameters', 'update instructions or messages', 'permanently remove them'), but misses a few synonyms the skill body itself surfaces, such as 'decommission' or 'roll back'.

4 / 5

Distinctiveness Conflict Risk

'LaunchDarkly configs' is a clear niche with distinct lifecycle triggers, but phrases like 'change model parameters' and 'update instructions or messages' overlap with the closely related configs-variations skill, creating minor conflict risk.

4 / 5

Total

18

/

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-update/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.