Agent skill

fin-daily-pulse

Daily financial pulse — queries Stripe (MRR, charges, churn, failures) and Omie (accounts payable/receivable, invoices) to generate an HTML snapshot of the company's financial health. Trigger when user says 'financial pulse', 'financial snapshot', or 'financial metrics'.

Stars 211
Forks 54

Install this agent skill to your Project

npx add-skill https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/fin-daily-pulse

SKILL.md

Financial Pulse — Daily Financial Snapshot

Daily routine that pulls data from Stripe and Omie to generate an HTML snapshot of financial health.

Always respond in English.

Step 1 — Collect Stripe data (silently)

Use the /int-stripe skill to fetch:

1a. MRR and Subscriptions

  • List active subscriptions (status=active) → count and sum values to calculate MRR
  • Compare with previous data if available in workspace/finance/

1b. Today's Charges

  • List charges created today (created >= start of day UTC-3)
  • Sum total charged amount
  • Count charges with status=succeeded vs status=failed

1c. Churn (last 30 days)

  • List subscriptions canceled in the last 30 days
  • Calculate churn rate vs total subscriptions

1d. Refunds (last 7 days)

  • List refunds from the last 7 days
  • Sum total refunded amount

1e. New customers (last 7 days)

  • List customers created in the last 7 days

Step 2 — Collect Omie data (silently)

Use the /int-omie skill to fetch:

2a. Overdue receivables

  • Fetch receivables with due date before today and status "open"

2b. Payables (next 7 days)

  • Fetch payables with due date in the next 7 days

2c. Invoices

  • Fetch invoices pending issuance
  • Count invoices issued in the current month

Step 3 — Day's transactions

Consolidate all financial transactions for the day:

  • Stripe charges (revenue)
  • Payments recorded in Omie (expenses)
  • Refunds

Format each transaction with: type (Revenue/Expense/Refund), description, amount, status.

Step 4 — Classify financial health

Define the health badge (CSS class):

  • green "Healthy": MRR stable or growing, no significant delinquency, churn < 5%
  • yellow "Warning": churn between 5-10%, or overdue accounts > R$ 1,000, or payment failures > 3
  • red "Risk": churn > 10%, or overdue accounts > R$ 5,000, or MRR declining

Step 5 — Alerts

Generate list of financial alerts:

  • Payment failures that need retry or follow-up
  • Accounts overdue for more than 7 days
  • Invoices that should have been issued
  • Churn above normal levels
  • Any anomalies in amounts

If there are no alerts: "No financial alerts at this time."

Step 6 — Generate HTML

Read the template at .claude/templates/html/custom/financial-pulse.html and replace ALL {{PLACEHOLDER}} with the collected data.

For transactions (dynamic table):

html
<tr>
  <td><span class="badge green/red/yellow">Revenue/Expense/Refund</span></td>
  <td>Description</td>
  <td class="right">R$ X,XXX.XX</td>
  <td><span class="badge green/yellow">Confirmed/Pending</span></td>
</tr>

Values in Brazilian format: R$ 1.234,56

Step 7 — Save

Save the filled HTML to:

workspace/finance/reports/daily/[C] YYYY-MM-DD-financial-pulse.html

Create the directory workspace/finance/reports/daily/ if it does not exist.

Step 8 — Confirm

## Financial Pulse generated

**File:** workspace/finance/reports/daily/[C] YYYY-MM-DD-financial-pulse.html
**MRR:** R$ X,XXX | **Subscriptions:** N | **Churn:** X%
**Alerts:** {N} attention points

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 Pulse" + MRR + alerts (1-3 lines)

Expand your agent's capabilities with these related and highly-rated skills.

EvolutionAPI/evo-nexus

data-create-viz

Cria visualizações de dados de qualidade profissional com Python no tema Evolution (fundo escuro, acento

211 54
Explore
EvolutionAPI/evo-nexus

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.

211 54
Explore
EvolutionAPI/evo-nexus

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.

211 54
Explore
EvolutionAPI/evo-nexus

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.

211 54
Explore
EvolutionAPI/evo-nexus

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.

211 54
Explore
EvolutionAPI/evo-nexus

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.

211 54
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results