Implementing Sigstore for Software Signing
Implements Sigstore-based software signing and verification using Cosign keyless signing, Rekor transparency log verification, and Fulcio certificate authority integration to establish cryptographic provenance for container images, binaries, and software artifacts. The practitioner configures OIDC-based identity binding, verifies signing events against the Rekor transparency log, and integrates signing workflows into CI/CD pipelines. Activates for requests involving software supply chain signing, keyless container signing, Sigstore deployment, or artifact provenance verification.
Install
npx skills add adriannoes/awesome-agentic-ai --skill implementing-sigstore-for-software-signinggit 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/implementing-sigstore-for-software-signing ~/.claude/skills/implementing-sigstore-for-software-signingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Implementing Sigstore for Software Signing ## When to Use - Signing container images and software artifacts without managing long-lived cryptographic keys - Establishing verifiable provenance for build outputs in CI/CD pipelines using OIDC identity binding - Querying the Rekor transparency log to audit when and by whom an artifact was signed - Verifying that container images pulled from registries were signed by authorized identities and issuers - Integrating Sigstore verification into Kubernetes admission controllers to enforce signed-image policies **Do not use** for signing artifacts that require air-gapped or offline signing workflows where OIDC authentication is unavailable, for environments that cannot reach the public Sigstore infrastructure (Fulcio, Rekor) and have no private instance deployed, or as a replacement for traditional PGP/GPG signing where regulatory compliance mandates specific key management procedures. ## Prerequisites - Cosign CLI v2.4+ installed (`go install github.com/sigstore/cosign/v2/cmd/cosign@latest` or binary release) - Access to an OIDC identity provider supported by Fulcio (Google, GitHub, Microsoft, or a custom OIDC issuer) - Container registry credentials (for signing container images) with push access to store signature objects - Python 3.9+ with `sigstore`, `requests`, and `cryptography` packages for the automation agent
Details
- Skill name
implementing-sigstore-for-software-signing- Repository
- adriannoes/awesome-agentic-ai
- Path
cursor-claude-codex/skills/anthropic-cybersecurity-skills/skills/implementing-sigstore-for-software-signing/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
FAQ
What does the Implementing Sigstore for Software Signing skill do?
Implements Sigstore-based software signing and verification using Cosign keyless signing, Rekor transparency log verification, and Fulcio certificate authority integration to establish cryptographic provenance for container images, binaries, and software artifacts. The practitioner configures OIDC-based identity binding, verifies signing events against the Rekor transparency log, and integrates signing workflows into CI/CD pipelines. Activates for requests involving software supply chain signing, keyless container signing, Sigstore deployment, or artifact provenance verification.
How do I install the Implementing Sigstore for Software Signing skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add adriannoes/awesome-agentic-ai --skill implementing-sigstore-for-software-signing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Implementing Sigstore for Software Signing 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".
Loop Library
100adriannoes/awesome-agentic-ai
Discover, find, compare, audit, repair, adapt, and design repeatable AI-agent loops with explicit triggers, actions, verification, stopping conditions, guardrails, and handoffs. Use when a user asks to analyze a codebase for potential loops, mine coding-thread history for work done more than once, turn repeated engineering work into a loop, find or recommend a published loop, create a recurring agent workflow or automation cadence, turn an outcome into a bounded copy-ready loop, or review an existing loop for weak checks, unsafe authority, unbounded repetition, stale state, or unclear stopping
Implementing Code Signing for Artifacts
100adriannoes/awesome-agentic-ai
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment pipelines.
Mapear
100adriannoes/awesome-agentic-ai
Use to map an existing (brownfield) codebase and produce docs/architecture/assessment.md — stack, architecture, implicit bounded contexts, maturity across the 5 axes, debts/risks, and historical decisions to become retroactive ADRs. Re-running updates the assessment. It is called by /kickoff in brownfield mode, and also runs standalone when the codebase changes or to analyze a repo. Trigger with /mapear.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.