CtrlK
BlogDocsLog inGet started
Tessl Logo

cloud-devops

Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.

50

Quality

55%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/cloud-devops/SKILL.md

The canonical home for this skill is cloud-devops in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 skill is a well-structured routing bundle that clearly sequences cloud/DevOps phases and points to sub-skills, but it offers little executable technical guidance and lacks per-phase validation checkpoints for its destructive/batch operations.

Suggestions

Add per-phase validation/verification steps (e.g., 'terraform plan' before apply, 'kubectl rollout status' after deploy) so destructive and batch operations include feedback loops.

Make the numbered Actions executable by including concrete commands or example snippets rather than abstract verbs like 'Design cloud architecture'.

Consider moving detailed per-provider/per-phase skill listings into reference files so the SKILL.md overview stays lean and one level deep.

DimensionReasoningScore

Conciseness

The body is structured and free of concept over-explanation, but the repeated trivial one-line 'Copy-Paste Prompts' duplicate information already in each phase's skills-to-invoke list.

4 / 5

Actionability

Copy-paste prompts to invoke named sub-skills are concrete, but the numbered 'Actions' are abstract (e.g., 'Design cloud architecture') with no executable code, commands, or manifests.

3 / 5

Workflow Clarity

Seven phases are clearly sequenced with a final Quality Gates checklist, but there are no per-phase validation checkpoints or feedback loops for destructive/batch operations like deployments and infra provisioning, capping the score at 3.

3 / 5

Progressive Disclosure

The content is well-organized into clear sections with no bundle files to navigate, but as a single ~226-line monolithic file it could benefit from splitting detailed phases into one-level-deep references.

4 / 5

Total

14

/

20

Passed

Description

48%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 clearly scopes the cloud/DevOps domain with strong natural trigger terms but lacks concrete actions and any explicit 'when to use' guidance. Its breadth also creates notable overlap risk with the very sub-skills it references.

Suggestions

Add a 'Use when...' clause naming concrete triggering situations (e.g., provisioning multi-cloud infra, setting up a CI/CD pipeline, deploying to Kubernetes).

Replace 'workflow covering' with concrete verbs (e.g., 'Provisions, orchestrates, deploys, and monitors cloud infrastructure across AWS/Azure/GCP').

Narrow scope or add a distinguishing qualifier so this bundle does not collide with individual provider/terraform/kubernetes skills.

DimensionReasoningScore

Specificity

The description names the domain and enumerates sub-domains (AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring) but uses only 'workflow covering' with no concrete verbs or actions.

2 / 5

Completeness

It has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

It includes natural terms users would say (AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, DevOps), though a few synonyms and variations are missing.

4 / 5

Distinctiveness Conflict Risk

It is a very broad umbrella spanning many sub-domains it itself routes to (aws-skills, kubernetes, terraform, etc.), creating high overlap risk with those specific skills.

2 / 5

Total

11

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.