drift-detector

Detect infrastructure drift between Terraform state and actual cloud resources. Identifies unmanaged resources, manual changes, and configuration drift. Use when: - User asks to check for infrastructure drift - User wants to find unmanaged cloud resources - User mentions "drift detection" or "Terraform drift" - User asks to compare cloud state to IaC - User wants to audit infrastructure changes

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is highly actionable with executable commands and a clear phased workflow, but loses points for command redundancy, missing validation feedback loops before destructive remediation, and broken/mismatched bundle references.

Suggestions

Add an explicit validation checkpoint before destructive remediation in Phase 4.2 (e.g., run a dry-run/confirm step and re-scan before deleting unmanaged resources).

Fix progressive disclosure: either create the referenced SERVICES.md and EXAMPLES.md files, or point the body's references to the existing references/drift-remediation.md so signaled paths resolve to real files.

Remove the duplicated basic scan command from Quick Start or Phase 2.1 and trim the "Core Principle" line to reduce token redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence (no "what is Terraform" padding), but the basic `snyk iac describe --from=tfstate://terraform.tfstate` command recurs in both Quick Start and Phase 2.1, and lines like "Core Principle: Your cloud should match your code." add little — so it is efficient but could be tightened.	2 / 3
Actionability	It provides fully executable, copy-paste-ready commands throughout (`snyk iac describe`, `aws sts get-caller-identity`, `terraform import`, GitHub Actions YAML), matching the level-3 anchor.	3 / 3
Workflow Clarity	The five phases (Setup, Detect, Analyze, Remediate, Prevention) are clearly sequenced with setup verification, but Phase 4.2 performs destructive deletion ("delete unmanaged resources") with only an implied "After verification" rather than an explicit validate→fix→retry checkpoint, capping clarity at 2 per the destructive-operations guideline.	2 / 3
Progressive Disclosure	The body signals references to `SERVICES.md` (line 59) and `EXAMPLES.md` (line 307), but neither file exists in the bundle; the only bundled file, `references/drift-remediation.md`, is never referenced from the body. The references are present in spirit but mismatched and not correctly signaled.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is third-person, concise, and explicitly covers both what the skill does and when to use it with natural trigger terms. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	"Detect infrastructure drift between Terraform state and actual cloud resources. Identifies unmanaged resources, manual changes, and configuration drift." lists multiple concrete actions (detect, identify unmanaged, manual changes, config drift), matching the level-3 anchor.	3 / 3
Completeness	It explicitly answers both what ("Detect infrastructure drift... Identifies unmanaged resources, manual changes, and configuration drift") and when (an explicit "Use when:" clause with five triggers), matching the level-3 anchor.	3 / 3
Trigger Term Quality	Phrases like "drift detection", "Terraform drift", "find unmanaged cloud resources", "compare cloud state to IaC", and "audit infrastructure changes" are natural terms a user would actually say, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The Terraform/IaC-vs-cloud drift niche is distinct, with specific triggers unlikely to fire for unrelated skills, matching the level-3 anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: snyk/studio-recipes
Commit: fffe731

Reviewed: 15 days 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.