fiken
Skill0 starsChanged 27 days agoApache-2.0View on GitHub
Read the Fiken accounting API (fiken.no) — costs/result reports, account balances, transactions, purchases, sales, invoices, contacts, drafts and the receipt inbox. Use when the user mentions Fiken, regnskap, kostnader/resultat/driftsresultat, kontoplan, bilag, kjøp/salg/faktura or mottak, or asks for accounting numbers. Read only; this skill cannot write anything.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- simonstrumse/vibelabs-skillstheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- simonstrumse/vibelabs-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- fiken-bokforingSkill
- fiken-kladdSkill
- folio-bokforingSkill
- folio-kladdSkill
- folioSkill
- reconcileSkill
The file
Files
Fiken (read)
Norwegian accounting (regnskap). Base https://api.fiken.no/api/v2, bearer auth via $FIKEN_READ_TOKEN + $FIKEN_COMPANY_SLUG. All commands go through scripts/fiken.sh.
This skill only reads. It has no write commands, and raw refuses anything but GET. Drafts are in the fiken-kladd skill; posting to the ledger is in the opt-in fiken-bokforing skill. If the user asks for something those cover and they aren't installed, say so; don't write your own API calls.
Setup (one-time):
export FIKEN_READ_TOKEN=... # personal API token (Rediger konto → API)
export FIKEN_COMPANY_SLUG=your-company-as
# or: export FIKEN_ENV=~/.config/fiken/.env (a file defining the two vars)Best practice: create the token as its own Fiken user with the role Se regnskapet uten å kunne gjøre endringer, so Fiken itself refuses writes made with it. See the repo README.
Amounts are in øre — divide by 100 for NOK. The reporting commands already do this; raw JSON does not.
Quick start
F=~/.claude/skills/fiken/scripts/fiken.sh
bash "$F" costs 2026-05 # driftskostnader for a month (GL movement, kl. 4-7)
bash "$F" costs ytd # ... year to date
bash "$F" result 2026-01..2026-05 # revenue / costs / driftsresultat for a range
bash "$F" balances 2026-05-31 # balance per account on a date
bash "$F" help # all commandsDates are YYYY-MM-DD; periods are YYYY-MM, ytd, or YYYY-MM..YYYY-MM. Output is JSON (via jq if present) except the costs/result reports, which print tables with account names. List commands follow Fiken's pagination automatically — results are always complete.
Common workflows
Monthly costs / result — the authoritative way (general-ledger movement, not the purchases list):
bash "$F" costs 2026-05 # itemized cost accounts + sum
bash "$F" result 2026-05 # inntekter, kostnader, driftsresultatThese compute GL movement (accountBalances end − start) per account and bucket by class (3 = revenue, 4-7 = cost, 8 = finance/tax). Use this over purchases — the purchases list misses costs booked as bilag, and the API has no date filter on purchases (the wrapper filters client-side).
Browse documents
bash "$F" purchases 2026-05-01 2026-05-31 # kjøp (filtered client-side on date)
bash "$F" sales 2026-05-01 2026-05-31
bash "$F" journal 2026-05-01 2026-05-31 # bilag
bash "$F" invoices ; bash "$F" contacts <søk> ; bash "$F" bank ; bash "$F" inbox
bash "$F" drafts ; bash "$F" offer-drafts ; bash "$F" invoice-draftsFull reference
Endpoints, VAT types and gotchas: see REFERENCE.md.
For anything not wrapped: bash "$F" raw GET /companies/$FIKEN_COMPANY_SLUG/....
Part of fiken-folio-skills by Fredrik Skorge Salberg (Pifre AS). Not affiliated with Fiken.
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.

