detecting-infrastructure-drift
Execute use when detecting infrastructure drift from desired state. Trigger with phrases like "check for drift", "infrastructure drift detection", "compare actual vs desired state", or "detect configuration changes". Identifies discrepancies between current infrastructure and IaC definitions using terraform plan, cloudformation drift detection, or manual comparison.
78
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/devops/infrastructure-drift-detector/skills/detecting-infrastructure-drift/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its purpose, provides explicit trigger phrases, and specifies the tools and methods used. It covers the what, when, and how effectively, making it easy for Claude to select this skill when appropriate. The only minor issue is the slightly awkward opening 'Execute use when' phrasing, but the content is otherwise excellent.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Identifies discrepancies between current infrastructure and IaC definitions', 'using terraform plan, cloudformation drift detection, or manual comparison'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Identifies discrepancies between current infrastructure and IaC definitions using terraform plan, cloudformation drift detection, or manual comparison') and when ('detecting infrastructure drift from desired state', with explicit trigger phrases). Has an explicit 'Trigger with phrases like...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'check for drift', 'infrastructure drift detection', 'compare actual vs desired state', 'detect configuration changes', plus tool-specific terms like 'terraform plan', 'cloudformation drift detection'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche around infrastructure drift detection with distinct triggers like 'drift', 'actual vs desired state', 'terraform plan', 'cloudformation drift detection'. Unlikely to conflict with other infrastructure or DevOps skills due to the narrow focus on drift specifically. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable overview of infrastructure drift detection with useful error handling and resource links, but falls short on actionability—key steps are described abstractly rather than with executable code. The workflow lacks validation checkpoints before destructive operations like terraform apply, and the content could be more concise by removing explanatory text Claude doesn't need.
Suggestions
Add executable code blocks for key operations: a complete bash script or step-by-step commands for running drift detection and parsing output, rather than inline command fragments.
Add explicit validation checkpoints before remediation steps—e.g., 'Review the drift report and confirm with the user before running terraform apply' to prevent unintended destructive changes.
Remove the Examples section (prompt examples don't teach Claude how to perform the task) and trim the Output section to focus on the actual report format/schema rather than listing deliverable categories.
Provide a concrete drift report template or JSON schema showing expected output structure, rather than just describing what should be in it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity—explaining what drift is, listing prerequisites Claude can infer, and providing example prompts that don't add instructional value. The error handling table and resources section are useful but the overall content could be tightened significantly. | 2 / 3 |
Actionability | Concrete commands are provided inline (terraform plan -detailed-exitcode, aws cloudformation detect-stack-drift) but there are no executable code blocks or copy-paste-ready scripts. Steps like 'generate a structured drift report' and 'determine if drift is intentional' are vague and lack concrete implementation details. | 2 / 3 |
Workflow Clarity | Steps are listed in a logical sequence covering detection through remediation, but there are no explicit validation checkpoints or feedback loops. Steps 5-9 are advisory rather than actionable workflow steps, and there's no 'validate then proceed' pattern for the destructive remediation commands like terraform apply. | 2 / 3 |
Progressive Disclosure | The content is organized into clear sections (Prerequisites, Instructions, Output, Error Handling, Resources) which is good, but it's somewhat monolithic—the error handling table and detailed output specifications could be in separate reference files. External links are provided but no internal file references for deeper content. | 2 / 3 |
Total | 8 / 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 | |
- Commit
c8a915c
- 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.