Agent skill
fin-weekly-report
Weekly financial report — consolidates Stripe and Omie data for the week: revenue, expenses, cash flow projection, overdue accounts, and variance analysis. Trigger when user says 'financial weekly', 'weekly financial report', or 'financial summary of the week'.
Install this agent skill to your Project
npx add-skill https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/fin-weekly-report
SKILL.md
Financial Weekly — Weekly Financial Report
Weekly routine that consolidates the week's financial data: revenue, expenses, Stripe, Omie, projected cash flow, and analysis.
Always respond in English.
Step 1 — Collect the week's revenue (silently)
1a. Stripe — revenue
Use /int-stripe to fetch:
- Succeeded charges for the week (Mon-Sun) → group by type/plan
- Compare with previous week
- Current MRR vs start of week
- New customers vs cancellations
- Payment failures
1b. Omie — revenue
Use /int-omie to fetch:
- Confirmed receipts for the week
- Invoices issued during the week
Group revenue by category:
- Stripe Subscriptions
- Services / Consulting
- Partnerships
- Other
Step 2 — Collect the week's expenses (silently)
2a. Omie — expenses
Use /int-omie to fetch:
- Payments made during the week
- Categorize: Personnel, Infrastructure, Services, Marketing, Taxes, Other
2b. Comparison
- Calculate variance vs previous week for each category
- Calculate % of total for each category
Step 3 — Detailed Stripe metrics
Consolidate the week's Stripe metrics:
- MRR and variance
- Total active subscriptions and variance
- Churn rate
- New customers
- Payment failures and at-risk amount
Step 4 — Detailed Omie metrics
Consolidate the week's Omie metrics:
- Overdue receivables (delinquency)
- Next week's payables
- Invoices pending issuance
- Invoices issued during the week
- Confirmed receipts
Step 5 — Cash flow projection (4 weeks)
Based on collected data, project:
- Expected inflows (Stripe recurring + receivables)
- Expected outflows (payables + recurring expenses)
- Balance and cumulative by week
Step 6 — Overdue accounts
List all overdue accounts (receivable and payable):
- Client/Vendor, type, amount, due date, days overdue
Step 7 — Analysis and recommendations
Write a brief analysis (3-5 bullets) covering:
- Revenue trend (growing/stable/declining)
- Out-of-pattern spending
- Delinquency status
- Cash flow (comfortable or tight)
Write recommended actions (bullets):
- Collections to make
- Invoices to issue
- Payments to expedite/postpone
- Any flags for the responsible person or finance team
Step 8 — Classify financial health
Health badge (CSS class):
- green "Healthy": revenue > expenses, no significant delinquency, positive cash flow
- yellow "Warning": tight margins, or delinquency > R$ 2,000, or projected negative cash flow
- red "Risk": expenses > revenue, or delinquency > R$ 10,000, or runway < 3 months
Step 9 — Generate HTML
Read the template at .claude/templates/html/custom/financial-weekly.html and replace ALL {{PLACEHOLDER}}.
For dynamic revenue/expense tables:
<tr>
<td>Category Name</td>
<td class="right">R$ X,XXX.XX</td>
<td class="right">XX%</td>
<td class="right var-positive/var-negative">+X% / -X%</td>
</tr>
For cash flow:
<tr>
<td>Week DD/MM - DD/MM</td>
<td class="right">R$ X,XXX</td>
<td class="right">R$ X,XXX</td>
<td class="right" style="color:var(--green/--red)">R$ X,XXX</td>
<td class="right">R$ XX,XXX</td>
</tr>
Values in Brazilian format: R$ 1.234,56
Step 10 — Save
Save to:
workspace/finance/reports/weekly/[C] YYYY-WXX-financial-weekly.html
Create the directory workspace/finance/reports/weekly/ if it does not exist.
Step 11 — Confirm
## Financial Weekly generated
**File:** workspace/finance/reports/weekly/[C] YYYY-WXX-financial-weekly.html
**Revenue:** R$ X,XXX ({var}%) | **Expenses:** R$ X,XXX ({var}%)
**MRR:** R$ X,XXX | **Projected 30d balance:** R$ XX,XXX
**Alerts:** {N} overdue accounts | {N} pending invoices
Notify via Telegram
Upon completion, send a short summary via Telegram to the user:
- Use the Telegram MCP:
reply(chat_id="YOUR_CHAT_ID", text="...") - Format: emoji + "Financial Weekly" + revenue vs expenses + MRR + alerts (2-3 lines)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
data-create-viz
Cria visualizações de dados de qualidade profissional com Python no tema Evolution (fundo escuro, acento
cs-customer-escalation
Empacota uma escalação para Devs, Produto ou Davidson com contexto completo. Use quando um bug precisa de atenção além do suporte normal, vários clientes reportam o mesmo problema, um cliente está ameaçando cancelar, ou um problema ficou sem resolução além do SLA. / Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.
mkt-draft-content
Draft blog posts, social media, email newsletters, landing pages, press releases, and case studies with channel-specific formatting and SEO recommendations. Use when writing any marketing content, when you need headline or subject line options, or when adapting a message for a specific platform, audience, and brand voice.
gog-tasks
Create, manage, and prioritize tasks and todo items. Convert emails to tasks, set priorities (P0-P3) and categories (Work/Personal/Errands/Admin), review daily priorities, track blocked and overdue tasks. Use when user mentions tasks, todos, action items, or wants to convert emails to tasks. Requires confirmation before creating or deleting tasks.
discord-get-messages
Retrieve messages from Discord channels via the Discord API. Use this skill when the user wants to read, search, or analyze messages from a Discord channel.
cs-customer-research
Pesquisa multi-fonte sobre pergunta ou tópico de cliente com atribuição de fontes. Use quando um cliente pergunta algo que precisa ser verificado, investigando se um bug foi reportado antes, verificando o que foi dito anteriormente a uma conta específica, ou coletando contexto antes de redigir uma resposta. / Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response.
Didn't find tool you were looking for?