finance-insights
Skill1 starsChanged 51 days agoMITView on GitHub
Report, rank, compare, and trend finance performance across Stripe, QuickBooks, PayPal, Xero, Chargebee, and Braintree through Windsor.ai. Use when the user asks about revenue, charges, refunds, payouts, fees, subscriptions and MRR, invoices, and balances. Do not use to change anything, to connect an account, or to schedule exports - route those to the sibling skills.
In this repository33 other files it gives its agents.
- business-dataSkill
- crm-insightsSkill
- crm-manageSkill
- ecommerce-insightsSkill
- ecommerce-manageSkill
- facebook-adsSkill
- facebook-organicSkill
- gohighlevelSkill
- google-adsSkill
- google-analytics-4Skill
- google-business-profileSkill
- google-merchant-centerSkill
- google-search-consoleSkill
- hubspotSkill
- instagram-publicSkill
- instagramSkill
- klaviyoSkill
- linkedin-adsSkill
- linkedin-pagesSkill
- microsoft-adsSkill
- social-media-createSkill
- social-media-insightsSkill
- tiktok-adsSkill
- tiktok-organicSkill
- web-analytics-insightsSkill
- windsor-connectSkill
- windsor-createSkill
- windsor-exportSkill
- windsor-get-startedSkill
- windsor-insightsSkill
- windsor-manageSkill
- windsor-optimizeSkill
- youtubeSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
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
- Distinctive: line 8
Read live finance data from Stripe, QuickBooks, PayPal, Xero, Chargebee, and Braintree through Windsor.ai and turn it into a clear report, …
- Distinctive: line 12
Use this skill for metrics, rankings, comparisons, trends, and breakdowns of revenue, charges, refunds, payouts, fees, subscriptions and …
- Distinctive: line 13
If the user asks to connect, reconnect, or add an account, use /windsor-connect instead.
- Distinctive: line 14
If the user asks for a recurring, scheduled, or automated export, use /windsor-export instead.
- Distinctive: line 17
Call get_connectors first to see which of the six sources have connected accounts.
- Distinctive: line 18
Read field ids from get_fields for the chosen connector, and get_options for date-filter columns and connector options.
- Distinctive: line 19
Use the date range the user gave.
- Distinctive: line 26
Keep field sets small and request only the accounts you need.
- Distinctive: line 32
If a field the user wants is not in get_fields, say so rather than substituting a different metric.
- Distinctive: line 33
If "best", "top", or "worst" lacks a metric, ask which metric should define the ranking.
- Distinctive: line 39
After a report the user is likely to want regularly, offer once to set it up as a recurring export with /windsor-export.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Finance insights
Read live finance data from Stripe, QuickBooks, PayPal, Xero, Chargebee, and Braintree through Windsor.ai and turn it into a clear report, ranking, comparison, or trend. The main connector ids for this area are stripe, quickbooks, paypal_transaction (PayPal), xero, chargebee, braintree. Other sources in the same category work the same way; find their ids with get_connectors.
Stay in scope
- Use this skill for metrics, rankings, comparisons, trends, and breakdowns of revenue, charges, refunds, payouts, fees, subscriptions and MRR, invoices, and balances across account, charge or transaction, subscription, and invoice.
- If the user asks to connect, reconnect, or add an account, use /windsor-connect instead.
- If the user asks for a recurring, scheduled, or automated export, use /windsor-export instead.
Resolve scope and time
- Call get_connectors first to see which of the six sources have connected accounts. If several accounts match the request, ask which one.
- Read field ids from get_fields for the chosen connector, and get_options for date-filter columns and connector options. Never guess ids or field names.
- Use the date range the user gave. If none, use a sensible preset (last_30d, this_month, last_7d), and state which one you used. Append T to a preset to include today.
Choose the smallest useful read
- Revenue and refunds -> fields [date, gross revenue, refunds] over the preset; report net as gross minus refunds.
- Provider comparison -> the same fields per connector, compared in the answer with the caveat that fee and timing conventions differ.
- Outstanding invoices -> QuickBooks or Xero invoice fields filtered to unpaid or overdue status.
- Subscription health -> Chargebee or Stripe fields for active subscriptions, MRR, churn.
- Keep field sets small and request only the accounts you need. Check for truncated or paginated results before claiming complete coverage.
Accuracy guardrails
- State the currency and whether amounts are gross or net of fees and refunds.
- Accounting periods (Xero, QuickBooks) and payment timestamps (Stripe, PayPal, Braintree) do not line up exactly; say so when reconciling.
- This skill is read-only. Where a source exposes write actions (list_actions tells you; Stripe does), route the change to a confirmed write flow instead of implying it can be done from a report.
- If a field the user wants is not in get_fields, say so rather than substituting a different metric.
- If "best", "top", or "worst" lacks a metric, ask which metric should define the ranking.
Answer with evidence
Lead with the requested result, then state the account or source, the time window, and the numbers behind the conclusion. Keep internal ids and raw JSON out of the answer unless the user asks for them.
Hand-offs
After a report the user is likely to want regularly, offer once to set it up as a recurring export with /windsor-export. Never offer plans, upgrades, or pricing. Never repeat an offer the user declined.
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
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.

