github-actions-generator

Generate GitHub Actions workflows, custom actions, and reusable CI/CD pipelines with validation.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill github-actions-generator-100thieves-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions-generator
Source: https://github.com/100Thieves-team/plady-expert-skills/tree/main/.claude/skills/github-actions-generator
Command: npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill github-actions-generator-100thieves-team

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Writing GitHub Actions workflows by hand is error-prone: unpinned actions, overly broad permissions, and unsafe fork-PR handling create security risks, while syntax mistakes break pipelines. This Skill scaffolds workflows, custom actions, and reusable workflows following current security and naming standards, then validates every generated file. ## Core Features & Use Cases - Workflow Generation: Create CI/CD pipelines with pinned action SHAs, minimal permissions, concurrency controls, caching, and matrix strategies. - Custom Action Scaffolding: Generate composite, Docker, or JavaScript actions from templates with proper metadata, branding, and versioning. - Reusable Workflows & Security Scanning: Build workflow_call pipelines with typed inputs and explicit secrets, plus dependency review, SBOM attestation, and CodeQL configurations. - Use Case: A developer needs a Node.js CI pipeline that runs tests on pull requests without exposing secrets to forked repos. The Skill generates a workflow with read-only baseline permissions, an untrusted-PR guardrail, SHA-pinned actions, and validates the result before delivery. ## Quick Start Ask the assistant to create a GitHub Actions CI workflow for your repository that runs tests on push and pull requests with secure default permissions.

Frequently Asked Questions about github-actions-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub Actions CI/CD workflow?

Define your triggers, runners, and job steps, then generate a workflow with semantic names, pinned action SHAs, explicit permissions, and concurrency controls. The Skill routes the request through a decision tree and validates the output before delivery.

How to create a custom GitHub Action with composite, Docker, or JavaScript?

Choose composite for reusable step combinations, Docker for custom environments, or JavaScript for API interactions and complex logic. Templates under assets/templates/action provide the directory structure, metadata, and branding for each type.

Why should GitHub Actions be pinned to a commit SHA?

Pinning actions to a full commit SHA prevents supply-chain attacks where a mutable tag is repointed to malicious code. The Skill pins every third-party action to a SHA with a version comment and cites the source repository and release.

How do I prevent secrets leaking to forked pull requests in GitHub Actions?

Use a guardrail condition that skips secret-using jobs when the pull request head repository differs from the base repository. The Skill applies this untrusted-PR guardrail by default and keeps workflow-level permissions read-only.

What happens if the GitHub Actions validator skill is unavailable?

The Skill falls back to actionlint or yamllint if installed, otherwise performs a manual YAML and schema review with an explicit not-tool-validated note. Any fallback usage is always reported in the final output.