Skill Market

friday brief

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.

GitHub
githubcommunity
0.0
0 installs24.9K GitHub starsby anthropics

Skill Introduction

Overview
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.

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community work faster.

Target users

  • Developers, testers, and maintainers who handle Development tasks in Focus Code.
  • Teams that already trust workflows or content from anthropics.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Development, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install friday-brief-84b8c8
View source

Detail Preview

SKILL.md

Primary filemarkdown2 KB

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?"

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet