agentleFS
donnybacondigital-debugdonnybacondigital-debug/claude-code-business-kit/.claude/skills/weekly-report/SKILL.md

weekly-report

Skill0 starsChanged 2 months agoMITView on GitHub

Turn a weekly spreadsheet export (hours, sales, tickets or any CSV/XLSX with dates, people and numbers) into a one-page weekly report with totals, week-over-week changes, anomalies and three actionable insights. Use when the user asks for a weekly report, weekly summary, "how did the week go", or shares a timesheet or sales export and wants it summarized.

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agency-clients, cross-post-video and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • posteverywhereSkill

    agency-clients

    Work safely across several clients or brands in PostEverywhere. Use when the user manages social media for more than one client, brand or business, mentions a client by name, asks to switch clients, or when the connected accounts belong to different companies.

    Also in 3 projects that use this

  • posteverywhereSkill

    cross-post-video

    Post one video to several platforms with PostEverywhere, with the right title and caption for each. Use when the user wants to share a video, Reel, Short or TikTok across TikTok, Instagram Reels, YouTube Shorts, LinkedIn and Facebook Reels, or asks to "post this video everywhere".

    Also in 3 projects that use this

  • CodeWithSulemanSkill

    approval-workflow

    Manage human-in-the-loop approval workflows for sensitive actions like payments, emails to new contacts, social media posts, and other actions requiring human oversight.

    Also in 3 projects that use this

  • flintfromthebasementSkill

    write-blog-post

    Write or edit a long-form blog post in a specific author's voice, then run it through six editorial passes (substance, structure, human voice, de-AI scrub, house style + O'Reilly word list, fresh-context critic) before delivering. Handles drafting from a brief, filling an outline, editing a draft, refreshing an old post, and applying revision notes. Use when the user wants a blog post that sounds like a real person wrote it, not a one-shot generation.

    Also in 3 projects that use this

  • +8 more from posteverywhere

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the columns are ambiguous, state your interpretation in one line under Assumptions.

    line 15
  2. Distinctive:

    Compute with code, not by eye: Use a script to calculate totals by person, by client or project, and by day.

    line 20
  3. Distinctive:

    Every number in the report comes from the computation, not from estimation.

    line 59
  4. Distinctive:

    No insight is generic. If you could say it about any company, rewrite it using the data.

    line 61

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Weekly report

Produce a one-page report a manager can read in two minutes and act on.

Inputs

  • A CSV or XLSX file. Typical columns: date, person or team, client or project, a numeric measure (hours, amount, units), optional status or category.
  • Optional: the previous week's file, targets or budgets.

If the columns are ambiguous, state your interpretation in one line under Assumptions. Do not stop to ask unless no numeric column exists.

Steps

  1. Load and check the data. Report the row count, date range and any rows you excluded (empty values, duplicates, dates outside the week). Never silently drop rows.
  2. Compute with code, not by eye. Use a script to calculate totals by person, by client or project, and by day. If a previous week is provided, compute changes in absolute and percentage terms.
  3. Find anomalies. Flag:
    • any person or project more than 25% above or below its usual share or target
    • days with no records
    • single entries larger than 3x the median entry
    • billable versus non-billable imbalance, if that column exists
  4. Write three insights. Each one states what happened, why it matters (money, time or risk), and one concrete next step with an owner if known.
  5. Write the report using the template below. Keep it to one page.

Template

# Weekly report · [week dates]

## Summary
[Two sentences: the headline number and the most important change.]

## Totals
| Measure | This week | Previous | Change |
|---|---|---|---|

## By [person / project]
| Name | [Measure] | Share | Note |
|---|---|---|---|

## Anomalies
- [anomaly and the rows that show it]

## Insights and next steps
1. **[Insight]** [why it matters] → **Next:** [action]
2. ...
3. ...

## Assumptions
- [interpretations, excluded rows, missing data]

Quality checks before answering

  • Every number in the report comes from the computation, not from estimation.
  • Shares add up to 100% (±1 rounding).
  • No insight is generic. If you could say it about any company, rewrite it using the data.
  • Excluded or ambiguous rows are listed under Assumptions.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.