GitHub Artifact Attestation Provenance Capability Pack Skill

Expert skill for reviewing GitHub Artifact Attestations, release artifact digests, workflow provenance, OIDC boundaries, and public release evidence before an AI agent recommends or publishes build outputs.

by JSONbored·added 2026-06-05·

Claude Code Codex Windsurf Gemini Cursor CLI

HarnessClaude Code Codex Windsurf Gemini Cursor CLI

Level:expertType:capability-packVerified:validated

Command center

Source

Review first

Review safety and privacy notes before installing or copying commands.

Safety notes Privacy notes

Install & copy

gh --version

Trust & readiness

TrustReview first
Sourcesource-backed
Safety notesPresent
ReviewedNo

Community context

Related entries(4)
Related guides(3)
Community signals

Compare

Integrations & API

Contribute

Suggest a metadata change Claim this listing

Documentation Source repository Browse directory

Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL: https://heyclau.de/entry/skills/github-artifact-attestation-provenance-capability-pack
Source URLs: https://docs.github.com/en/actions/how-tos/secure-your-work/use-artifact-attestations/use-artifact-attestations, https://github.com/github/docs
Brand: GitHub
Brand domain: github.com
Brand asset source: brandfetch
Package URL: https://github.com/github/docs/archive/refs/heads/main.zip
Safety notes: Artifact attestation verification confirms provenance for a digest, not malware safety, runtime behavior, dependency health, or install trust., Do not approve a release when the verified repository, workflow, ref, subject digest, or commit does not match the artifact being distributed., Keep OIDC and workflow-permission review separate from ordinary release-note editing.
Privacy notes: Verification evidence can expose repository names, workflow names, internal release timing, commit SHAs, artifact names, and runner metadata., Public comments should summarize verification without pasting private URLs, unpublished release notes, or internal environment details.
Platform compatibility: claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author: JSONbored
Submitted by: JSONbored
Claim status: unclaimed
Last verified: 2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context

Selected

Current score

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Pending
Baseline comparison available
No baseline peer selected yet.
Pending
Diverging trust signals identified
No major trust-signal divergence found.
Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

6 listed

Install type

Package install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

Confirm source provenanceRequired
Source URL/provenance metadata is present.
Done
Confirm metadata review state
No review metadata found; increase manual validation.
Pending
Verify install payload
Install/config payload exists and can be inspected.
Done

Security checks

Confirm safety, privacy, and package integrity signals.

Review safety notesRequired
Safety notes are present.
Done
Review privacy notesRequired
Privacy notes are present.
Done
Verify package integrity metadata
No package verification/checksum metadata.
Pending

Rollout

Adopt in controlled steps based on the selected plan.

Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Pending
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Pending
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

3 prerequisites to line up before setup. Includes a review or approval gate.

0/3 ready

Install & runtime1Review & approval1General1

Safety & privacy surface

3 safety and 2 privacy notes across 3 risk areas. Review closely: permissions & scopes.

3 areas

SafetyExecution & processesArtifact attestation verification confirms provenance for a digest, not malware safety, runtime behavior, dependency health, or install trust.
SafetyGeneralDo not approve a release when the verified repository, workflow, ref, subject digest, or commit does not match the artifact being distributed.
SafetyPermissions & scopesKeep OIDC and workflow-permission review separate from ordinary release-note editing.
PrivacyExecution & processesVerification evidence can expose repository names, workflow names, internal release timing, commit SHAs, artifact names, and runner metadata.
PrivacyGeneralPublic comments should summarize verification without pasting private URLs, unpublished release notes, or internal environment details.

Safety notes

Artifact attestation verification confirms provenance for a digest, not malware safety, runtime behavior, dependency health, or install trust.
Do not approve a release when the verified repository, workflow, ref, subject digest, or commit does not match the artifact being distributed.
Keep OIDC and workflow-permission review separate from ordinary release-note editing.

Privacy notes

Verification evidence can expose repository names, workflow names, internal release timing, commit SHAs, artifact names, and runner metadata.
Public comments should summarize verification without pasting private URLs, unpublished release notes, or internal environment details.

Prerequisites

Release artifact, checksum, repository, workflow run, and commit SHA under review.
GitHub CLI available with access to verify attestations for the target repository.
Release policy that defines which artifacts require provenance evidence.

Schema details

Install type: package
Reading time: 9 min
Troubleshooting: No

Source repository stats

Scope: Source repo

Package metadata

Download URL: https://github.com/github/docs/archive/refs/heads/main.zip

Skill and platform metadata

Skill type: capability-pack
Skill level: expert
Verification: validated
Verified at: 2026-06-05

Retrieval sources

https://docs.github.com/en/actions/how-tos/secure-your-work/use-artifact-attestations/use-artifact-attestationshttps://docs.github.com/en/actions/how-tos/secure-your-work/use-artifact-attestations/using-artifact-attestations-to-establish-provenance-for-buildshttps://docs.github.com/en/actions/reference/security/oidchttps://github.com/github/docs

Tested platforms

ClaudeCodexCursorGeneric AGENTS

Platform	Support	Install path
claude-code	Native	.claude/skills/<skill-name>/SKILL.md
codex	Native	.agents/skills/<skill-name>/SKILL.md
windsurf	Native	.windsurf/skills/<skill-name>/SKILL.md
gemini	Native	.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursor	Adapter	.cursor/rules/<skill-name>.mdc
cli	Manual	AGENTS.md or tool-specific context file

Full copyable content

# Trigger
"Apply the GitHub artifact attestation provenance capability pack to this release."

# Required output
1) Artifact, digest, workflow, repository, and commit inventory
2) Attestation verification result and provenance summary
3) Release-blocking gaps or mismatches
4) Public-safe release evidence wording

About this resource

Knowledge Freshness

This capability pack is based on GitHub Artifact Attestation and OIDC documentation checked on 2026-06-05. Use the current GitHub docs and CLI help for command syntax, supported artifact types, and policy behavior.

Retrieval Sources

Core Workflow

Inventory the release artifact, package, checksum, repository, workflow run, commit SHA, ref, release tag, and distribution channel.
Confirm the build workflow generated the artifact and attestation in a trusted GitHub Actions context.
Verify the artifact with the expected owner and repository using GitHub CLI.
Compare the verification output to the release evidence: subject digest, builder identity, workflow, repository, commit, and ref.
Check for mismatches: renamed artifacts, local rebuilds, copied binaries, wrong repository, untrusted fork workflow, or stale release notes.
Produce a public-safe provenance summary and a private maintainer note for anything that should not be disclosed.
Block release recommendation when provenance is missing, mismatched, or only asserted in prose.

Capability Scope

GitHub Artifact Attestation evidence review
Release artifact digest and filename verification
Workflow provenance and OIDC boundary review
Release-note provenance wording
AI-assisted release recommendation guardrails
Privacy-safe summary of verification results

Compatibility

Native

Claude Code and Claude: use as a release review skill before publishing notes.
Codex: use when checking PRs, release branches, or package publication work.

Manual Adaptation

Generic AGENTS files: convert the workflow into a release provenance checklist.
Cursor and Windsurf: use the output contract for artifact review prompts.

Required Inputs

Artifact path and digest
Repository owner/name and expected release tag
Workflow run or build provenance evidence
Commit SHA and ref
Local or remote artifact location used for verification

Production Rules

Do not treat a filename, release note, or maintainer claim as proof of provenance.
Do not verify a different artifact from the one users download.
Do not ignore a repository, workflow, digest, commit, or ref mismatch.
Do not paste private verification logs into public comments.
Keep vulnerability scanning, malware review, and install trust as separate gates.
Require exact commands or reproducible evidence for the final release decision.

Output Contract

Artifact inventory and digest.
Verification command and result.
Provenance fields: repository, workflow, ref, commit, subject digest.
Blocking mismatches or missing evidence.
Public-safe release wording.
Follow-up checks outside attestation scope.

#github-actions #artifact-attestations #provenance #release-security #supply-chain

Source citations

Source methodology →

Add this badge to your README

Show that GitHub Artifact Attestation Provenance Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/skills/github-artifact-attestation-provenance-capability-pack.svg)](https://heyclau.de/entry/skills/github-artifact-attestation-provenance-capability-pack)

How it compares

GitHub Artifact Attestation Provenance Capability Pack Skill side by side with its closest alternative on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Field	GitHub Artifact Attestation Provenance Capability Pack Skill Expert skill for reviewing GitHub Artifact Attestations, release artifact digests, workflow provenance, OIDC boundaries, and public release evidence before an AI agent recommends or publishes build outputs. Open dossier	GitHub Actions Secure CI/CD Capability Pack Skill Expert GitHub Actions capability skill for secure workflow architecture, token minimization, supply-chain controls, and CI reliability. Open dossier
Next steps	Open dossier API JSON Open LLM Open source Newsletter Claim listing	Open dossier API JSON Open LLM Open source Newsletter Claim listing
Trust
Review status	Not reviewed	Not reviewed
Package trustDiffers	Package not verified	Package verified2026-04-10
Source provenanceDiffers	Source-backed	No submission link
SubmitterDiffers	JSONbored	—
Install risk	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Brand	GitHub	GitHub
Category	skills	skills
Source	Source-backed	First-party
Author	JSONbored	JSONbored
Added	2026-06-05	2026-04-10
Platforms	Claude Code Codex Windsurf Gemini Cursor CLI	Claude Code Codex Windsurf Gemini Cursor CLI
Harness	Claude Code Codex Windsurf Gemini Cursor CLI	Claude Code Codex Windsurf Gemini Cursor CLI
Source repo	—	—
Safety notes	✓Artifact attestation verification confirms provenance for a digest, not malware safety, runtime behavior, dependency health, or install trust. Do not approve a release when the verified repository, workflow, ref, subject digest, or commit does not match the artifact being distributed. Keep OIDC and workflow-permission review separate from ordinary release-note editing.	✓May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first. Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.
Privacy notes	✓Verification evidence can expose repository names, workflow names, internal release timing, commit SHAs, artifact names, and runner metadata. Public comments should summarize verification without pasting private URLs, unpublished release notes, or internal environment details.	✓Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration. Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.
Prerequisites	Release artifact, checksum, repository, workflow run, and commit SHA under review. GitHub CLI available with access to verify attestations for the target repository. Release policy that defines which artifacts require provenance evidence.	Existing workflows or target CI/CD architecture Branch protection and environment policy context Security/compliance requirements
Install	`gh --version`	`curl -L https://heyclau.de/downloads/skills/github-actions-secure-cicd-capability-pack.zip -o github-actions-secure-cicd-capability-pack.zip && unzip -o github-actions-secure-cicd-capability-pack.zip -d ./github-actions-secure-cicd-capability-pack`
Config	—	—
Citations	Source repositorygithub.com 2026-06-05 Documentationdocs.github.com Package downloadgithub.com Submitted by JSONbored2026-06-05 Source methodology →	Source repositorygithub.com 2026-07-20T14:55:19+00:00 Documentationdocs.github.com Package (SHA-256 pinned)/downloads/skills/github-actions-secure-cicd-capability-pack.zip Source methodology →
Claim	Unclaimed	Unclaimed

Open in the interactive comparison tool

Signals

Loading live community signals…

Citation facts

Review trust signals before you adopt

Source and provenance checks

Safety and privacy checks

Package and install checks

Compare-driven decision checks

Package install

Balanced adoption plan

Pre-adoption checks

Security checks

Rollout

Evidence readiness matrix · balanced

Source provenance

Metadata review

Safety notes

Privacy notes

Package integrity

Install payload

Decision timeline · balanced

Confirm source provenanceRequired

Check metadata review statusRequired

Review safety notesRequired

Review privacy notes

Validate package integrity metadata

Verify install payload and commandsRequired

Prerequisite readiness

Safety & privacy surface

Safety notes

Privacy notes

Prerequisites

Schema details

About this resource

Knowledge Freshness

Retrieval Sources

Core Workflow

Capability Scope

Compatibility

Native

Manual Adaptation

Required Inputs

Production Rules

Output Contract

Source citations

Add this badge to your README

How it compares

Related resources

GitHub Actions Secure CI/CD Capability Pack Skill

GitHub Actions Security Review Capability Pack Skill

Pull Request Triage Capability Pack Skill

GitHub Search Review Queue Statusline

Related guides

Package Provenance Checks Before Installing MCP Servers

Claude Code GitHub Actions Review Workflow

Pinning MCP Server Packages Before Installation

Signals