github-actions-expert

Optimizes GitHub Actions workflows for CI/CD automation, security, and performance.

3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/trudyan141/my-antigravity-agents-kit --skill github-actions-expert-trudyan141
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions-expert
Source: https://github.com/trudyan141/my-antigravity-agents-kit/tree/main/templates/.agent/skills/github-actions-expert
Command: npx skills add https://github.com/trudyan141/my-antigravity-agents-kit --skill github-actions-expert-trudyan141

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? GitHub Actions workflows often suffer from YAML syntax errors, slow execution, insecure secret handling, and inefficient caching. This Skill diagnoses and fixes these issues while guiding the design of secure, performant CI/CD pipelines. ## Core Features & Use Cases - Workflow Diagnosis & Optimization: Detects YAML syntax errors, circular job dependencies, cache inefficiencies, and runner cost problems. - Security Hardening: Implements OIDC authentication, minimal permission scopes, SHA-pinned actions, and proper secrets management. - Advanced Patterns: Provides reusable workflows, dynamic matrix generation, path-filtered conditional execution, and multi-environment deployment strategies. - Use Case: A team's CI pipeline takes 40 minutes and exposes secrets in logs. Use this Skill to redesign caching, parallelize jobs with an optimized matrix, and migrate to OIDC-based cloud authentication. ## Quick Start Ask the assistant to review the workflows in .github/workflows and fix any security or performance issues.

Frequently Asked Questions about github-actions-expert

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

FAQPage Schema
How do I optimize slow GitHub Actions workflows?

Optimize slow workflows by implementing multi-level dependency caching with well-designed cache keys, parallelizing jobs with matrix strategies, and excluding unnecessary matrix combinations. Also review runner selection and set timeout values to prevent runaway jobs.

How do I secure secrets in GitHub Actions?

Secure secrets by using OIDC authentication instead of long-lived tokens, scoping secrets to environments, and defining minimal permissions at the workflow or job level. Never expose secrets in logs, outputs, or environment variables.

Should I pin GitHub Actions to a SHA or version tag?

Pin actions to a specific SHA commit rather than floating tags, since tags can be moved to point to malicious code. Include the version as a comment alongside the SHA for readability and upgrade tracking.

How do I create a reusable workflow in GitHub Actions?

Create a reusable workflow by defining a workflow with the workflow_call trigger, declaring typed inputs and outputs, then calling it from other workflows with the uses keyword. This standardizes CI logic across repositories.

Why does my GitHub Actions matrix build run unnecessary jobs?

Matrix builds run all combinations by default, including irrelevant ones. Use the exclude keyword to skip specific combinations, or generate the matrix dynamically with fromJson to reduce combinations for pull requests.

How do I run jobs only when certain files change?

Use a path-filtering action such as dorny/paths-filter in a setup job that outputs which directories changed. Then gate downstream jobs with conditional if expressions referencing those outputs.