Verifying Build Provenance with Slsa Sigstore
Verify signed artifacts and SLSA build provenance with Sigstore cosign and slsa-verifier, enforce keyless OIDC identity, and apply SLSA Build levels to harden the software supply chain.
Install
npx skills add adriannoes/awesome-agentic-ai --skill verifying-build-provenance-with-slsa-sigstoregit clone --depth 1 https://github.com/adriannoes/awesome-agentic-ai.git /tmp/awesome-agentic-ai
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-agentic-ai/cursor-claude-codex/skills/anthropic-cybersecurity-skills/skills/verifying-build-provenance-with-slsa-sigstore ~/.claude/skills/verifying-build-provenance-with-slsa-sigstorePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Verifying Build Provenance with SLSA and Sigstore ## Overview Build-provenance verification answers a question that defeats many supply-chain attacks: *was this artifact actually built from the source I think it was, by the builder I trust, without tampering?* Attackers who compromise a build system, swap a compiled release, or inject a malicious step (as in the SolarWinds and 3CX incidents) produce artifacts that look legitimate but lack verifiable provenance. SLSA (Supply-chain Levels for Software Artifacts, https://slsa.dev) defines Build levels (L1–L3) describing increasing provenance integrity, and Sigstore (https://www.sigstore.dev) provides the signing and transparency infrastructure: **cosign** for signing/verifying artifacts and attestations, **Fulcio** for short-lived keyless certificates bound to an OIDC identity, and **Rekor** as a tamper-evident transparency log. This skill covers verifying signatures and SLSA provenance with **cosign** (`cosign verify`, `cosign verify-attestation`, `cosign verify-blob-attestation`) and **slsa-verifier** (`slsa-verifier verify-artifact`), enforcing the builder identity (the GitHub Actions workflow that produced the artifact) and the expected source repository. Keyless verification ties trust to an OIDC issuer (e.g., `https://token.actions.githubusercontent.com`) and a certificate identity rather than a long-lived private key.
Details
- Skill name
verifying-build-provenance-with-slsa-sigstore- Repository
- adriannoes/awesome-agentic-ai
- Path
cursor-claude-codex/skills/anthropic-cybersecurity-skills/skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
FAQ
What does the Verifying Build Provenance with Slsa Sigstore skill do?
Verify signed artifacts and SLSA build provenance with Sigstore cosign and slsa-verifier, enforce keyless OIDC identity, and apply SLSA Build levels to harden the software supply chain.
How do I install the Verifying Build Provenance with Slsa Sigstore skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add adriannoes/awesome-agentic-ai --skill verifying-build-provenance-with-slsa-sigstore. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Verifying Build Provenance with Slsa Sigstore popular?
It lives in adriannoes/awesome-agentic-ai, which has 100 GitHub stars and 27 forks, and is included in 2 curated skill lists.
Related skills
Browserstack
100adriannoes/awesome-agentic-ai
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
Coverage
100adriannoes/awesome-agentic-ai
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
Fix
100adriannoes/awesome-agentic-ai
Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".
X Devs
88jonathimer/devmarketing-skills
When the user wants to build a developer following on Twitter/X, write technical threads, or understand what works for dev audiences on X. Trigger phrases include "Twitter," "X," "developer Twitter," "tech Twitter," "technical threads," "building dev following," or "Twitter for developers.
Typescript Best Practices
100adriannoes/awesome-agentic-ai
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
Shadinglanguagex
49jakethorn/ShadingLanguageX
Write, debug, explain and compile ShadingLanguageX (SLX), the C-like shading language in `.mxsl` files that the mxslc++ compiler turns into MaterialX (`.mtlx`) node graphs. Use for any task involving .mxsl source, MaterialX materials written as code, porting GLSL/Shadertoy/OSL snippets to SLX, running the compiler (`mxslc` CLI, Python `import mxslc` from `pip install mxslcxx`, C++, JS/WASM), compile options (globals, entry functions, macros, reduce_graph, MaterialX versions), decompiling .mtlx back to SLX, or explaining which MaterialX nodes an SLX construct produces.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.