github-actions-management
Manage GitHub Actions workflows, runs, and CI/CD via MCP. Use when asked to check CI status, read logs, or re-run jobs.
Works with
--- name: github-actions-management description: Manage GitHub Actions workflows, runs, and CI/CD via MCP. Use when asked to check CI status, read logs, or re-run jobs. license: MIT --- # GitHub Actions Management via MCP Use this skill when you need to check CI/CD status, read workflow logs, re-run failed jobs, or trigger deployments. ## Available Tools | Tool | What it does | |------|-------------| | `list_workflows` | List all workflow files in a repository | | `list_runs` | List workflow runs (filter by workflow or status) | | `get_run` | Get details of a specific workflow run | | `get_run_logs` | Get the logs URL for a run (zip download) | | `rerun_workflow` | Re-run an entire workflow run | | `rerun_failed_jobs` | Re-run only the failed jobs from a run | | `cancel_run` | Cancel an in-progress or queued run | | `list_artifacts` | List artifacts produced by a workflow run | | `trigger_workflow` | Trigger a workflow via `workflow_dispatch` | ## Workflow 1. Use `list_runs` with `owner` and `repo` to see recent runs and their status 2. For failed runs: `get_run` for details, then decide whether to `rerun_failed_jobs` or investigate logs 3. `trigger_workflow` requires the workflow file name and a branch — the workflow must have a `workflow_dispatch` trigger ## Key Patterns - All tools require `owner` and `repo` parameters (e.g., `owner: "ofershap"`, `repo: "my-project"`) - `list_runs` supports `status` filter: "completed", "in_progress", "queued", "failure", "success" - `rerun_failed_jobs` is preferred over `rerun_workflow` — it's faster and cheaper - `trigger_workflow` needs `workflow_id` (filename like "ci.yml") and `ref` (branch name) ## Safety - Prefer `rerun_failed_jobs` over full `rerun_workflow` to avoid unnecessary compute - Confirm before `cancel_run` — the user may want the run to finish - `trigger_workflow` can trigger deployments — always confirm the target branch
More Deployment & CI/CD skills
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).
prisma-compute
prisma/skills
Prisma Compute deployment and hosting guide. Use whenever the user mentions Prisma Compute, `prisma.compute.ts`, `defineComputeConfig`, deploying or hosting a Prisma app, `@prisma/cli app deploy`, `compute:deploy`, `create-prisma --deploy`, `PRISMA_SERVICE_TOKEN`, Compute auth/workspaces, apps/deployments/build logs/domains, localhost vs `0.0.0.0`, deploy port binding, or framework deploy readiness for Hono, Elysia, Next.js, TanStack Start, Astro, Nuxt, Svelte, Nest, Turborepo, or custom/prebuilt artifacts.
azure-quotas
microsoft/azure-skills
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: \"check quotas\", \"service limits\", \"current usage\", \"request quota increase\", \"quota exceeded\", \"validate capacity\", \"regional availability\", \"provisioning limits\", \"vCPU limit\", \"how many vCPUs available in my subscription\".
