SKILLEMALL.ai
GitHub ↗ RU Sign in

DD gitops-knowledge

Flux CD and Flux Operator expert — answers questions and generates schema-validated YAML for all Flux CRDs (not repo auditing or live cluster debugging). Use when users ask about Flux concepts, want manifests for HelmRelease, Kustomization, GitRepository, OCIRepository, ResourceSet, FluxInstance, or any Flux resource. When user needs guidance on GitOps repository structure, bootstrap Flux with Terraform, multi-tenancy, OCI-based delivery, image tag automation, drift detection, preview environments, monorepo app delivery, running migration Jobs before or after a deployment, notifications, or the Flux Web UI and MCP Server.

Not recommendedcritical or high security findings · low grade D
fluxcd/agent-skills Agent Skills author: fluxcd 39 files body ≈ 3 682 tokens Open the sourcegithub.com↗ analyzed 10 h ago

Flux CD and Flux Operator expert — answers questions and generates schema-validated YAML for all Flux CRDs (not repo auditing or live cluster debugging).

As a process D 44/100 · Unfinished process — References files that are not bundled: assets/schemas/<kind>-<group>-<version>.fields.txt

GeneratorTerraformGitHubKubernetesInfrastructuretype 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
D
72/100
safety, quality, tests
Safety 60%
64
Quality 40%
83
Run on models
none yet
Process rating
D
44/100
Unfinished process
References files that are not bundled: assets/schemas/<kind>-<group>-<version>.fields.txt
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Secrets in code
If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 2

  • high Secrets in code secret-private-key references/sources.md:72
    Private key material (key header without key body)
    -----BEGIN PRIVATE KEY----- …
    header only
  • high Secrets in code secret-private-key references/sources.md:85
    Private key material (key header without key body)
    -----BEGIN PRIVATE KEY----- …
    header only

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: assets/schemas/<kind>-<group>-<version>.fields.txt
  • note edit-residue the text marks something as outdated (lines 12): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: assets/schemas/<kind>-<group>-<version>.fields.txt
  • 0Tools and files. 1 referenced file(s) missing: assets/schemas/<kind>-<group>-<version>.fields.txt
  • 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
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 36 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3682 tokens
  • 100Running it twice. Mutating operations check current state
  • low The response is described with custom markup (5 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
  • +2Single-language instructions
  • +3Description length 629: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 36 items
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (16 of 16)
  • +1License stated

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