CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

manage-iacm

Manage Harness Infrastructure as Code Management (IaCM) via MCP. Configure Terraform workspaces with remote state and RBAC, set up continuous drift detection with auto-remediation, design multi-tier change approval workflows, and estimate infrastructure costs before deployment. Use when asked to manage Terraform workspaces, detect infrastructure drift, set up approval workflows for infrastructure changes, or estimate Terraform costs. Do NOT use for creating Harness infrastructure definitions (use create-infrastructure instead) or OPA policies (use create-policy instead). Trigger phrases: terraform, workspace, drift detection, infrastructure cost, IaCM, state management, change approval, terraform plan, infracost, infrastructure governance.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

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

The content is well-organized and token-efficient with genuinely useful domain guidance (RBAC tiers, drift severity classification, break-glass rationale), but it reads more like a design checklist than an operational skill: the key pipeline example is pseudocode, and no step includes validation or verification. Splitting the four workflows into reference files would improve both actionability and disclosure.

Suggestions

Replace the comment-only pipeline spec in Step 5 with an executable harness_create body (real stage specs, actual infracost/terraform step configuration) or a complete copy-paste-ready example.

Add explicit validation checkpoints after each risky operation, e.g. verify workspace creation via harness_list, confirm the approval pipeline triggers on a plan, and require a post-apply drift scan before declaring success.

Move the four per-task workflows (workspace/state management, drift detection, approval design, cost estimation) into one-level-deep reference files under references/ and keep SKILL.md as a routing overview with clear links.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows (no 'what is Terraform' padding) and stays tight throughout, e.g. 'Classify drift by severity: critical (security group changes, IAM), warning (tags, descriptions), info (metadata)'. A few policy-style bullets ('Remote state backend with encryption at rest and state locking') and the descriptive checklist style could be trimmed slightly, so it fits 'efficient; minor instances of over-explanation' rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

The harness_list call is concrete, but the harness_create pipeline body is comment-only pseudocode ('# terraform plan + output change summary', '# infracost diff', '# risk-based approval routing') and most guidance is descriptive checklists ('Design workspace structure: One workspace per environment per account') rather than executable steps. This matches 'some concrete guidance but incomplete; pseudocode instead of executable code' rather than 4, which expects mostly executable guidance.

3 / 5

Workflow Clarity

The six-step sequence is clearly labeled and ordered, but there are no validation or verification checkpoints anywhere (nothing confirms a workspace was created, a pipeline is valid, or drift scans ran correctly). Because the skill routes destructive terraform apply operations, the rubric's cap on workflows lacking validation applies, holding this at 3 even though the sequencing alone would merit 4.

3 / 5

Progressive Disclosure

The single ~145-line file covers four distinct task workflows (workspace/state, drift, approvals, cost) plus troubleshooting, all of which are prime candidates for one-level-deep reference files; none exist (no references/, scripts/, or assets/ directories). It has clear section headers but fits 'content that should be separate is inline' (3) better than the appropriately-placed-content anchor at 4.

3 / 5

Total

13

/

20

Passed

Description

96%Weight 40%Scale 1-5

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 description: it uses third-person voice, enumerates four concrete capabilities, provides an explicit 'Use when' clause with a comprehensive trigger-phrase list, and adds negative boundary guidance to prevent mis-triggering against sibling skills. The only weakness is that a couple of very generic trigger terms ('terraform', 'workspace') could pull it into contexts outside Harness IaCM.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'Configure Terraform workspaces with remote state and RBAC, set up continuous drift detection with auto-remediation, design multi-tier change approval workflows, and estimate infrastructure costs' — with comprehensive coverage of the skill's domain. It matches the 'multiple specific concrete actions; comprehensive coverage' anchor and does not fall to 4, which expects minor gaps in coverage.

5 / 5

Completeness

It explicitly answers both 'what' (the four concrete actions) and 'when' ('Use when asked to manage Terraform workspaces, detect infrastructure drift, set up approval workflows for infrastructure changes, or estimate Terraform costs'), plus concrete trigger phrases and negative boundaries. This matches the anchor for clearly and explicitly answering both what AND when.

5 / 5

Trigger Term Quality

The explicit trigger list — 'terraform, workspace, drift detection, infrastructure cost, IaCM, state management, change approval, terraform plan, infracost, infrastructure governance' — comprehensively covers natural user phrasing including synonyms (IaCM, infracost, terraform plan). It matches the comprehensive-coverage anchor rather than the 'a few natural terms missing' anchor at 4.

5 / 5

Distinctiveness Conflict Risk

The 'Do NOT use for creating Harness infrastructure definitions (use create-infrastructure instead) or OPA policies (use create-policy instead)' clause establishes a clear niche with explicit disambiguation. However, the generic triggers 'terraform' and 'workspace' carry minor overlap risk with non-Harness Terraform-related skills, fitting 'mostly distinct; minor overlap risk' (4) better than 'minimal conflict risk' (5).

4 / 5

Total

19

/

20

Passed

Validation

100%

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

harness/harness-ai

Path

plugins/claude/skills/manage-iacm/SKILL.md

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.