Expert SLSA provenance review skill for checking source, build, artifact, and trust evidence before accepting content or package submissions.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
86
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
5 prerequisites to line up before setup. Includes a review or approval gate.
Safety & privacy surface
4 safety and 2 privacy notes across 3 risk areas. Review closely: network access.
| 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 |
# Trigger
"Apply the SLSA provenance review capability pack to this submission."
# Required output
1) Source, package, artifact, and provenance evidence inventory
2) Expected producer, repository, revision, builder, and policy
3) SLSA source/build provenance review result
4) Acceptance, rejection, or manual-review decision with evidenceThis capability pack is pinned to SLSA v1.2 documentation and source files verified on 2026-06-03. Refresh the SLSA spec, provenance format, and package ecosystem behavior before using it for production policy decisions.
Prefer current SLSA specification pages and pinned source files over model memory for predicate details, verification expectations, and level-specific requirements.
This is not a HeyClaude submission-field factory. Use it for source and provenance review when a content, package, or registry intake needs evidence about where a submission came from, how an artifact was produced, and whether trust claims match the expected source.
SKILL.md-style instructions for registry, package, or artifact intake.Issue: The artifact has no provenance
Fix: Record the missing evidence and fall back to source, package, release, and maintainer judgment. Missing provenance may be acceptable for low-risk content but should block strong verification claims.
Issue: The provenance exists but the digest does not match
Fix: Treat the artifact as unverified. Ask for the exact artifact referenced by the provenance record or a new provenance record for the submitted artifact.
Issue: The source revision is a branch name
Fix: Resolve the branch to an immutable commit SHA, record when it was checked, and prefer a tag or release object when reviewing a published package.
Issue: The submitter claims SLSA compliance without evidence
Fix: Mark the claim unsupported. Require reachable source, builder, predicate, and verification evidence before using the claim in public metadata.
Issue: The evidence includes details that do not need to be public
Fix: Summarize only the identifiers needed for review and keep unnecessary operational details out of public issues or PRs.
Show that SLSA Provenance Review Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/slsa-provenance-review-capability-pack)SLSA Provenance Review Capability Pack Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
2 trust signals differ across this comparison (Source provenance, Submitter).
| Field | Expert SLSA provenance review skill for checking source, build, artifact, and trust evidence before accepting content or package submissions. Open dossier | Expert validation skill for reviewing /llms.txt, search discovery artifacts, canonical signals, structured data, and LLM-ready documentation links. Open dossier | Expert FastMCP review skill for auditing Python MCP server structure, tools, resources, prompts, transports, and deployment readiness before release. Open dossier | 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 |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenanceDiffers | Submission linkedSource submission | Submission linkedSource submission | Submission linkedSource submission | Source-backed |
| SubmitterDiffers | oktofeesh1 | oktofeesh1 | oktofeesh1 | JSONbored |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | |
| Category | skills | skills | skills | skills |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | oktofeesh1 | oktofeesh1 | oktofeesh1 | JSONbored |
| Added | 2026-06-03 | 2026-06-03 | 2026-06-03 | 2026-06-05 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Use this as a read-only evidence review workflow; ordinary intake should not require running submitted projects. The install command fetches a pinned SLSA source archive for reference, not an executable package. Provenance evidence improves confidence but does not replace human source review, category-fit review, or maintainer judgment. Treat missing, stale, unverifiable, or mismatched provenance as a risk signal and request clearer evidence before accepting strong trust claims. | ✓Installing `llms-txt` adds Python dependencies in the selected environment; pin the reviewed version and prefer project-scoped tooling. The `llms_txt2ctx` helper can retrieve linked HTTPS resources while expanding context; review target URLs before running it against private staging content. Search artifacts influence crawler and model-facing discovery signals; treat canonical, robots, sitemap, and structured data changes as publish-impacting. The source archive is external and version-pinned for reference; package trust should remain a maintainer decision. | ✓Installing FastMCP adds Python packages to the selected environment; use an isolated project environment and pin the reviewed version. Reviewing a server can exercise tool, resource, and prompt paths; use controlled fixtures and avoid live side effects unless the release plan explicitly permits them. The source ZIP is external and version-pinned for reference; package trust should remain a maintainer decision. Treat destructive tools, write-capable resources, network calls, and long-running jobs as release-blocking until their behavior is documented and tested. | ✓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 | ✓Work from public source URLs, release metadata, package metadata, and maintainer-approved context. Keep public notes focused on source URLs, revisions, digests, and high-level risk summaries; omit operational details that do not need to be public. | ✓`/llms.txt`, expanded context, sitemap, and structured data artifacts can expose URL paths, page titles, product terms, doc structure, and internal naming. Context expansion can collect linked markdown content into a single artifact, which may reveal more detail than the compact index. Keep public review notes focused on artifact shape, URL classes, stale links, and source evidence; avoid exposing private staging paths or unreleased content. | ✓FastMCP tools and resources can expose files, API responses, database records, prompts, and application state. Keep review notes focused on public source links, object names, version data, and summarized findings; omit operational details that do not need to be public. | ✓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 |
|
|
|
|
| Install | | | | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Validate /llms.txt, sitemap, robots, canonical, and structured data artifacts with source-backed checks and reviewer-ready evidence.
Review FastMCP servers with package/version checks, tool/resource/prompt inventory, runtime readiness, and release evidence.
Review GitHub artifact attestations, workflow provenance, digests, and release evidence.
Source-backed guides for putting this to work.
Verify MCP package provenance and publisher trust before adding servers to Claude Code.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.