briefkin

CI/CD · 1 skill

GitHub Actions MCP and Claude skills

Read workflow runs, failed jobs and their logs from GitHub Actions, and report red builds, flaky jobs and slow pipelines before anyone asks.

Connect GitHub Actions to your agent (MCP)

  1. GitHub MCP Server with the actions toolset, hosted at https://api.githubcopilot.com/mcp/x/actions; append /readonly for read tools only. It lists runs and jobs and fetches job logs.
  2. The gh CLI. gh run list --branch main --status failure --json databaseId,workflowName,conclusion,createdAt finds red runs, and gh run view <run-id> --log-failed prints only the failing steps' output. Set GH_TOKEN for unattended runs.
  3. REST API with a fine-grained token in GITHUB_TOKEN, scoped to the repositories you watch, with Actions: Read and Metadata: Read.

Actions: Read lets the agent list runs and download logs but not rerun, cancel or trigger workflows; grant write only if you want it to retry flaky jobs.

1 GitHub Actions skill

GitHub Actions failed runs on main

Each weekday morning: workflow runs that failed on the default branch in the last 24 hours, the job and step that broke, the error and the commit behind it.

DevelopersWeekdays at 8:00Report cardUses GitHub Actions, GitHub.

What agents do with GitHub Actions

Workflow runs are the core object. Each has status, conclusion (success, failure, cancelled, timed_out), head_branch, head_sha, event, run_attempt, run_started_at and updated_at. Jobs and steps hang off each run with their own conclusions and timings, and the failed step's log is where an agent finds the actual error. The REST endpoints are GET /repos/{owner}/{repo}/actions/runs (filter by branch, status, created) and GET /repos/{owner}/{repo}/actions/runs/{run_id}/jobs.

Typical checks: the default branch every hour or each morning, a weekly flaky-job report (jobs that failed and then passed on a rerun of the same commit, so run_attempt above 1), the slowest workflows by median duration, and failed scheduled workflows that nobody watches.

github.com/features/actions

Often used with GitHub Actions

Teams that use these

Your GitHub Actions numbers, on one board with everything else

Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.

Join the open betaBrowse all skills

Free during the open beta. No card.