Skill
A skill is a written procedure a coding agent follows to change a library: when to use it, its rules, its steps, when to stop, and when it is done. folio ships seven: set-up, configure, write, organise, address, publish and run.

The person using folio talks to their agent in plain words, and the agent picks the matching skill. The skills call the folio command the way an agent calls git, so the person never needs to learn it.

The set is fixed. What is specific to a kind of document lives in its genre's card, and what is specific to a procedure lives in a workflow, so neither needs a skill of its own.

Seven skills around one command

Every skill acts on the library through the same command. Pick a command to see which skills call it.

The seven skills, each joined to the folio command in the middle folio the command set-up configure write organise address publish run

folio check: every skill. A change is done only when the gate passes.

folio journal add: six of the seven. Each records a decision as a new entry; address answers comments instead.

folio new: write alone. Every document any skill produces goes through write.

folio map add: write, which puts a new document on a map, and organise, which keeps the maps current.

folio mv: organise alone, with promote and rm --to, so a move keeps every link, comment and date.

folio annotations: address answers threads, write reads them and leaves flags, organise checks them before a move.

folio config set: set-up and configure, the only two skills that write the charter.

folio export: publish alone, after the gate.

set-up

Installs a library once: the charter, the home page, the first journal entry.

  • init
  • config
  • pack on
  • journal add
  • check

configure

Changes the charter: packs, home maps, genres, variants, workflows.

  • config
  • pack
  • genre add
  • workflow add
  • journal add
  • check

write

Adds or revises any document, in its genre's voice, and puts it on a map.

  • search
  • new
  • cite
  • map add
  • annotations
  • journal add
  • check

organise

Moves, merges, promotes and retires, with every link kept; runs health passes.

  • maps
  • map add
  • mv
  • promote
  • rm --to
  • tags
  • journal add
  • check

address

Answers the comments readers left, on the page each was left on.

  • annotations
  • genre
  • check

publish

Exports the static site, and builds and freezes papers.

  • up
  • export
  • paper build
  • paper freeze
  • journal add
  • check

run

Follows a workflow step by step; every document it makes goes through write.

  • workflows
  • genre
  • journal add
  • check
Each card lists the main commands its skill names, without the folio prefix. The command is shared; what differs between skills is which calls they make and in what order.

Who talks to whom

  1. The person

    Asks in plain words: "add a concept for this", "tidy the maps".

  2. The agent

    Matches the words to a skill by its description, and reads it.

  3. The skill

    Its steps, rules and stops, followed in order.

  4. folio

    The command the skill calls, ending at the gate.

Every skill starts the same way

This is why a new genre, workflow or pack never needs a new skill: each one reads what the library offers before it acts.

  1. Find the library: the nearest folio.yaml.
  2. Read the charter.
  3. List the genres and workflows available, from the library, its packs and the core.
  4. Read the card for the genre in hand.
The trap: thinking a new kind of document needs a new skill. Every skill starts by reading the charter, the genres and the workflows, so it already knows what a new genre or pack adds.

Related

Every skill that changes a document ends at the gate, then commits exactly the files it touched.

Where they live

The skills are installed in a library's .agents/skills/, for any coding agent that reads that folder.