Weekly recap

Skill inflowave/skills/skills/weekly-recap

Run a narrated weekly business review of an Inflowave account — growth, engagement, pipeline, revenue, and the top-performing (and stalling) workflows — ending in three prioritized moves. Use when the user says "weekly recap", "how did we do this week", "give me my numbers", or asks for a business summary.From its SKILL.md

Install

npx -y skills add inflowave/skills --skill weekly-recap

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 602 tokens by cl100k_base, as published. Nobody here has run it

Weekly Recap

Produce a concise, plain-English weekly review for a business owner. Never dump raw tool output — synthesize it into a story with a cause for every number and a short ranked action list at the end.

Steps

Establish scope. Call check_connection to confirm the account, plan, and what's available. If the user manages multiple workspaces, call list_sub_accounts and ask which one (or "all") — default to the whole agency only if they say so.
Pull the headline numbers (all reads, safe to run in parallel):
- weekly_recap — the platform's own rollup if available; use it as the spine.
- get_dashboard_summary — top-line KPIs.
- get_engagement_analytics and get_follower_analytics — audience + reach movement.
- get_pipeline_analytics — opportunities created / won / lost / value.
- get_finances_summary — revenue and spend.
- get_team_performance — if they have a team, who moved the needle.
Find the movers, not just the totals. For every metric that changed meaningfully, name the why: a spike in leads → check the source (form, campaign, DM); a jump in won revenue → which pipeline / workflow; a drop in replies → which account or workflow stalled. Pull one supporting read to confirm the cause before asserting it.
Surface the top and bottom workflows. get_workflow_performance (or list_workflows + get_workflow_details) to name the 1–2 workflows driving the most outcomes and any that quietly stopped firing.

Output

A short brief, in this shape:

This week in one line — the single most important thing that happened.
Growth — audience/reach, with the driver.
Pipeline & revenue — created vs won, value, and the source of the wins.
Automations — the best performer and anything that stalled.
Do this next — exactly 3 ranked actions, each one sentence, each tied to a number above (e.g. "Re-activate the 'New Lead DM' workflow — it drove 40% of replies last week and has been off for 3 days").

Guardrails

Read-only. Never create or change anything in this skill — if an action is warranted, name it in "Do this next" and let the user ask.
Plain language. No tool names, no p95s, no internal IDs in the output.
If a number looks off (zero, or a huge swing), say so honestly rather than inventing a cause.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.