BC ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Promises CI/CD pipeline automation: build setup, test configuration, deployment strategies. One instruction file with 2985 tokens, no scripts, no critical issues. Quality score 85, process score 56—the gap suggests the logic is there, but reproducibility lags. No model testing, no sandbox runs. Compatible with all major agents from Claude to DeepSeek.
Works for basic pipeline setup: the instruction is solid enough and security-clean. But if you need certainty it'll work on your stack, test it on a dummy repo first before committing.
Automates CI/CD pipeline setup.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 16 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2985 tokens
- low 14 top-level sections: this looks like several domains in one skill
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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 207: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (14 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.