CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/syft-generation

Generates Software Bill of Materials (SBOMs) using Anchore Syft - supports container images / directories / archives across OCI / Docker / Singularity formats; output formats CycloneDX-JSON / SPDX-JSON / Syft-JSON / table / GitHub-JSON; pairs with `grype-scanning` for SBOM-driven vuln scanning. Use when the team needs SBOM artifacts for compliance (US EO 14028, EU CRA, FDA medical-device guidance) or as input to vuln scanners.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, lean overview with executable commands, a clear sequenced workflow including a validation checkpoint, and one-level-deep progressive disclosure backed by a real references file. It avoids concept re-explanation and pads nothing.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, omitting tutorial fluff like "what an SBOM is"; each section (Install, Basic generation, Attestation, CI) earns its place with executable content and no padded explanation.

3 / 3

Actionability

Copy-paste-ready, executable commands appear throughout (install snippets, `syft <image> -o cyclonedx-json`, cosign attest/verify, and a complete GitHub Actions YAML), with specific flags and concrete examples.

3 / 3

Workflow Clarity

An explicit numbered 8-step sequence (Install → Generate → Formats → Sources → Attest → Validate → CI → Composition) includes a validation checkpoint in Step 6 (diffing two SBOMs with `jq -S`) for inventory-accuracy verification, plus an Anti-patterns table reinforcing the sequence.

3 / 3

Progressive Disclosure

SKILL.md acts as a concise spine keeping common cases inline and clearly signals one-level-deep references to `references/formats.md` for the full format catalog and source-type syntax; the referenced file exists and contains exactly that, with no deeper nesting.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concrete, third-person, and answers both what and when with explicit compliance-driven triggers. It names specific formats, sources, and the sister scanning skill, making it highly distinctive.

DimensionReasoningScore

Specificity

Concrete actions and enumerated specifics are present: "Generates Software Bill of Materials (SBOMs)", listing both source types ("OCI / Docker / Singularity") and output formats ("CycloneDX-JSON / SPDX-JSON / Syft-JSON / table / GitHub-JSON"), matching the multiple-concrete-actions anchor.

3 / 3

Completeness

It explicitly answers both what (generates SBOMs via Syft with named formats/sources) and when via the "Use when the team needs SBOM artifacts for compliance...or as input to vuln scanners" clause, matching the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Natural user-facing terms appear ("SBOMs", "compliance", "vuln scanners") alongside concrete regulatory triggers ("US EO 14028, EU CRA, FDA medical-device guidance") that a user would actually cite, giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche (Anchore Syft SBOM generation) and pairs with a distinct sister skill (`grype-scanning`), making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents