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

fiken-bokforing

Skill0 starsChanged 27 days agoApache-2.0View on GitHub

Post Fiken drafts to the ledger (bokføring) after the user explicitly says yes, plus a write escape hatch for the Fiken API. Opt-in; install only if you want the agent to book in Fiken. Use when the user asks to bokføre/post a specific Fiken draft and has confirmed it in this conversation.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every call is logged to ~/.local/state/fiken-folio-skills/audit.jsonl and the result is read back.

    line 22

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fiken bokføring (opt-in)

Posting a draft turns it into a booked purchase. That is irreversible — booked entries can't be deleted, only corrected with a credit note in Fiken.

The rule: run a command from this skill only after the user has said yes to that exact draft in the same conversation. Show them the draft first (supplier, date, amount in NOK, account, VAT) using the fiken skill. Never post as part of a chain of other steps.

What locks this, honestly: nothing deterministic. Every command requires --confirm, but you can type that flag yourself. The real check is the user's agent tool asking before it runs a command containing --confirm. If the user hasn't set that up, recommend posting in Fiken instead.

Setup: same FIKEN_WRITE_TOKEN + FIKEN_COMPANY_SLUG as fiken-kladd.

F=~/.claude/skills/fiken-bokforing/scripts/fiken-bokforing.sh
bash "$F" post-draft <draftId> --confirm
bash "$F" raw <METHOD> <path> [json] --confirm   # any other write; GET is in the fiken skill

Every call is logged to ~/.local/state/fiken-folio-skills/audit.jsonl and the result is read back. A post is never retried automatically: after a timeout or 5xx, check fiken purchases before trying again.

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

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