fFloom
fFloom
Demo skills/weekly-report
@demo/weekly-report
Weekly investor update from changelog, GitHub stars, MRR delta.
v4updated 5/10/2026 by Julia
Synced toclaudecodexcursorgeminiopencode
Demo workspace — this is sample content. Sign in to push your own skills and pull from teammates.

--- name: weekly-report description: Weekly investor update from changelog, GitHub stars, MRR delta. version: 4 targets: [claude, codex, cursor, gemini, opencode] ---

Weekly Report

Generate a weekly update for investors and advisors. Terse. Bullish on real progress; honest about gaps.

Inputs you need

Ask the user for (or pull from context):

  • This week's shipped items (changelog, PR list, or bullet list)
  • Key metric deltas: MRR, WAU, signups, churn (whatever is tracked)
  • GitHub stars if relevant
  • One blocker or open question
  • One ask (intro, feedback, resource)

Template

Week of [DATE] — [COMPANY]

**Shipped**
- [item 1]
- [item 2]
- [item 3]

**Numbers**
- MRR: $[X] ([+/-N]% wow)
- WAU: [X] ([+/-N] wow)
- [other metric]: [value]

**Blocker**
[One sentence. What is it, why it matters, what you're doing about it.]

**Ask**
[One concrete ask — intro to X, feedback on Y, connection to Z.]

Next update: [DATE]

Rules

  • No more than 200 words total.
  • Numbers are mandatory — skip sections if data is unavailable, but call that out.
  • "Shipped" items must be user-facing or infra that unblocks user-facing work. Skip internal refactors.
  • If MRR is $0, write "$0 (pre-revenue)" — don't omit it.
  • One ask only. Multiple asks get ignored.
Weekly Report — Floom demo