agentleFS
itinovo-crmitinovo-crm/claude-plugin/skills/review-the-numbers/SKILL.md

review-the-numbers

Skill1 starsChanged 22 days agoMITView on GitHub

Review an itinovo agency's figures for a month, a quarter or a year — sold, margin, collected, leads and conversion, destinations and operators, compared with the period before — with what clients still owe, what is due to suppliers and what is left to invoice. For the agency's administrators. Use when the user asks how the month or the quarter went, for the agency's numbers, or for a summary for the owner or the partners.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Never request a payment or send a reminder from here: they leave from the itinovo app.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Reviewing the agency's numbers

Steps

  1. Settle the period: the one the user asks for; by default the last full month. «This month» runs to today.
  2. Read the report with get_analytics (view: report, period: month, quarter, year or custom with from and to; anchor: a day of a past month, quarter or year). It holds sold, margin, collected, conversion, destinations and operators against the period before, and as of today what clients owe by how late it is, what is due to suppliers and what is left to invoice.
  3. For the detail of what is owed, get_money (view: invoices, status: overdue; view: payment_requests, status: sent, then partially_paid).
  4. Write the review in a few lines:
    • what grew and what fell against the period before, with the figures;
    • where it comes from, as the data shows it: destinations, operators, conversion;
    • what is still to collect, the largest amounts first with how late they are, and what is due to suppliers;
    • two or three next steps: quotes to follow up (the follow-up-open-quotes skill), payments to chase and bookings to invoice from the app.
  5. On request, a table for the partners, or the narrative summary with get_analytics (view: executive_summary, month, quarter or year).

Rules

  • The figures are itinovo's: never recompute margins or VAT of your own, and always say the period and the currency.
  • Name the app's pages as the report says them, in the user's language.
  • Analytics are for administrators: if itinovo refuses, say that an administrator can see them.
  • Never request a payment or send a reminder from here: they leave from the itinovo app.

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.