SKILLEMALL.ai
GitHub ↗ RU Sign in

BF deployment-pipeline-design

Architecture patterns for multi-stage CI/CD pipelines with approval gates and deployment strategies.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 2 171 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Architecture patterns for multi-stage CI/CD pipelines with approval gates and deployment strategies.

As a process F 52/100 · Will not run — References files that are not bundled: assets/approval-gate-template.yml, references/pipeline-orchestration.md

ProcedureGitHubKubernetesGitLabDockerInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
F
52/100
Will not run
References files that are not bundled: assets/approval-gate-template.yml, references/pipeline-orchestration.md
Tools and files w 18
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 3 more places: agentic-awesome-skills, agentic-awesome-skills, RA-Skills

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: assets/approval-gate-template.yml
  • warning missing-ref reference to a missing file: references/pipeline-orchestration.md
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "date_added"

Process rating: all ten parameters 52/100

Will not run. References files that are not bundled: assets/approval-gate-template.yml, references/pipeline-orchestration.md
  • 0Tools and files. 2 referenced file(s) missing: assets/approval-gate-template.yml, references/pipeline-orchestration.md
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 22 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 60 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2171 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)
  • +3Description length 100: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 29 headings
  • +3Step-by-step instructions: 60 items
  • +4Has examples (12 code blocks)

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