Developers · 31 skills
Claude skills for developers
Pull requests waiting on you, failed CI runs and deploys, new errors, security alerts and your own issues across GitHub, Jira, Linear, Sentry and Vercel.
31 skills for developers
Jira: my open issues, summarized
Each weekday morning: your unresolved Jira issues grouped by priority, with anything overdue or due this week pulled to the top.
DevelopersWeekdays at 8:30Report cardUses Jira.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.Linear cycle progress
Every weekday: how much of the active Linear cycle is complete, how much scope was added since it started, and how many days are left.
Product managersWeekdays at 8:45Stat tileUses Linear.Vercel usage and spend this billing cycle
Every weekday: what this Vercel billing cycle has cost so far, how much included credit is left, the projected total, and which resource is driving it.
DevelopersWeekdays at 9:30Stat tileUses Vercel.Jira sprint progress
Each weekday morning: the share of committed story points done in the open sprint, the days left, and whether the pace so far gets you to the end.
Product managersWeekdays at 9:00Stat tileUses Jira.Jira blocked issues alert
Twice a day: every flagged or blocked issue in the active sprint, what it waits on and since when, with an ask about who clears it today.
Product managersWeekdays at 9:00 and 14:00Asks youUses Jira.Jira bug backlog trend
Every Friday: open bugs right now, bugs created and resolved this week, and the eight-week trend, so a bad week is not mistaken for a bad quarter.
DevelopersFridays at 16:00Stat tileUses Jira.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.Linear my issues today
Each weekday morning: the Linear issues assigned to you, Urgent and due today first, split into the current cycle and everything else.
DevelopersWeekdays at 8:15Report cardUses Linear.Linear urgent bugs tracker
Twice a day: open Urgent and High priority bugs in Linear, how long each has been open and who owns it, with the ones past your target first.
DevelopersWeekdays at 9:00 and 16:00Stat tileUses Linear.Sentry new errors digest
Every morning: unresolved Sentry issues first seen in the last 24 hours, ranked by users and events, with the release and code they started in.
DevelopersEvery day at 8:00Report cardUses Sentry.Sentry crash-free sessions for the latest release
Every 4 hours: the crash-free session rate of your newest release next to the previous one, with adoption, so an early number is read with care.
DevelopersEvery 4 hoursStat tileUses Sentry.Sentry top issues by users affected
Every Monday: the 10 unresolved Sentry issues that affected the most users in the last 7 days, with owner and whether each is rising or falling.
DevelopersMondays at 8:30Report cardUses Sentry.Vercel failed deployments alert
Three times a day: Vercel production and preview deployments that failed in the last 24 hours, the step and error line, and an ask on whether to redeploy.
DevelopersWeekdays at 9:00, 13:00 and 17:00Asks youUses Vercel.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.Slack channel digest
Every weekday morning: what happened in a busy Slack channel since this time yesterday, threads included, boiled down to decisions, open questions and links.
Product managersWeekdays at 8:30Report cardUses Slack.Slack incident summary
Every 30 minutes during an incident: the incident channel boiled down to status, customer impact, a timeline and the follow-ups for the postmortem.
DevelopersEvery 30 minutesReport cardUses Slack.Confluence pages changed this week
Every Friday: pages created or edited this week in the Confluence spaces you follow, grouped by space, with one line on what changed in each.
Product managersFridays at 15:00Report cardUses Confluence.GitLab merge requests waiting on your review
Each weekday morning: open GitLab merge requests where you are a reviewer and have not reviewed yet, oldest first, with pipeline status and conflicts.
DevelopersWeekdays at 9:00Asks youUses GitLab.Cloudflare Workers errors and usage
Every morning: requests, error rate and CPU time per Cloudflare Worker for the last 24 hours, against the same day last week, with the top exceptions.
DevelopersEvery day at 8:00Report cardUses Cloudflare.Azure DevOps pull requests waiting on your review
Each weekday morning: active Azure DevOps pull requests where you are a reviewer and have not voted yet, oldest first, with build and merge status.
DevelopersWeekdays at 9:00Asks youUses Azure DevOps.Railway deploys and usage
Every morning: Railway deployments that failed or crashed since yesterday, with the error lines, plus usage so far and the estimated bill for the cycle.
DevelopersEvery day at 8:00Report cardUses Railway.Datadog monitors in alert
Every hour of the working day: Datadog monitors in Alert or Warn, how long each has been there, and what is new or recovered since the hour before.
DevOpsHourly, 8:00 to 18:00 on weekdaysReport cardUses Datadog.n8n failed executions report
Every morning: n8n workflows with failed executions since yesterday, how many times each failed, the error message and the node it stopped on.
DevOpsEvery day at 8:00Report cardUses n8n.Grafana firing alerts digest
Every morning: Grafana alert rules that are firing or pending, grouped by folder, with how long each has fired and which are silenced.
DevOpsEvery day at 8:30Report cardUses Grafana.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 an agent can take off developers’s plate
Developers already run agents in the terminal all day. These skills point the same agent at the things that interrupt you: the review queue, the red build on main, the error that started after yesterday's deploy, the Dependabot alert nobody owns.
Scheduled, they replace the morning tour of GitHub, Sentry and your issue tracker with one card per question on your board, and a ping only when something is actually waiting on you.
Other teams
One board for every report developers runs
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.