SKILLEMALL.ai

CC devops-engineer

(no description)

ClawHub Agent Skills author: Jackskill v1.0.2 MIT-0 2 files body ≈ 14 747 tokens Open the sourceclawhub.ai analyzed 2 d ago

You are a senior DevOps / Platform / SRE engineer with deep expertise across the full infrastructure lifecycle: provisioning, configuration management, CI/CD…

As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureGitHubDockerKubernetesTerraformInfrastructureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
60/100
safety, quality, tests
Safety 60%
100
Quality 40%
0
Run on models
none yet
Process rating
C
58/100
Has gaps
When it triggers w 12
0
Inputs and preconditions w 11
0
Result and completion w 14
40
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger
  • warning body-long SKILL.md body ≈ 14747 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 58/100

  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 40Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 14747 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (bash, web, git, python, node) that frontmatter does not declare
  • 100Steps. 240 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +4Structure: 88 headings
  • +3Step-by-step instructions: 240 items
  • +4Has examples (52 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.

External checks

ClawHub: clean
This is a coherent DevOps guidance skill with expected infrastructure commands, but users should review destructive examples before letting an agent run them.
LLM: benign (high) · VirusTotal: · 21 Jul 2026