infrastructure

云原生基础设施。Kubernetes、Helm、Kustomize、Operator、CRD、GitOps、ArgoCD、Flux、IaC、Terraform、Pulumi、CDK。当用户提到 K8s、Helm、GitOps、IaC 时路由到此。

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./templates/skills/domains/infrastructure/SKILL.md

Quality

Content

75%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 body is a dense, well-structured reference of commands, layouts, tables, and checklists that is token-efficient and actionable. Validation commands exist but explicit validate→fix→retry feedback loops for destructive IaC/GitOps operations are absent.

Suggestions

Add explicit feedback loops for destructive flows (e.g., after `terraform plan`: review output, fix errors, re-plan, only then apply).

Trim the '触发词' section, which duplicates the frontmatter trigger terms.

Consider offloading the large comparison tables (ArgoCD vs Flux, IaC tool对比) into a reference file to reduce inline length.

Dimension	Reasoning	Score
Conciseness	The body is dense reference material (commands, directory layouts, tables, checklists) that assumes Claude's competence and avoids concept re-explanation — efficient with only minor trimmable parts (the '触发词' section duplicates frontmatter triggers) — anchor 4, not 5 due to that redundancy.	4 / 5
Actionability	Pervasive copy-paste-ready commands ('helm lint', 'kubectl apply -k', 'terraform init → validate → fmt → plan → apply', 'pulumi preview → up') and concrete config keys — mostly executable, anchor 4, not 5 since entries are scattered bullets and config hints rather than complete worked examples.	4 / 5
Workflow Clarity	Clear command-flow sequences exist (Terraform, Pulumi, CDK, operator-sdk) with validation tools present (validate, lint, template, diff) and a 'review plan before apply' checklist checkpoint — anchor 4; not capped at 3 because validation is present, but not 5 since no explicit validate→fix→retry feedback loops.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets empty), so content is one self-contained ~200-line file organized into clear sections with headers, tables, and checklists — good structure with minor organization gaps (some comparison tables could be split out) — anchor 4, not 5 since nothing is offloaded to one-level-deep references.	4 / 5
	Total	16 / 20 Passed

Description

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

The description is concise and domain-specific with an explicit trigger clause, yielding strong completeness and distinctiveness. Its main weakness is specificity: it enumerates tools rather than stating concrete actions.

Suggestions

Replace the tool-list 'what' with concrete actions, e.g. 'Write Helm charts, manage Kustomize overlays, provision cloud resources with Terraform/Pulumi'.

Add a few more natural trigger synonyms (e.g. 'Kubernetes', 'infrastructure as code') alongside K8s and IaC.

Dimension	Reasoning	Score
Specificity	The description lists the domain and many tool nouns ('云原生基础设施。Kubernetes、Helm、Kustomize、Operator、CRD、GitOps...') but states no concrete actions — closest to anchor 2 ('names the domain but actions are minimal or generic'), and not 3 since there are zero action verbs.	2 / 5
Completeness	Answers 'what' (cloud-native infrastructure toolchain) and 'when' (route on K8s/Helm/GitOps/IaC mentions) with concrete trigger phrases; the 'what' is an enumeration rather than action-based, keeping it just below the 5 anchor.	4 / 5
Trigger Term Quality	Explicit triggers '当用户提到 K8s、Helm、GitOps、IaC 时路由到此' plus the broad tool list give good natural keyword coverage with synonyms (K8s, IaC), missing only a few variations — anchor 4, not 5 since coverage is not exhaustive.	4 / 5
Distinctiveness Conflict Risk	Clear niche (cloud-native infrastructure) with distinct, specific triggers (K8s, Helm, GitOps, IaC) and minimal conflict risk — matches anchor 5; not lowered because no evidence of overlapping sibling skills.	5 / 5
	Total	15 / 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: fengshao1227/ccg-workflow
Path: templates/skills/domains/infrastructure/SKILL.md
Commit: f349e3d

Reviewed: 5 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.