agentleFS
Sign inStart free
Salberg87Salberg87/fiken-folio-skills/skills/folio/SKILL.md

folio

Skill0 starsChanged 27 days agoApache-2.0View on GitHub

Read the Folio business-bank API (folio.no) — accounts, balances, transactions, bookkeeping events, ledger categories, receipts and statement PDFs. Use when the user mentions Folio or their bedriftskonto, or asks to pull transactions, check a balance, look at events that need bookkeeping, or download a kontoutskrift. Read only; cannot write, book or move money.

  • Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Use a key with read access only if Folio offers one, otherwise a key without payment access.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Folio (read)

Norwegian business banking. Base https://api.folio.no/v2, bearer auth via $FOLIO_READ_KEY. All commands go through scripts/folio.sh.

This skill only reads. Notes, categories and receipts on events are in the folio-kladd skill; completing events is in the opt-in folio-bokforing skill. Money is never moved by any of them: Folio's API can only create payment drafts that a person must sign in Folio, and these skills don't even do that.

Setup (one-time):

export FOLIO_READ_KEY=...               # create at https://app.folio.no/til/api-tilgang
# or: export FOLIO_ENV=~/.config/folio/.env   (a file defining FOLIO_READ_KEY)

Use a key with read access only if Folio offers one, otherwise a key without payment access.

Quick start

F=~/.claude/skills/folio/scripts/folio.sh

bash "$F" accounts                            # list accounts
bash "$F" transactions 2026-01-01 2026-06-09  # transactions in range
bash "$F" events 2026-05-01 2026-05-31        # events, incl. which still need bookkeeping
bash "$F" event <eventId>                     # one event: complete? receipts? category?
bash "$F" help                                # all commands

Dates are YYYY-MM-DD. Output is JSON (piped through jq if available); statements/attachments download as files.

Common workflows

Transactions and balances

bash "$F" transactions 2026-05-01 2026-05-31 --merchants
bash "$F" transactions 2026-05-01 2026-05-31 --account <accountNumber>   # one account
bash "$F" balance <accountNumber> 2026-05-31

What needs bookkeeping — an event with complete: false. A LedgerCategory (bash "$F" category <id>) flags requiresPurpose, requiresParticipants, requiresAttachment, requiresReview and the VAT code. There is no list endpoint for categories — find ids on past events (bash "$F" events <range> | jq '.events[].ledgerCategory').

Statement PDF (e.g. for regnskap)

bash "$F" statement 2026 05 -o ~/Downloads/folio-2026-05.pdf
bash "$F" statement --range 2026-01-01 2026-03-31 -o ~/Downloads/folio-q1.pdf

Export to CSV — pull JSON, shape with jq:

bash "$F" transactions 2026-01-01 2026-06-09 \
  | jq -r '.transactions.booked[] | [.bookingDate, .description, .transactionAmount.amount, .transactionAmount.currency] | @csv'

Export to CSV — pull JSON, shape with jq:

bash "$F" transactions 2026-01-01 2026-06-09 \
  | jq -r '.transactions.booked[] | [.bookingDate, .description, .transactionAmount.amount, .transactionAmount.currency] | @csv'

Full reference

Endpoints, schemas and gotchas: see REFERENCE.md. For anything not wrapped: bash "$F" raw GET /some/path.

Part of fiken-folio-skills by Fredrik Skorge Salberg (Pifre AS). Not affiliated with Folio.

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.

Check your setup, free