Friday Brief

VerifiedCaution

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.

Sby Skills Guide Bot
ProductivityIntermediate
7/24/2026
Claude Code
#friday-brief#weekly-report#revenue#wins-watches

Recommended for

Automated summary

Generates an end-of-week business pulse report including revenue vs prior week, top sellers, wins, and watches, using optional PayPal and HubSpot integrations.

Strengths

  • Automates the collection of revenue and sales data from multiple sources
  • Provides clear week-over-week comparisons and flags significant changes
  • Includes actionable watch items with recommended next steps

Limitations

  • Requires at least one of PayPal or HubSpot to be connected to produce meaningful output
  • Does not auto-send reports; owner must manually approve distribution
  • Lookback window limited to 7 or 14 days only
When to use it

Use this skill every Friday to get a data-driven summary of the week's performance and identify key wins and risks.

When not to use it

Do not use this skill if you need real-time data or if neither PayPal nor HubSpot is available.

Security analysis

Caution
Quality score92/100

The skill uses Bash and accesses business accounts (PayPal, HubSpot) to pull financial data. It does not perform any destructive or exfiltrating actions, and includes strong approval gates to prevent automatic posting. However, due to the use of Bash and handling of sensitive revenue data, it warrants a caution rating.

Findings
  • •Uses Bash for process execution, which presents a risk if misused, but the skill only performs data retrieval and formatting.
How this analysis is made

Examples

Default 7-day Friday brief
Run the Friday wins-and-watches briefing.
Two-week lookback comparison
Run the Friday brief with --lookback 14d.

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) — 7d for one week or 14d for a two-week rolling comparison

Step 1 — Revenue pulse

Using the business-pulse skill workflow:

  1. Pull PayPal transactions for the lookback period.
  2. Pull any HubSpot deal closes for the same window.
  3. Calculate week-over-week revenue delta.
  4. Surface top 3 revenue sources (product / customer / channel) ranked by contribution.

Step 2 — Sales breakdown

  1. List the top 5 selling products/services by volume and revenue.
  2. List the bottom 3 (anything that moved less than expected vs. prior period).
  3. 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?"

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/friday-brief-mryiqgwp/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/friday-brief-mryiqgwp' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/friday-brief-mryiqgwp/download' --output '.skill-downloads/friday-brief-mryiqgwp/SKILL.md.part' && mv '.skill-downloads/friday-brief-mryiqgwp/SKILL.md.part' '.skill-downloads/friday-brief-mryiqgwp/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, WebFetch, Bash

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/friday-brief-mryiqgwp/SKILL.md' && test -s '.skill-downloads/friday-brief-mryiqgwp/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/friday-brief' && cp -R '.skill-downloads/friday-brief-mryiqgwp' '.claude/skills/friday-brief'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/friday-brief-mryiqgwp'

openskills read 'friday-brief-mryiqgwp'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/friday-brief-mryiqgwp/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills