@tank/github-actions-mastery

Design secure GitHub Actions workflows with SHA pinning and OIDC federation.

1|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/tankpkg/packages --skill tank-github-actions-mastery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: @tank/github-actions-mastery
Source: https://github.com/tankpkg/packages/tree/main/skills/github-actions-mastery
Command: npx skills add https://github.com/tankpkg/packages --skill tank-github-actions-mastery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams build reliable, secure GitHub Actions workflows without memorizing every syntax rule, security pitfall, or optimization trick.

Core Features & Use Cases

  • Workflow authoring: Define triggers, jobs, steps, expressions, contexts, outputs, and environment variables correctly.
  • CI/CD optimization: Apply caching, matrix strategies, concurrency controls, and monorepo path filtering to cut runtime and cost.
  • Security hardening: Lock down permissions, pin actions by SHA, use OIDC for cloud access, and protect deployment environments.
  • Reusable automation: Choose between reusable workflows, composite actions, JavaScript actions, and Docker actions for shared logic.
  • Use cases: Speed up test, lint, deploy, release, Docker build, and self-hosted runner workflows across single repos and monorepos.

Quick Start

Ask for a production-ready GitHub Actions workflow for your repository, including the right trigger, permissions, caching, and security safeguards.

Frequently Asked Questions about @tank/github-actions-mastery

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

FAQPage Schema
How do I build a secure GitHub Actions workflow for CI/CD?

Build secure GitHub Actions workflows by enforcing least-privilege permissions, pinning actions by SHA, and using OIDC federation for cloud access. This approach prevents unauthorized deployments while maintaining efficient CI/CD automation across Node, Python, and Docker environments.

What is the best way to optimize GitHub Actions workflows for a monorepo?

Optimize GitHub Actions monorepo workflows by applying path filtering for change detection, matrix strategies for parallel testing, and caching to reduce runtime. Concurrency controls prevent overlapping deployments, cutting both execution time and infrastructure costs.

How does OIDC federation work in GitHub Actions deployments?

OIDC federation in GitHub Actions eliminates static cloud credentials by issuing short-lived tokens authenticated through your cloud provider's trust policy. This secures deployment automation by ensuring workflows assume temporary roles instead of storing long-lived secrets.

Can I use reusable workflows and composite actions together in GitHub Actions?

You can combine reusable workflows and composite actions in GitHub Actions to share logic efficiently. Choose reusable workflows for entire pipeline templates, composite actions for grouped steps, or JavaScript and Docker actions for custom automation logic.

Why should I pin GitHub Actions dependencies by SHA instead of version tags?

Pin GitHub Actions dependencies by SHA to enforce security hardening and ensure reproducible builds. Version tags are mutable and vulnerable to supply chain attacks, while SHA pinning locks actions to specific commits, preventing unauthorized code modifications.

Does GitHub Actions support self-hosted runner patterns for production deployments?

GitHub Actions supports self-hosted runner patterns for production deployments by allowing customized environment protection rules and concurrency control. This enables reproducible workflow composition while maintaining strict security boundaries across your infrastructure.