CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

manage-supply-chain

Manage Harness Software Supply Chain Assurance (SSCA) via MCP. Configure automated SBOM generation with CycloneDX or SPDX formats, set up artifact signing and attestation with Cosign, define supply chain security policies using OPA, and track SLSA provenance levels. Use when asked to generate SBOMs, sign artifacts, enforce supply chain policies, track software provenance, or manage SLSA compliance. Do NOT use for OPA pipeline governance policies (use create-policy instead) or vulnerability scanning (use security-report instead). Trigger phrases: SBOM, software bill of materials, supply chain security, SLSA, artifact signing, cosign, provenance, attestation, CycloneDX, SPDX, supply chain policy.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The content is a well-structured, mostly actionable workflow guide with two concrete MCP tool calls (including a complete Rego policy example) and useful troubleshooting and performance sections. Its main gaps are the missing MCP calls for the SBOM-configuration and storage steps, the absence of post-configuration validation steps, and minor padding in the Performance Notes.

Suggestions

Add the concrete MCP tool calls (tool name and parameters) for Step 3 (SBOM generation configuration) and Step 5 (SBOM storage and dashboard setup) so those steps are executable rather than descriptive, matching the pattern already shown in Steps 1 and 4.

Add explicit validation checkpoints after configuration, e.g., verifying the policy was created and testing enforcement against a sample artifact before considering the workflow complete.

Trim the Performance Notes of advisory filler (e.g., "SBOM storage costs are minimal (JSON files) but retention policies prevent unbounded growth") and convert Step 3/Step 5 descriptive bullets into direct configuration instructions.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (it never explains what SBOM, Cosign, or OPA are) and uses dense, directive bullet lists, so it is mostly efficient. Minor instances could be trimmed, e.g. "SBOM storage costs are minimal (JSON files) but retention policies prevent unbounded growth" and "acceptable for most pipelines" in Performance Notes, plus descriptive (rather than instructive) bullets in Step 3 and Step 5. This fits the score-4 anchor (efficient, minor trimmable over-explanation) rather than 5, but is clearly above 3 since no known concepts are re-taught.

4 / 5

Actionability

Concrete executable guidance exists: the harness_list call with parameters and the complete harness_create call with a full Rego policy body, plus enumerated concrete options ("CycloneDX 1.5 (JSON) or SPDX 2.3 (JSON)", "Cosign keyless (Sigstore), Cosign with KMS, AWS KMS, GCP KMS"). However Steps 3 and 5 ("Configure SBOM generation in the CI pipeline", "Configure SBOM storage") only describe what to configure without the actual MCP tool calls to do it. Mostly executable with minor gaps fits score 4, not 5 (Steps 3/5 are not copy-paste ready) and not 3 (real executable code is present, not pseudocode).

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit input checkpoints ("Confirm the user's org, project, service, and build tool", "Gather from the user", "Gather enforcement points from the user") and the Troubleshooting section supplies error-recovery loops for signing and policy failures. Missing are post-configuration validation steps (e.g., verifying the policy was created or testing enforcement against a sample artifact), which keeps it at score 4 rather than 5, but checkpoints are present rather than implicit so it is above score 3.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is a single, well-organized document with clear sections (numbered Instructions, Examples, Performance Notes, Troubleshooting) and easy navigation. At roughly 127 lines with a full Rego policy inlined, some content (e.g., additional policy examples) could be split into reference files, so it fits score 4 (good structure, content mostly appropriately placed) rather than 5, which expects well-signaled one-level-deep references or a clearly appropriate split.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

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

This is an exemplary description: it names four concrete capabilities with specific technologies, provides an explicit 'Use when' clause with concrete triggers, and includes explicit negative boundaries that disambiguate it from sibling skills. It is specific, complete, and conflict-resistant while staying concise.

DimensionReasoningScore

Specificity

"Configure automated SBOM generation with CycloneDX or SPDX formats, set up artifact signing and attestation with Cosign, define supply chain security policies using OPA, and track SLSA provenance levels" lists multiple specific concrete actions with named technologies and formats, giving comprehensive coverage. It exceeds the score-4 anchor (which allows minor coverage gaps) because formats, tools, and the tracking capability are all explicitly named.

5 / 5

Completeness

The description explicitly answers what ("Manage Harness Software Supply Chain Assurance (SSCA) via MCP. Configure automated SBOM generation... set up artifact signing... define supply chain security policies... track SLSA provenance levels") and when ("Use when asked to generate SBOMs, sign artifacts, enforce supply chain policies, track software provenance, or manage SLSA compliance") with concrete trigger phrases. Both halves are explicit, matching the score-5 anchor rather than score 4 where the 'when' could be more specific.

5 / 5

Trigger Term Quality

"Trigger phrases: SBOM, software bill of materials, supply chain security, SLSA, artifact signing, cosign, provenance, attestation, CycloneDX, SPDX, supply chain policy" gives comprehensive coverage including synonyms (both the abbreviation SBOM and its expansion), both format standards, and tool names a user would naturally say. This matches the score-5 anchor rather than score 4, which expects a few natural terms to be missing.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Harness SSCA via MCP) with explicit negative boundaries: "Do NOT use for OPA pipeline governance policies (use create-policy instead) or vulnerability scanning (use security-report instead)" actively disambiguates against sibling skills. Minimal conflict risk, matching the score-5 anchor; it is not score 4 because explicit redirection to alternative skills removes even the minor overlap risk.

5 / 5

Total

20

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

harness/harness-ai

Path

plugins/claude/skills/manage-supply-chain/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.