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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is action-rich with concrete IaC commands and a clear error table, but it loses points for a redundant Overview, a lack of validation checkpoints around destructive remediation, and failure to integrate the existing bundle (an unmentioned drift-check.sh and a broken Pulumi reference link). Tightening the Overview and wiring in the helper script would lift the weaker dimensions.

Suggestions

Trim or remove the Overview paragraph so it does not duplicate the numbered Instructions, improving token efficiency.

Add an explicit validation checkpoint before destructive remediation (e.g. review the plan and confirm before running 'terraform apply') and fold the Error Handling rows into the workflow as a retry loop.

Reference the existing scripts/drift-check.sh from the Instructions and fix the empty Pulumi drift-detection link in Resources so the bundle is actually signaled and navigable.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient (no over-explanation of what drift or Terraform is), but the Overview paragraph ('Run drift detection commands, analyze modified/added/deleted resources, generate drift reports...') restates what the numbered Instructions already cover, so it could be tightened — matching 'mostly efficient but could be tightened'.	2 / 3
Actionability	Concrete, copy-paste-ready commands throughout: 'terraform plan -detailed-exetcode' with exit-code semantics, 'aws cloudformation detect-stack-drift', 'pulumi preview', and remediation commands like 'terraform apply', 'terraform import' — matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Steps 1–9 are clearly sequenced, but the workflow recommends destructive remediation ('terraform apply' in step 7) with no validation checkpoint or feedback loop before enforcing desired state, and the Error Handling table is not woven back into the flow — the guideline caps workflow clarity at 2 when destructive/batch operations lack validation steps.	2 / 3
Progressive Disclosure	Sections are well organized, but the body never references the actual bundle (e.g. the real scripts/drift-check.sh helper is present yet unmentioned), and the Resources section includes a broken/empty Pulumi link; content stays inline rather than signaling the one-level-deep references that exist — matching 'some structure but references not clearly signaled'.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong: it states concrete capabilities, includes natural trigger phrases, explicitly pairs what and when, and carves out a distinct, low-conflict niche. The only minor flaw is slightly awkward phrasing ('Execute use when') rather than the cleaner 'Use when' form.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and tools: 'Identifies discrepancies between current infrastructure and IaC definitions using terraform plan, cloudformation drift detection, or manual comparison' — matches the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('Identifies discrepancies...using terraform plan, cloudformation drift detection') and when ('Execute use when detecting infrastructure drift...Trigger with phrases like...'), matching the 'both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say: 'check for drift', 'infrastructure drift detection', 'compare actual vs desired state', 'detect configuration changes' — good coverage matching the top anchor.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (infrastructure drift from IaC state) with distinctive triggers, making it unlikely to fire for unrelated skills — matches the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/devops/infrastructure-drift-detector/skills/detecting-infrastructure-drift/SKILL.md
Commit: 0540a62

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.