devops

Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.

Quality

90%

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

80%

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

A well-organized, token-efficient overview with executable quick-start commands and a clear reference map. Its main gaps are missing validation/verification checkpoints for deployment workflows and two broken script reference paths that fail to resolve against the actual bundle.

Suggestions

Fix the two broken script references: change "scripts/cloudflare-deploy.py" → "scripts/cloudflare_deploy.py" and "scripts/docker-optimize.py" → "scripts/docker_optimize.py" to match the actual filenames.

Add a lightweight validation/verification step to deployment workflows (e.g., check `wrangler deploy` output URL, `kubectl rollout status`, or `gcloud run services describe` after deploy) so destructive/irreversible deploys have an explicit checkpoint.

Consider condensing the overlap between the "When to Use" list and the "Platform Selection" table, which cover similar ground.

Dimension	Reasoning	Score
Conciseness	The body is lean: a compact need→platform table, terse Quick Start commands, and one-line reference entries with no padding explaining what Docker or Kubernetes is. Every section earns its tokens.	3 / 3
Actionability	Quick Start provides copy-paste-ready, executable commands ("wrangler init my-worker && cd my-worker && wrangler deploy", "docker build -t myapp .", "gcloud run deploy ...", "kubectl apply -f manifests/"), and the Platform Selection table gives concrete decision guidance.	3 / 3
Workflow Clarity	Per-platform commands are concrete but there is no sequenced multi-step workflow with validation checkpoints — deployments are irreversible/batch-style operations with no verify step, which caps this dimension at 2 per the rubric's feedback-loop guidance.	2 / 3
Progressive Disclosure	Structure is otherwise well-organized with one-level-deep .md references that resolve, but two referenced script paths are broken: the body cites "scripts/cloudflare-deploy.py" and "scripts/docker-optimize.py" while the actual bundle files are cloudflare_deploy.py and docker_optimize.py (underscores), undermining navigation.	2 / 3
	Total	10 / 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.

A strong, third-person description that concisely names specific platforms and tools, includes an explicit "Use for" trigger clause, and occupies a clear niche. No significant weaknesses; the description reads naturally as something a user would say when they need this skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, specific capabilities and sub-tools — "Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm)" — naming granular components rather than vague categories.	3 / 3
Completeness	Explicitly answers both what ("Deploy to Cloudflare ... Docker, GCP ... Kubernetes") and when ("Use for serverless, containers, CI/CD, GitOps, security audit") with an explicit trigger clause.	3 / 3
Trigger Term Quality	The "Use for serverless, containers, CI/CD, GitOps, security audit" clause gives good coverage of natural terms a user would say, alongside recognizable platform names.	3 / 3
Distinctiveness Conflict Risk	The DevOps/cloud-deployment niche is clearly scoped to named platforms and tooling, with distinct triggers unlikely to overlap with unrelated skills.	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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: mrgoonie/claudekit-skills
Path: .claude/skills/devops/SKILL.md
Commit: 80113d8

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.