Skills library · 80 skills · 53 apps
Claude skills that report back
Ready-made automations for Claude Code, Codex, Cursor and every agent that reads a SKILL.md. Pull a report from Jira, Search Console, Stripe or GitHub, run it on a schedule, and read the result on your board.
- 80skills
- 53apps
- 11teams
- 0accounts needed
80 skills, ready to run with your own agent
Search Console weekly keyword report
Every Monday: clicks, impressions and position for your top queries, what moved since last week, and the pages to work on first.
SEOMondays at 9:00Stat tileUses Google Search Console.GA4 weekly traffic report
Every Monday: last week's GA4 sessions, users and key events, each channel set against the week before, and the change worth a look.
MarketingMondays at 8:00Stat tileUses Google Analytics.Google Ads weekly audit
Every Monday: last week's Google Ads spend and CPA, wasted spend on search terms, disapproved ads and campaigns held back by budget, in one card.
MarketingMondays at 8:30Report cardUses Google Ads.Weekly SEO report: Search Console and GA4
Every Monday: Google clicks and position from Search Console, organic sessions and key events from GA4, and the pages that moved, in a single card.
SEOMondays at 10:00Report cardUses Google Search Console, Google Analytics.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.HubSpot weekly pipeline report
Every Monday: open pipeline by stage, the deals that changed stage last week, and what was created, won and lost.
SalesMondays at 8:00Stat tileUses HubSpot.Stripe weekly MRR report
Every Monday: MRR, net new MRR split into new, expansion, contraction and churn, and active subscriptions, computed from Stripe the same way each week.
FoundersMondays at 8:00Stat tileUses Stripe.Weekly founder metrics: MRR, traffic and active users
Every Monday: MRR from Stripe, sessions from Google Analytics and weekly active users from PostHog, each with its change since the week before.
FoundersMondays at 7:30Stat tileUses Stripe, Google Analytics, PostHog.Daily morning brief: calendar, inbox and issues
Weekdays at 7:30: today's meetings from Google Calendar, the emails that need a reply from Gmail, and your Linear issues due today or overdue.
FoundersWeekdays at 7:30Report cardUses Google Calendar, Gmail, Linear.Ahrefs new and lost backlinks
Every Friday, the referring domains Ahrefs found linking to you this week, the ones that stopped, and the links worth a follow-up email.
SEOFridays at 10:00Report cardUses Ahrefs.Semrush position tracking report
Each Tuesday: your Semrush Position Tracking visibility, how it compares with the competitors in the campaign, and the keywords that moved it.
SEOTuesdays at 7:30Stat tileUses Semrush.Notion content calendar status
Every Monday: the pieces due this week in your Notion content calendar, the ones past their date and not yet live, and what went out last week.
MarketingMondays at 8:30Report cardUses Notion.Jira weekly status report
Every Friday afternoon: what got done, what is in flight, what is blocked and what scope was added, written for people who never open Jira.
Product managersFridays at 15:00Report cardUses Jira.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 stale issues report
Every Monday: To Do and In Progress issues with no update for 14 days or more, oldest first, with their owners and a suggested next move for each.
Product managersMondays at 10:00Report cardUses 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 triage queue
Every weekday at 10: the issues sitting in Linear Triage, oldest first, each with a suggested team, priority and label, ready to accept or change.
Product managersWeekdays at 10:00Asks youUses Linear.Linear weekly changelog
Every Friday: the issues completed in Linear this week, filtered to what customers will notice and rewritten as a short changelog ready to edit.
Product managersFridays at 14:00Report 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.Salesforce weekly pipeline report
Monday mornings: open Salesforce pipeline by stage and forecast category, the deals that moved or slipped last week, and the change in total.
SalesMondays at 7:30Stat tileUses Salesforce.Zendesk ticket backlog
Twice each weekday: unsolved Zendesk tickets by priority and age, the ones already past their SLA target, and whether the queue grew.
Customer supportWeekdays at 8:00 and 14:00Stat tileUses Zendesk.Intercom conversation themes
Every Friday: the topics customers raised in Intercom this week, how many conversations each, and real quotes behind them.
Customer supportFridays at 14:00Report cardUses Intercom.Stripe daily revenue report
Each morning: yesterday's gross revenue, refunds and net from Stripe, how many customers paid you for the first time, and any dispute that came in.
FoundersEvery day at 7:00Stat tileUses Stripe.Stripe failed payments to chase
Every weekday: Stripe invoices whose payment failed, with amount, decline reason and next retry, and a question about which customers to email.
FinanceWeekdays at 10:00Asks youUses Stripe.Stripe monthly churn report
On the 1st: last month's customer churn and revenue churn from Stripe, split by the reason customers gave when they canceled.
Founders1st of the month at 9:00Stat tileUses Stripe.Stripe new and canceled subscriptions
Every weekday morning: which Stripe subscriptions started and which ended since the last run, grouped by plan, with the MRR each one adds or removes.
FoundersWeekdays at 8:00Report cardUses Stripe.Stripe trials ending this week
Mondays: every Stripe trial ending in the next 7 days, which ones have a card on file, and how many trials converted last month.
FoundersMondays at 9:30Stat tileUses Stripe.QuickBooks cash and runway
Mondays: cash across your QuickBooks bank accounts, average monthly net burn over the last three months, and how many months of runway that leaves.
FinanceMondays at 8:30Stat tileUses QuickBooks.QuickBooks overdue invoices to chase
Twice a week: your A/R aging from QuickBooks, the overdue invoices worth chasing first, and a question about which payment reminders to send.
FinanceMondays and Thursdays at 10:00Asks youUses QuickBooks.Google Sheets KPI tracker report
Fridays: each KPI in your tracking sheet against its target, which ones are behind, which moved since last week, and which rows nobody updated.
FoundersFridays at 15:00Stat tileUses Google Sheets.Shopify daily sales report
Each morning: yesterday's Shopify net sales, order count, average order value and best-selling product, against the day before.
FoundersEvery day at 7:15Stat tileUses Shopify.Asana overdue tasks by assignee
Every weekday: overdue tasks in an Asana project or portfolio, grouped by assignee, with the oldest ones and the tasks nobody owns.
Product managersWeekdays at 9:30Stat tileUses Asana.Morning marketing summary: GA4, Google Ads and Meta Ads
Weekday mornings: yesterday's sessions, key events, ad spend and ROAS across GA4, Google Ads and Meta Ads, against the same day last week.
MarketingWeekdays at 8:00Report cardUses Google Analytics, Google Ads, Meta Ads.Competitor website change monitor
Every Monday: the competitor pages that changed since last week, with each change in one line: new prices, new features, removed plans.
MarketingMondays at 8:00Report cardUses Firecrawl.Gong deal risks from this week's calls
Every Friday: open deals whose Gong calls this week raised pricing pushback, a competitor or no next step, each with the call to review.
SalesFridays at 14:00Asks youUses Gong.Supabase daily signups
Every morning: how many people signed up yesterday in your Supabase project, confirmed and by provider, against the 7-day average.
FoundersEvery day at 8:00Stat tileUses Supabase.Obsidian weekly review: open tasks and stale notes
Every Sunday evening: open tasks across your Obsidian vault by due date, inbox notes older than a week, and a short summary of what you wrote.
FoundersSundays at 18:00Report cardUses Obsidian.Postgres daily metrics from your own tables
Every morning: one number from a saved SQL query against your Postgres database, such as signups or orders, with the change since the day before.
FoundersEvery day at 8:00Stat tileUses PostgreSQL.Outlook emails waiting on your reply
Weekday afternoons: Outlook conversations where the last message is from someone else and over 24 hours old, with an offer to draft replies.
FoundersWeekdays at 15:00Asks youUses Outlook.Google Drive weekly changes digest
Every Friday: the docs created or edited this week in the Drive folders you choose, who changed them, and one line on the larger edits.
Product managersFridays at 16:00Report cardUses Google Drive.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.Airtable overdue records alert
Every weekday: the records in your Airtable view that are past their due date, grouped by owner, and a question on who takes the unassigned ones.
Product managersWeekdays at 9:00Asks youUses Airtable.ClickUp weekly status report
Every Friday: tasks completed, in progress and blocked in each ClickUp list, and what is due next week, ready for the weekly update.
Product managersFridays at 15:00Report cardUses ClickUp.Zoom meeting action items digest
Every weekday at 17:30: the action items and owners from today's recorded Zoom meetings, from AI Companion summaries or transcripts.
Product managersWeekdays at 17:30Report cardUses Zoom.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.AWS cost anomaly alert
Every morning: new AWS cost anomalies with the service, account, region and dollars above expected, and a question about who owns each one.
DevOpsEvery day at 9:00Asks youUses AWS.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.Azure daily cost report
Every morning: yesterday's Azure cost against the 7-day average, with the top services and resource groups and the one that moved.
DevOpsEvery day at 8:00Stat tileUses Azure.Snowflake credit usage this week
Every Monday: Snowflake credits used in the last 7 days against the week before, by warehouse, with the most expensive queries and who ran them.
Data teamsMondays at 8:00Stat tileUses Snowflake.Databricks failed jobs
Every morning: Databricks job runs that failed or timed out since yesterday, with the failing task, the error line and a link, and an ask about repairing.
Data teamsEvery day at 7:30Asks youUses Databricks.Figma comments waiting on you
Each weekday morning: open Figma comment threads that mention you or that you are part of, where the last word is not yours, oldest first.
DesignWeekdays at 9:00Asks youUses Figma.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.Striking distance keywords worth the most clicks: Search Console and DataForSEO
Once a month: your queries at positions 5 to 20, sized by real search volume, and the clicks each would add if it reached position 3.
SEO1st of the month at 9:00Report cardUses Google Search Console, DataForSEO.Ghost pipeline: CRM deals with no real contact
Fridays: open deals with no email, meeting or Gong call with the buyer in 14 days, and this week's external meetings the CRM never heard about.
SalesFridays at 14:00Asks youUses HubSpot, Pipedrive, Salesforce, Gmail, Google Calendar, Gong.Churn early warning: Stripe, usage, support and email
Mondays: paying accounts where a usage drop, a failed payment, an unhappy ticket or a cancel email line up, with the MRR at risk.
FoundersMondays at 8:30Asks youUses Stripe, PostHog, Mixpanel, Intercom, Zendesk, Gmail.Pages that earn sign-ups: Search Console, GA4 and your sign-ups
Every Monday: organic clicks, GA4 sessions and real sign-ups for each landing page, joined on the URL, with the pages to push and the pages to fix.
SEOMondays at 9:00Report cardUses Google Search Console, Google Analytics, Supabase, PostgreSQL, Stripe.AI answer visibility: DataForSEO, GA4 and Search Console
Weekly: of your top 20 non-branded Google queries, how many get an AI answer citing your domain in ChatGPT, Perplexity or AI Overviews, plus AI referral visits.
SEOMondays at 8:00Stat tileUses DataForSEO, Google Analytics, Google Search Console.By team
Skills for the work your team already does
Each team page collects the reports, digests and monitors that job runs every week, and the apps they come from.
- 10MarketingTraffic, campaigns, ad spend and email results, pulled by your agent from Google Analytics, Google Ads, HubSpot and Shopify, and posted where the team looks every morning.See 10 skills
- 7SEOSearch Console keywords, striking-distance pages, content decay, backlinks and rankings, checked on a schedule so you see what changed without opening five tools.See 7 skills
- 25Product managersSprint and cycle progress, stale and blocked issues, feature adoption, funnels and customer themes from Jira, Linear, PostHog, Notion and Intercom, summarized on a schedule.See 25 skills
- 31DevelopersPull requests waiting on you, failed CI runs and deploys, new errors, security alerts and your own issues across GitHub, Jira, Linear, Sentry and Vercel.See 31 skills
- 8SalesPipeline, forecast against quota, deals going quiet, new leads and response times from HubSpot and Salesforce, written up by your agent before the pipeline review.See 8 skills
- 29FoundersMRR, revenue, churn, cash, traffic and the inbox: the handful of numbers a founder checks every day, pulled from Stripe, QuickBooks, Shopify, Google Analytics and Gmail.See 29 skills
- 9FinanceCash position, overdue invoices, monthly P&L, spend by category, failed payments and budget against actual from QuickBooks, Stripe and Google Sheets.See 9 skills
- 4Customer supportTicket backlog and SLA, response times, CSAT and the themes behind them from Zendesk, Intercom, HubSpot and Slack, summarized for the team every day.See 4 skills
- 9DevOpsCloud costs, firing alerts, failed pipelines, incidents and uptime from AWS, Azure, Cloudflare, Datadog, Grafana and PagerDuty, checked on a schedule so the morning starts with what is red.See 9 skills
- 3Data teamsWarehouse spend, failed jobs, stale sources, slow queries and the dashboards stakeholders ask about, from Snowflake, BigQuery, Databricks, dbt, Metabase and Postgres.See 3 skills
- 1DesignFigma comments waiting on you and the files that changed this week, pulled from the Figma API by your agent and posted where you look first.See 1 skills
On a schedule
Scheduled task examples, by how often they run
Every skill comes with a schedule and the cron line for it. Run it once by hand, then let it run on its own.
By app
53 apps your agent can read for you
Every app page explains how an agent connects to it (an MCP server, a CLI or an API token) and lists the skills that use it.
- GitHub9
- Stripe9
- Google Analytics7
- Jira6
- Linear6
- Google Search Console5
- Sentry5
- Vercel4
- Gmail3
- PostHog3
- DataForSEO2
- Gong2
- Google Ads2
- Google Calendar2
- HubSpot2
- Intercom2
- PostgreSQL2
- QuickBooks2
- Salesforce2
- Slack2
- Supabase2
- Zendesk2
- Ahrefs1
- Airtable1
- Asana1
- AWS1
- Azure1
- Azure DevOps1
- ccusage1
- ClickUp1
- Cloudflare1
- Confluence1
- Databricks1
- Datadog1
- Figma1
- Firecrawl1
- GitHub Actions1
- GitLab1
- Google Drive1
- Google Sheets1
- Grafana1
- Meta Ads1
- Mixpanel1
- n8n1
- Notion1
- Obsidian1
- Outlook1
- Pipedrive1
- Railway1
- Semrush1
- Shopify1
- Snowflake1
- Zoom1
How it works
From a SKILL.md to a card you glance at
- 1
Install the skill
One command puts its SKILL.md where Claude Code, Codex, Cursor, Gemini CLI and other agents look for skills. Or paste the prompt into any agent.
- 2
Run it, then schedule it
Ask your agent to run it once and check the result. Then put it on a schedule with cron, a routine or GitHub Actions, so it runs while you do something else.
- 3
Read it on your board
Each run posts one card to Briefkin: a number with its trend, a short report, or a question for you. The same card updates in place, run after run.
Questions
About these skills
What is an agent skill?
A skill is a SKILL.md file: instructions an AI agent loads when a task calls for it. Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI and other agents read the same format. The skills here describe one job each, such as "summarize the Jira issues assigned to me" or "top Search Console queries this week", with the steps, the data to pull and the shape of the report.
Are the skills free?
Yes. Every skill is free to read, copy and install, and runs with your own agent and your own access to each app. Nothing is sent to Briefkin unless you connect a board.
Which agents do they work with?
Anything that can follow a SKILL.md or a prompt: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Windsurf and Amp, and scheduled runs of any of them. Each skill also has a plain prompt you can paste into a chat.
Why post the result to Briefkin?
A report you have to go and find is a report you stop reading. With a Briefkin token set, each run posts one card to your board: the number and its trend on a stat tile, the report on a card, or a question when something needs you. It updates in place every run, and Telegram pings you only for the questions.
How do I run a skill on a schedule?
Every skill page has a suggested schedule and the cron line for it, for example "30 8 * * 1-5 claude -p 'Run the jira-my-open-issues skill'". Claude Code routines, Codex in a GitHub Action or a plain cron job on a server all work.
Every report your agents run, on one board
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.