create-runtime-setting
Create a new RuntimeSetting that can be changed at runtime via `agent config set/get` and the config API
57
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/create-runtime-setting/SKILL.mdQuality
Discovery
57%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 is reasonably specific about what it does—creating a RuntimeSetting accessible via a particular config API—and occupies a clear niche unlikely to conflict with other skills. However, it lacks an explicit 'Use when...' clause and could benefit from broader natural-language trigger terms to help Claude select it reliably.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to add a new runtime-configurable setting, configuration option, or dynamic parameter.'
Include natural-language trigger term variations such as 'configuration option', 'dynamic setting', 'add a setting', 'runtime configuration' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific domain (RuntimeSetting) and a concrete action (create), and mentions the mechanism (`agent config set/get` and config API), but only describes one action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Clearly answers 'what' (create a new RuntimeSetting changeable at runtime via specific interfaces), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'RuntimeSetting', 'agent config set/get', 'config API', and 'runtime', which are useful but fairly technical. Missing common natural-language variations a user might say like 'add a setting', 'configuration option', 'runtime config', or 'dynamic setting'. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche—creating RuntimeSettings with a particular API (`agent config set/get`)—which is unlikely to conflict with other skills. The domain is narrow and well-defined. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill that provides a clear end-to-end workflow for creating RuntimeSettings in the Datadog Agent codebase. Its greatest strengths are the precise file paths, concrete method requirements, and explicit verification steps. Minor improvements could be made in reducing some redundancy and potentially splitting reference details into supporting files.
Suggestions
Remove the duplicated mention of CLI/HTTP API exposure (appears in both the intro and Important Notes) to improve conciseness.
Consider extracting the detailed service registration paths (Step 1.7) into a separate reference file to improve progressive disclosure and reduce the main skill's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy — the API/CLI exposure is mentioned in both the introduction and Important Notes, and some details (like the config key often being the same as the setting name) could be trimmed. However, most content is project-specific knowledge Claude wouldn't have, so the verbosity is mostly justified. | 2 / 3 |
Actionability | The skill provides specific file paths, exact glob patterns, concrete method signatures, specific bash commands for testing, and precise registration locations in named files. Claude knows exactly what to create, where to put it, and how to verify it. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with logical dependencies (gather info → read references → implement → test → register → verify). Step 6 includes explicit validation with test execution and linting, plus a feedback loop to fix issues if they fail. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's a moderately long monolithic file with no references to supporting documents. The detailed registration site list and type conversion details could potentially be split out, though for a single skill file without bundle support this is acceptable. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- DataDog/datadog-agent
- Commit
a41685a
- 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.