SKILLEMALL.ai
GitHub ↗ RU Sign in

CC sbom-supply-chain-security-expert

Supply chain security, CycloneDX SBOM, Cosign signing, SLSA Level 3 / Keamanan rantai pasok software, SBOM CycloneDX, dan tanda tangan Cosign.

The skillemall take

Promises guidance on SBOM generation (CycloneDX/SPDX), Sigstore Cosign keyless signing, and SLSA Level 3 provenance. Single file, no scripts. Safety score 100, quality 72, process 50—no critical findings, no lint errors.

Never tested on models. Process score suggests incomplete or vague instructions. For production supply chain security, this is thin. Use as a starting template, but validate all outputs before deployment.

roedyrustam/vibes-plug Agent Skills author: roedyrustam 1 file body ≈ 2 800 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Supply chain security, CycloneDX SBOM, Cosign signing, SLSA Level 3 / Keamanan rantai pasok software, SBOM CycloneDX, dan tanda tangan Cosign.

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

ProcedureGitHubKubernetesDockerSoftware developmenttype 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
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
C
50/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 50/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 100Steps. 17 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2800 tokens
  • 100Progress reporting. Reports progress

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 142: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (3 code blocks)

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