AF devops-pipeline-management
Expert for DevOps pipeline management, handling the complete lifecycle of pipelines on the quality and efficiency platform. Core capabilities: 1) Workspace management - Query workspace lists with filtering 2) Pipeline management - Create, query, update, and delete pipelines 3) Execution management - Execute and cancel pipelines, query execution records and details 4) Template management - Query pipeline templates and create pipelines from templates Trigger scenarios: - Users need to search for workspaces or pipelines - Users need to execute or run pipelines - Users need to check pipeline execution status or logs - Users need to create, update, or delete pipelines - Users need to query pipeline templates
Expert for DevOps pipeline management, handling the complete lifecycle of pipelines on the quality and efficiency platform.
As a process F 31/100 · Will not run — References files that are not bundled: references/workspace-list.md, docs/pipeline_skill.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/workspace-list.md - warning
missing-refreference to a missing file: docs/pipeline_skill.md
Process rating: all ten parameters 31/100
- 0Tools and files. 2 referenced file(s) missing: references/workspace-list.md, docs/pipeline_skill.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 25 mutating operations with no state check
- 70Execution cost. Instruction body is 4029 tokens
- 100Steps. 58 steps
- 100Consistency. Name and required fields are in place
- low 20 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 tags): a typed call is more reliable
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
- +1No license
- +2Single-language instructions
- +3Description length 713: enough signal without eating the budget
- +4Structure: 68 headings
- +3Step-by-step instructions: 58 items
- +4Has examples (29 code blocks)
- +4Reference files are cited in the instructions (13 of 14)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.