Code · 9 skills
GitHub MCP and Claude skills
Pull open pull requests, review requests, stale issues, releases and Dependabot alerts from GitHub, and report what is waiting on whom.
Connect GitHub to your agent (MCP)
- GitHub MCP Server, GitHub's official server, hosted at
https://api.githubcopilot.com/mcp/. Sign in with OAuth or a personal access token; add/readonlyto the URL, or use a toolset URL such ashttps://api.githubcopilot.com/mcp/x/pull_requests/readonly, to expose only read tools. It also runs locally (source). - The
ghCLI. Rungh auth loginonce, or setGH_TOKENfor scheduled runs.gh pr list --search "review-requested:@me" --json number,title,url,createdAtandgh api repos/{owner}/{repo}/dependabot/alertscover most reports. - REST and GraphQL with a fine-grained token. Store it in
GITHUB_TOKEN, limit it to the repositories in the report, and grant Read on Metadata, Contents, Pull requests and Issues, plus Dependabot alerts if you report on them.
With every permission on a fine-grained token set to Read, the agent can't push, merge, comment or close anything.
9 GitHub skills
GitHub PRs waiting on your review
Twice a day: every open PR where your review is requested, the longest wait first, with size and CI state, and a nudge once one has waited over a day.
DevelopersWeekdays at 9:30 and 13:30Asks youUses GitHub.GitHub daily standup summary
Each weekday before standup: what merged, what opened and what got reviewed in the repo since yesterday morning, written person by person.
DevelopersWeekdays at 9:15Report cardUses GitHub.GitHub stale pull requests
Every Monday: open PRs with no commits, comments or reviews in 7 days, who each one waits on, and whether to nudge, merge or close it.
DevelopersMondays at 9:30Report cardUses GitHub.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.GitHub release notes draft
Every Thursday: PRs merged since the last release, grouped by label into breaking, new, fixed and internal, and rewritten so a customer can follow them.
DevelopersThursdays at 14:00Report cardUses GitHub.GitHub Dependabot alerts by severity
Every Monday: open Dependabot alerts across the org by severity, the critical and high ones with a fix available, and the repos that hold the most.
DevelopersMondays at 8:00Stat tileUses GitHub.GitHub, Vercel and Sentry release health check
An hour after each production deploy: errors after the release against the hour before, new Sentry issues, key page checks, and the PRs that shipped.
DevelopersEvery hourReport cardUses GitHub, Vercel, Sentry.Agent cost per merged PR: ccusage and GitHub
Every Monday: agent tokens at API list price divided by the PRs that merged, Claude Code against Codex, with the review rounds each PR needed.
DevelopersMondays at 9:00Stat tileUses ccusage, GitHub.Deploy to error to conversion chain
Each morning and after a deploy: every production release lined up with the Sentry issues it introduced and the key event rate before and after it.
DevelopersDaily at 8:00, and after each deployReport cardUses GitHub, Sentry, PostHog, Google Analytics, Vercel.What agents do with GitHub
Agents reach GitHub through the gh CLI, the REST API and the GraphQL API. Pull requests carry isDraft, reviewDecision, reviewRequests, mergeable, createdAt and updatedAt; issues carry labels, assignees, milestones and comment counts. Search qualifiers do most of the filtering: is:pr is:open review-requested:@me, is:pr is:open draft:false with an updated:< date a week back, is:issue is:open label:bug no:assignee. Security data comes from Dependabot alerts (GET /repos/{owner}/{repo}/dependabot/alerts) and code scanning alerts, and merged PRs and releases feed changelogs.
Developers put these on a schedule: PRs waiting on your review each morning, PRs open more than a week, a weekly list of merged PRs as a changelog, new Dependabot alerts by severity, and issues that never got a reply.
Often used with GitHub
Teams that use these
Your GitHub 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.
Free during the open beta. No card.