create-config-field
Add a new configuration field to the Datadog Agent (datadog.yaml)
54
62%
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-config-field/SKILL.mdQuality
Discovery
32%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 narrowly focused on a specific product (Datadog Agent) and file (datadog.yaml), which helps with distinctiveness, but it is too terse. It lacks a 'Use when...' clause, provides only a single action without elaboration, and misses common keyword variations that would help Claude select it appropriately.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to add a new config option, parameter, or setting to the Datadog Agent's datadog.yaml file.'
List more specific concrete actions involved, such as 'defines the field schema, adds default values, updates validation logic, and documents the new option'.
Include natural trigger term variations like 'config option', 'agent setting', 'YAML parameter', 'datadog config', 'agent configuration' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific domain (Datadog Agent configuration) and one action (add a configuration field), but does not list multiple concrete actions or elaborate on what adding a field entails (e.g., updating schema, validation, documentation). | 2 / 3 |
Completeness | Describes what (add a configuration field to datadog.yaml) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also thin, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Datadog Agent', 'datadog.yaml', and 'configuration field' that a user might mention, but misses common variations like 'config option', 'agent setting', 'YAML config', or 'new parameter'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Datadog Agent' and 'datadog.yaml' provides some specificity, but 'add a new configuration field' is generic enough that it could overlap with other configuration-related skills or general YAML editing skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, well-structured skill that provides precise, project-specific guidance for adding configuration fields to the Datadog Agent. Its greatest strengths are the comprehensive subsystem mapping tables, concrete code examples, and clear multi-step workflow with validation. The only minor weakness is that all content is inline rather than leveraging bundle files for reference material like the subsystem tables.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every table, code snippet, and note earns its place by providing project-specific knowledge Claude wouldn't have (file paths, function names, subsystem mappings, build commands). No unnecessary explanations of Go concepts or general programming. | 3 / 3 |
Actionability | Provides fully concrete guidance: exact file paths, specific Go function names, executable code snippets for BindEnvAndSetDefault, precise build/lint commands, and clear references to existing files to use as patterns. The step-by-step process with AskUserQuestion integration is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit validation in Step 4 (build, lint, generate-config). The workflow includes decision points (which subsystem, inline vs dedicated file, user-facing or not) and a feedback loop (report results to user). The information-gathering step ensures all needed context is collected before proceeding. | 3 / 3 |
Progressive Disclosure | The content is well-structured with tables and clear sections, but everything is inline in a single file. The subsystem tables and key methods reference could potentially be split into separate reference files. However, given no bundle files exist, the skill is reasonably sized and self-contained, though it's on the longer side for a single file. | 2 / 3 |
Total | 11 / 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.