Contract
- Input: software bill of materials (existing or target), build system, deployment pipeline, threat model.
- Output: SBOM policy + signing policy + SLSA target + vulnerability response runbook.
- Scope: designs security policy; does not patch dependencies or re-sign artifacts unless explicitly instructed.
- Rule: designs security policy; does not patch dependencies or re-sign artifacts unless explicitly instructed.
- Rule: documented standards override defaults; explicit project rules take precedence.
- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.
Provenance
| Question |
Answer |
| What is the source of truth? |
The user's request, originating spec/issue, and the skill's declared outputs |
| What is in scope? |
Work covered by the skill's acceptance criteria and completion rules |
| What is explicitly out of scope? |
Files, behaviors, and decisions outside the skill's declared boundary |
| Who or what consumes this artifact afterward? |
The next skill in the workflow or the user |
| What evidence proves it is done? |
Completion criteria met, artifact saved, validation passed |
| What risk remains? |
Subjective judgment calls, missing context, or external dependency failures |
Artifact
Emit SupplyChainSecurityArtifact as both:
- JSON:
.agents/skills/platform/artifacts/supply-chain-security/{identifier}.json
- Markdown view: same filename with
.md extension
Supply Chain Security
Design supply chain security — SBOM, Sigstore, SLSA, provenance, signing — with explicit trust tiers, artifact verification, and incident response for compromised dependencies.
Process
1. Inventory and SBOM policy
- Artifact types (container images, binaries, packages, libraries, firmware).
- SBOM format (SPDX, CycloneDX) and minimum granularity (package, file, container).
- Generation cadence (per-build, per-release, continuous).
- Storage and access (artifact registry, versioning, retention).
- Verification rules (SBOM present, signed, matches artifact hash).
Completion criterion: SBOM policy with format, cadence, and storage defined.
2. Artifact signing
- Signing authority (machine identity, build service, developer keys).
- Signing tool (Sigstore / Cosign, keyless vs key-based).
- Verification enforcement (admission controller, CI gate, deployment policy).
- Key rotation and revocation process.
Completion criterion: signing policy with enforcement points defined.
3. SLSA build tiers
- SLSA level target (L2: hosted build platform; L3: hard and hermetic).
- Build platform requirements (isolated, reproducible, ephemeral).
- Provenance attestation generation (SLSA provenance, in-toto).
- Verification by consumers (registry, deployment pipeline).
Completion criterion: SLSA target and build platform requirements documented.
4. Dependency management
- Dependency allow-list and deny-list (internal, open source, critical CVE history).
- Update policy (automated Dependabot / Renovate, review cadence).
- Lock files and pinned versions enforced.
- Transitive dependency visibility (SBOM includes transitive deps).
Completion criterion: dependency management policy with update and pinning rules defined.
5. Vulnerability response
- Scanning cadence (per-build, nightly, on CVE publication).
- SLA by severity (critical: 24h; high: 7d; medium: 30d; low: 90d).
- Triage and patch process (upstream fix, patch release, CVE acceptance).
- Communication plan (security advisories, customer notifications).
Completion criterion: vulnerability SLA and response runbook defined.
6. Audit and compliance
- Attestation verification in CI/CD and runtime.
- Periodic audit of signing keys, SBOM accuracy, and SLSA compliance.
- Evidence collection for compliance (SOC 2, FedRAMP, ISO 27001).
- Incident response for compromised artifacts (revocation, re-sign, customer notification).
Completion criterion: audit schedule and incident response runbook defined.
Rules
- Rule: generate SBOM for every artifact; never ship without it.
- Rule: verify signatures at every stage: build, registry, deploy, runtime.
- Rule: target SLSA L3 for production artifacts; document exceptions with risk acceptance.
- Rule: automate dependency updates and vulnerability scanning; manual review only for exceptions.
- Rule: maintain an incident response runbook for supply chain compromise.
Completion
- the skill's completion criteria are explicitly checked
- the artifact is saved and validated
- any blockers or skipped validations are documented
- the next consumer is identified or the work is handed off
@include .agents/skills/platform/contract-base.xml
1---2name: "supply-chain-security"3category: "sec"4maturity: "stable"5version: "1"6description: "Design supply chain security — SBOM, Sigstore, SLSA, provenance, signing — with explicit trust tiers, artifact verification, and incident response for compromised dependencies."7license: "MIT"8capabilities:9 - apply supply chain security methods within explicit sec boundaries10 - analyze design supply chain security — sbom, sigstore, slsa, provenance, signing — with explicit trust tiers, artifact verification, and incident response for compromised dependencies with assumptions, constraints, and failure modes11 - produce and validate a sec artifact with evidence, decisions, and next steps12outputs: "SBOM policy + signing policy + SLSA target + vulnerability response runbook."13sideEffects: []14dependencies: []15stopCondition: "SBOM policy defined; signing policy defined; SLSA target and attestation documented."16risk: "medium"17trustTier: "3"18maxIterations: "6"19promptVersion: "2.0"20artifactType: "security"21modelTier: "reasoning"22evaluators: ["behavioral", "regression"]23fixturesPath: .agents/skills/platform/fixtures/behavioral/supply-chain-security.json24diataxis: "how-to"25tags: ["sec"]26compatibility: []27approvalRequired: "true"28approvalFor: []29metadata:30 source: https://skillmd.com/skills/quantumquirkxyz/supply-chain-security31---3233## Contract3435- Input: software bill of materials (existing or target), build system, deployment pipeline, threat model.36- Output: SBOM policy + signing policy + SLSA target + vulnerability response runbook.37- Scope: designs security policy; does not patch dependencies or re-sign artifacts unless explicitly instructed.38- Rule: designs security policy; does not patch dependencies or re-sign artifacts unless explicitly instructed.39- Rule: documented standards override defaults; explicit project rules take precedence.40- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.4142## Provenance4344| Question | Answer |45|---|---|46| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |47| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |48| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |49| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |50| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |51| What risk remains? | Subjective judgment calls, missing context, or external dependency failures525354## Artifact5556Emit `SupplyChainSecurityArtifact` as both:57- JSON: `.agents/skills/platform/artifacts/supply-chain-security/{identifier}.json`58- Markdown view: same filename with `.md` extension596061# 62# 63# Supply Chain Security6465Design **supply chain security** — SBOM, Sigstore, SLSA, provenance, signing — with explicit trust tiers, artifact verification, and incident response for compromised dependencies.6667## Process6869### 1. Inventory and SBOM policy70- Artifact types (container images, binaries, packages, libraries, firmware).71- SBOM format (SPDX, CycloneDX) and minimum granularity (package, file, container).72- Generation cadence (per-build, per-release, continuous).73- Storage and access (artifact registry, versioning, retention).74- Verification rules (SBOM present, signed, matches artifact hash).7576**Completion criterion:** SBOM policy with format, cadence, and storage defined.7778### 2. Artifact signing79- Signing authority (machine identity, build service, developer keys).80- Signing tool (Sigstore / Cosign, keyless vs key-based).81- Verification enforcement (admission controller, CI gate, deployment policy).82- Key rotation and revocation process.8384**Completion criterion:** signing policy with enforcement points defined.8586### 3. SLSA build tiers87- SLSA level target (L2: hosted build platform; L3: hard and hermetic).88- Build platform requirements (isolated, reproducible, ephemeral).89- Provenance attestation generation (SLSA provenance, in-toto).90- Verification by consumers (registry, deployment pipeline).9192**Completion criterion:** SLSA target and build platform requirements documented.9394### 4. Dependency management95- Dependency allow-list and deny-list (internal, open source, critical CVE history).96- Update policy (automated Dependabot / Renovate, review cadence).97- Lock files and pinned versions enforced.98- Transitive dependency visibility (SBOM includes transitive deps).99100**Completion criterion:** dependency management policy with update and pinning rules defined.101102### 5. Vulnerability response103- Scanning cadence (per-build, nightly, on CVE publication).104- SLA by severity (critical: 24h; high: 7d; medium: 30d; low: 90d).105- Triage and patch process (upstream fix, patch release, CVE acceptance).106- Communication plan (security advisories, customer notifications).107108**Completion criterion:** vulnerability SLA and response runbook defined.109110### 6. Audit and compliance111- Attestation verification in CI/CD and runtime.112- Periodic audit of signing keys, SBOM accuracy, and SLSA compliance.113- Evidence collection for compliance (SOC 2, FedRAMP, ISO 27001).114- Incident response for compromised artifacts (revocation, re-sign, customer notification).115116**Completion criterion:** audit schedule and incident response runbook defined.117118## Rules119120- Rule: generate SBOM for every artifact; never ship without it.121- Rule: verify signatures at every stage: build, registry, deploy, runtime.122- Rule: target SLSA L3 for production artifacts; document exceptions with risk acceptance.123- Rule: automate dependency updates and vulnerability scanning; manual review only for exceptions.124- Rule: maintain an incident response runbook for supply chain compromise.125126## Completion127128- the skill's completion criteria are explicitly checked129- the artifact is saved and validated130- any blockers or skipped validations are documented131- the next consumer is identified or the work is handed off132---133@include .agents/skills/platform/contract-base.xml