Skip to main content
hc
Submit
skillsFirst-partyReview first Safety ✓ Privacy ✓
GitHub logo

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.

by JSONbored·added 2026-04-10·
Claude CodeCodexWindsurfGeminiCursorCLI
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
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-actions-secure-cicd-capability-pack
Source URLs
https://docs.github.com/actions, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/github-actions-secure-cicd-capability-pack.mdx
Brand
GitHub
Brand domain
github.com
Brand asset source
brandfetch
Package URL
/downloads/skills/github-actions-secure-cicd-capability-pack.zip
Package SHA256
171cde88dd94e324d349dfa76d0910dfd8bd3da54f1f22898331b04f5132e4b0
Safety notes
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
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.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2026-04-10

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

—

Delta

No baseline selected

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

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as first-party.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

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

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    Package marked verified.

    Done

  • Checksum metadata

    SHA-256 hash is present.

    Done

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

Difficulty

88/100

Adoption plan

Balanced adoption plan

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

Risk 0

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

    Listing has review metadata.

    Done

  • 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

    Package verification/checksum metadata is available.

    Done

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

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

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

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

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 available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

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

0/3 ready
Review & approval1General2

Safety & privacy surface

Safety & privacy surface

2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens.

3 areas
  • SafetyExecution & processesMay produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first.
  • SafetyCredentials & tokensUse least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.
  • PrivacyData retentionInputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration.
  • PrivacyCredentials & tokensRedact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.

Safety notes

  • 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

  • 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

  • Existing workflows or target CI/CD architecture
  • Branch protection and environment policy context
  • Security/compliance requirements

Schema details

Install type
package
Reading time
9 min
Difficulty score
88
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
171cde88dd94e324d349dfa76d0910dfd8bd3da54f1f22898331b04f5132e4b0
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-04-10
Retrieval sources
https://docs.github.com/actionshttps://docs.github.com/actions/security-for-github-actions/security-guides/automatic-token-authenticationhttps://docs.github.com/actions/learn-github-actions/reusing-workflows
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Apply the GitHub Actions secure CI/CD capability pack to this repository."

# Required output
1) Workflow threat model
2) Permissions and token scope plan
3) Supply-chain hardening changes
4) Reliability and failure-recovery checklist

About this resource

Knowledge Freshness

This capability pack is pinned to documentation verified on 2026-04-10. When upstream docs change, refresh endpoint contracts, examples, and constraints before using this skill for production changes.

Retrieval Sources

Always prefer direct retrieval from official docs/API references over model memory for limits, endpoint signatures, and behavior guarantees.

Core Workflow

  1. Confirm target version/runtime and pull latest official docs for the task scope.
  2. Build an execution plan with explicit read-only discovery before any mutation.
  3. Validate contracts, permissions, and safety constraints before applying changes.
  4. Execute with deterministic checkpoints and rollback criteria.
  5. Produce a verification report with evidence, caveats, and next actions.

Overview

This capability pack teaches agents how to build secure and resilient GitHub Actions systems. It focuses on practical controls that reduce compromise risk and operational breakage.

Capability Scope

  • Workflow architecture and trust boundaries
  • Token permissions and environment scoping
  • Action pinning and supply-chain controls
  • Reusable workflow governance
  • Build reliability and incident handling

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Production Rules

  • Grant minimum workflow permissions by job.
  • Pin third-party actions to immutable refs.
  • Separate trusted release workflows from untrusted PR execution.
  • Capture artifacts/logs for post-failure diagnostics.

Troubleshooting

Issue: CI passes in PRs but fails after merge
Fix: Align PR and main workflow environments and dependency assumptions.

Issue: Workflow has excessive token scope
Fix: Reduce permissions per job and isolate privileged steps to protected environments.

Issue: Third-party action risk is unclear
Fix: Pin exact versions/SHAs and periodically review upstream security posture.

Output Contract

  1. Provide an implementation plan ordered by risk and dependency.
  2. Provide exact production-ready config/commands with no placeholders.
  3. Call out secrets, permissions, and least-privilege requirements.
  4. Include rollback and recovery guidance for each risky step.

Validation Checklist

  • Verify all referenced docs/versions before applying changes.
  • Run regression checks for core user flow and error paths.
  • Confirm observability/logging is enabled for changed components.
  • Confirm security controls (auth, rate limits, input validation) still pass.
  • Record final known limitations and follow-up actions.
#github-actions#cicd#security#devops#capability-pack

Source citations

Add this badge to your README

Show that GitHub Actions Secure CI/CD 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
[![Listed on HeyClaude](https://heyclau.de/badge/skills/github-actions-secure-cicd-capability-pack.svg)](https://heyclau.de/entry/skills/github-actions-secure-cicd-capability-pack)

How it compares

GitHub Actions Secure CI/CD Capability Pack Skill side by side with 3 alternatives 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).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field
GitHub logoGitHub 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
GitHub logoGitHub Actions Security Review Capability Pack Skill

Expert GitHub Actions security review capability pack applying documented workflow hardening, GITHUB_TOKEN least privilege, secrets handling, and fork PR safety checks from official GitHub Actions security documentation.

Open dossier
GitHub logoGitHub 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
Code Review Automation Capability Pack Skill

Expert code-review capability pack for deterministic PR audits, risk-ranked findings, and low-noise fix planning without SaaS lock-in.

Open dossier
Next stepsDiffers
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verified2026-04-10Package not verifiedPackage not verifiedPackage verified2026-04-11
Source provenanceDiffersSource-backedSubmission linkedSource submissionSource-backedNo submission link
SubmitterDiffers—kiannidevJSONbored—
Install riskReview firstReview firstReview firstLow risk
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandGitHub logoGitHubGitHub logoGitHubGitHub logoGitHub—
Categoryskillsskillsskillsskills
Sourcefirst-partysource-backedsource-backedfirst-party
AuthorJSONboredkiannidevJSONboredJSONbored
Added2026-04-102026-06-162026-06-052026-04-11
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo————
Safety notes✓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.✓Workflow changes can exfiltrate secrets on fork PRs—review pull_request_target and untrusted checkout patterns. Over-broad permissions blocks increase blast radius—default to least privilege per hardening docs. Third-party actions are supply-chain dependencies—pin to commit SHA when policy requires.✓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.✓Installs from a downloaded package and may run local commands or scaffold files as part of the workflow; review the package and any generated changes before applying.
Privacy notes✓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.✓Review summaries may reference secret names but must not echo secret values. Redact internal runner labels and self-hosted paths in external tickets.✓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.✓Operates on your local project files and any context you share in the session; review what you expose before sharing — nothing is sent beyond the model unless a step calls an external service.
Prerequisites
  • Existing workflows or target CI/CD architecture
  • Branch protection and environment policy context
  • Security/compliance requirements
  • Workflow YAML files or PR diff containing GitHub Actions changes.
  • Repository branch protection and environments policy context.
  • Security reviewer before applying hardening to default branch.
  • 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.
  • Repository access and PR diff
  • Security severity policy
  • Test/lint/typecheck commands
Install
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
—
gh --version
curl -L https://heyclau.de/downloads/skills/coderabbit-lite-pr-review-capability-pack.zip -o coderabbit-lite-pr-review-capability-pack.zip && unzip -o coderabbit-lite-pr-review-capability-pack.zip -d ./coderabbit-lite-pr-review-capability-pack
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

guides

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by YB0y
guides

Auto Mode Hard-Deny Policies For Safe Automation

Set autoMode.hard_deny rules to block risky actions in auto mode.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by kiannidev
GitHub logoguides

Claude Code GitHub Actions Review Workflow

Automate PR review with Claude Code GitHub Actions using official setup steps.

Review firstSource-backedReview firstAdded 28d ago
Safety ✓ Privacy ✓by kiannidev

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.