terraform-cc008-migration

Migrates Terraform charm and product modules to the CC008 Charm Terraform Standards, enforcing the required file layout, variable and output contracts, MAJOR_VERSION markers, module tests and the operator-workflows reusable CI workflows. Use whenever a repository's Terraform modules must be brought to (or audited against) CC008.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%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.

A well-structured, highly actionable migration runbook: explicit module classification before rule application, per-category contracts, executable commands, and a mandatory validation loop with a quality bar. The spec is correctly externalized via progressive disclosure. Weakest points are mild verbosity in a few explanatory passages and YAML examples that are fragments rather than complete files.

Suggestions

Tighten the subordinate-charm determination paragraph in "DO — Charm Modules": condense the charmcraft.yaml walk-up and subordinate-key semantics into a compact 2-3 line rule, leaving edge cases to the spec.

Provide one complete, copy-paste-ready workflow file example (e.g. the full terraform_modules_compliance.yaml with trigger, permissions and the reusable-workflow call) instead of separate fragments for permissions and paths filters.

Move the operator-workflows reference URLs and finished-migration PR links into a short references section or the spec bundle to trim the secondary-references block.

Dimension	Reasoning	Score
Conciseness	The body explicitly avoids restating the spec ("This skill does not restate the spec; it only reinforces the parts that are most often missed") and sticks to non-obvious, project-specific rules. A few passages run long, e.g. the subordinate-charm units determination procedure and the paths-filter rationale, which could be tightened.	4 / 5
Actionability	Mostly executable guidance: copy-paste commands for module discovery (`find . -type f -name 'main.tf' ...`), SHA pinning (`git ls-remote ...`), validation (`tflint --init && tflint --recursive`, the checker script), plus concrete YAML fragments. The workflow snippets are illustrative fragments rather than complete copy-paste workflow files, which keeps it below the fully-executable anchor.	4 / 5
Workflow Clarity	A clear, ordered pipeline — read the spec first, discover and classify every module, apply universal rules then category-specific rules, wire CI, housekeeping, validate — with an explicit feedback loop: "Run the checker against every discovered module and iterate until it passes clean" and a final Quality Bar checklist.	5 / 5
Progressive Disclosure	The 46KB specification is properly externalized to assets/cc008.spec.md as the declared source of truth, with one-level-deep, well-signaled references (including an explicit authority ordering) that resolve to real bundle files; the body carries only deltas and repository plumbing the spec omits.	5 / 5
	Total	18 / 20 Passed

Description

92%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.

A strong description: third-person voice, concrete enumerated capabilities, and an explicit "Use whenever..." trigger clause. Only minor gap is the absence of a few natural synonyms (Juju, terraform-compliance) that users might phrase the request with.

Dimension	Reasoning	Score
Specificity	"enforcing the required file layout, variable and output contracts, MAJOR_VERSION markers, module tests and the operator-workflows reusable CI workflows" lists multiple specific concrete actions covering the full migration surface, matching the comprehensive-coverage anchor.	5 / 5
Completeness	It clearly answers both: what ("Migrates Terraform charm and product modules to the CC008 Charm Terraform Standards, enforcing...") and when ("Use whenever a repository's Terraform modules must be brought to (or audited against) CC008").	5 / 5
Trigger Term Quality	Natural terms users would say are present ("Terraform", "charm", "CC008", "compliance", "audited", "CI workflows"), but a few common variants are missing (e.g. "Juju", "compliance check failing in CI"), so it is good-but-not-comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	A clear niche (CC008 Charm Terraform Standards migration/audit) with distinct trigger terms; minimal overlap risk with generic Terraform skills since CC008 and charm-module vocabulary are unique to this domain.	5 / 5
	Total	19 / 20 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: canonical/copilot-collections
Path: groups/platform-engineering/skills/terraform-cc008-migration/SKILL.md
Commit: d41d8d9

Reviewed: 1 day 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.