detecting-infrastructure-drift
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill detecting-infrastructure-driftExecute 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
50%This skill provides a reasonable framework for drift detection with good output examples and error handling coverage, but falls short on actionability by describing steps rather than providing executable commands. The workflow lacks validation checkpoints critical for infrastructure operations, and contains unnecessary boilerplate sections that waste tokens.
Suggestions
Replace procedural descriptions with actual executable commands (e.g., show 'terraform plan -detailed-exitcode' instead of 'Execute drift detection command')
Add explicit validation checkpoints between drift detection and remediation steps, such as 'Review drift report before proceeding' with criteria for when to stop
Remove the empty 'Overview' and 'Examples' sections at the end, or populate them with concrete usage patterns
Move the extensive error handling section to a separate TROUBLESHOOTING.md file and reference it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary boilerplate (generic 'Overview' and 'Examples' sections at the end add nothing), and the prerequisites section explains things Claude would know. However, the core content is reasonably focused. | 2 / 3 |
Actionability | Provides example output formats and remediation commands, but lacks executable code for actually performing drift detection. The instructions are procedural descriptions rather than concrete commands (e.g., 'Execute drift detection command' without showing the actual command). | 2 / 3 |
Workflow Clarity | Steps are listed sequentially but lack explicit validation checkpoints. For infrastructure operations that can be destructive, there's no feedback loop for verifying drift detection results before remediation, and no explicit 'stop and verify' steps. | 2 / 3 |
Progressive Disclosure | References external resources appropriately, but the document itself is somewhat monolithic. The error handling section could be a separate reference file, and the empty 'Examples' section suggests incomplete structure. | 2 / 3 |
Total | 8 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific actions, excellent trigger terms that users would naturally say, explicit 'when to use' guidance, and a clear niche that distinguishes it from other infrastructure-related skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'detecting infrastructure drift', 'compare actual vs desired state', 'detect configuration changes', and names specific tools like 'terraform plan, cloudformation drift detection, or manual comparison'. | 3 / 3 |
Completeness | Clearly answers both what (identifies discrepancies between current infrastructure and IaC definitions using specific tools) and when (explicit 'Trigger with phrases like...' clause provides clear usage guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would say: 'check for drift', 'infrastructure drift detection', 'compare actual vs desired state', 'detect configuration changes'. These are realistic phrases DevOps users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche focused on infrastructure drift detection with distinct triggers like 'drift', 'IaC', 'terraform plan', 'cloudformation'. Unlikely to conflict with general infrastructure or code skills due to the specific drift-detection focus. | 3 / 3 |
Total | 12 / 12 Passed |
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.