Agent skills for Figa

Give your agent a connection and a repeatable way to use it. This pack contains standard SKILL.md instructions, supporting references and optional Python helpers. It works independently of a particular chat product; installation and tool access depend on your runtime.

Download Figa agent skills (.zip)

Five workflows

• figa-api-read: read context, expenses and summaries through MCP or REST. The existing name is retained for compatibility.
• figa-expense-write: create and update expenses with explicit recurring scope and retry rules.
• figa-organize-expenses: manage local categories and tags, preserving the intended assignments.
• figa-recurring-bills: confirm invoices, explain forecasts and change monthly billing settings with the intended scope.
• figa-integration-playbooks: build an event-driven or scheduled workflow with verification and source deduplication.

Install and connect

1. Extract the ZIP and read its README. Copy the individual figa-* folders into your agent’s skill directory. Each installed folder must directly contain SKILL.md; the ZIP’s outer folder is not itself a skill.
2. Use your runtime’s documented loader. OpenClaw uses workspace or shared skill directories; see the OpenClaw guide. For Hermes, dots, Grok bots, Muse or another agent, check its supported skill and tool formats.
3. If there is no skill loader, provide the relevant instructions and references as task context. Configure a working tool connection separately; instructions cannot add capabilities to a client.
4. Connect MCP with OAuth, or configure REST with FIGA_API_BASE_URL=https://api.figa.cc and FIGA_API_KEY in the runtime’s secret store. Only the optional REST helpers need Python 3.10+.
5. Start with one read: “Show this month’s expenses in my Home workspace, separating confirmed amounts and estimates.” Verify the selected workspace and dates.

Agents vary in support for remote MCP, OAuth, skill loading and interactive MCP Apps views. The pack does not imply a native integration or verified support for every named client. The connected server’s current schemas and your granted permissions determine what is available.

Try a practical task

Use this invoice to update the matching recurring electricity bill. Show me the match and proposed amount before saving, then list the bills still unpaid this month.

The invoice walkthrough explains the matching, confirmation and follow-up analysis. Your external tool reads the document; Figa stores the expense and bill data.

For forecasting, try: “Use seasonal forecasts for my gas bills and explain the December estimate.” The forecast guide covers the four methods, missing history and reliability.

The skills distinguish recurring scopes, full tag-set replacement, confirmed amounts and estimates, and binary payment status. Reuse operation IDs for retries and keep a source ledger for recurring automation.

Existing installations can still use the OpenClaw download link. Both downloads are built from the same maintained sources.