How to install friday-brief
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill friday-briefFull instructions (SKILL.md)
Source of truth, from anthropics/knowledge-work-plugins.
name: friday-brief description: Delivers the Friday end-of-week pulse — revenue vs prior week, top sellers, wins and watches. Accepts optional lookback window of 7 or 14 days. allowed-tools: Read, WebFetch, Bash
Run the Friday wins-and-watches briefing. Pull the numbers, surface what matters, and give the owner a clean end-of-week picture.
Parse arguments:
--lookback(default:7d) —7dfor one week or14dfor a two-week rolling comparison
Step 1 — Revenue pulse
Using the business-pulse skill workflow:
- Pull PayPal transactions for the lookback period.
- Pull any HubSpot deal closes for the same window.
- Calculate week-over-week revenue delta.
- Surface top 3 revenue sources (product / customer / channel) ranked by contribution.
Step 2 — Sales breakdown
- List the top 5 selling products/services by volume and revenue.
- List the bottom 3 (anything that moved less than expected vs. prior period).
- Flag any items with a sudden spike or drop (>20% change).
Step 3 — Wins and watches summary
Format the output as:
Friday Brief — {date}
WINS
• {win 1}
• {win 2}
• {win 3}
WATCHES
• {watch 1} — {recommended action}
• {watch 2} — {recommended action}
Revenue this week: ${amount} ({+/-}X% vs last week)
Connector failures
Run with whatever is connected — this command degrades gracefully. If PayPal is missing, skip transaction data and note "PayPal not connected — revenue data from HubSpot deals only." If HubSpot is missing, skip deal closes and note it. If neither is connected, stop and tell the owner: "No revenue sources connected. Connect PayPal or HubSpot to run the Friday brief."
Approval gates
- Never send or post this brief automatically. Always display it for the owner to review first.
- Never auto-cancel or modify anything. Surface the data and recommendations only.
Output
End with the formatted brief and ask the owner: "Want me to post this to Slack, email it to yourself, or save it?"
Related skills
More from anthropics/knowledge-work-plugins and the wider catalog.
data-visualization
Pick the right chart and generate publication-quality Python visualizations with built-in design and accessibility best practices.
code-review
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
documentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
build-dashboard
Build an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
task-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
memory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.