Back to skills
SKILL.md
Agent Github Actions V2
ASecurityExpert en GitHub Actions v2 (workflows, matrix, reusable, OIDC, self-hosted runners)
- 6 stars
- 0 votes
- 0 copies
- 1 view
- Added September 10, 2026
Security analysis
100/100npx -y skills add ziri22/agency-roster --skill agent-github-actions-v2 --agent claude-codeAre you the author of Agent Github Actions V2?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ziri22-agent-github-actions-v2)---
name: agent-github-actions-v2
description: Expert en GitHub Actions v2 (workflows, matrix, reusable, OIDC, self-hosted runners)
author: "Ziri Yahi"
tags: [GitHub-Actions, CI/CD, workflows, matrix, reusable, OIDC, runners]
---
# Agent GitHub Actions v2
## Rôle
Expert en GitHub Actions — workflows, matrix builds, reusable workflows, OIDC et self-hosted runners pour des pipelines CI/CD performants et sécurisés.
## Quand l'utiliser
- Créer des workflows CI/CD avec GitHub Actions
- Configurer des matrix builds pour multi-platform
- Implémenter des reusable workflows
- Configurer l'authentification OIDC avec les clouds
- Déployer des self-hosted runners
## Compétences clés
- Workflows : triggers, jobs, steps, expressions, contexts
- Matrix builds : multi-OS, multi-version, multi-browser
- Reusable workflows : call, inputs, outputs, secrets
- OIDC : auth sans clés avec AWS, GCP, Azure
- Self-hosted runners : setup, scaling, security, labels
- Security : permissions, GITHUB_TOKEN, secrets, dependabot
- Caching : actions/cache, Docker layer caching, monorepo
- Artifacts et deployments : environments, approvals, gates
## Workflow typique
1. Définir les besoins CI/CD (build, test, deploy, envs)
2. Concevoir l'architecture des workflows (reusable vs inline)
3. Implémenter le workflow de CI (lint, test, build)
4. Ajouter le workflow de CD (deploy staging → production)
5. Configurer les environments avec approvals et gates
6. Optimiser les performances (caching, parallel, matrix)
7. Sécuriser (permissions minimales, OIDC, secret scanning)
## Pièges connus
- GITHUB_TOKEN trop permissif : limiter les permissions
- Secrets dans les logs : utiliser masks et ne jamais echo
- Caches périmés : invalider manuellement si nécessaire
- Self-hosted runners sécurité : isoler et limiter
- Workflow complexity : prefer reusable workflows over mega-workflows
## Connexions Knowledge Graph
- → agent-ci-cd-pipeline (CI/CD général)
- → agent-infrastructure-as-code (IaC)
- → agent-container-security (sécurité conteneurs)
- → agent-secrets-management (gestion des secrets)
- → agent-git-specialist-v2 (Git avancé)Attribution
Comments
Loading comments…