Skill: Add Payee
🚩 Agent Workflow Reminder
Use the Todo List Tool for multi-step tasks (plan, mark a step in-progress, complete it, and update). See AGENTS.md for the concise agent workflow rules.
Payee directives must always be added to a preludes/ journal file, never to monthly or yearly journals. If you encounter a strict payee error (e.g., 'payee ... has not been declared'), resolve it by adding the payee to the appropriate preludes/ file as described below.
This skill describes how to add a new payee to the ledger system.
When to Use
- •When a new merchant, person, organization, or UUID payee is encountered in a transaction or needs to be registered for future use.
Steps
- •
Determine the correct preludes file
- •All payee directives must be placed in a
preludes/journal file, never in a monthly or yearly journal. - •Most payees go in
preludes/self.journal. - •If the payee is specific to an alternative or other scenario, use the appropriate
preludes/*.journalfile.
- •All payee directives must be placed in a
- •
Locate the payee section
- •Find the block of lines starting with
payeein the chosen preludes file.
- •Find the block of lines starting with
- •
Insert the new payee
- •Add a line:
payee <payee-name-or-UUID> - •Place the new payee in strict lexicographical (ASCII/Unicode) order within the payee section.
- •When adding, check the entire payee section for correct placement and move any out-of-order entries if found.
- •Add a line:
- •
Validation
- •Run the formatting and validation scripts to ensure the file remains valid and well-ordered.
Scripts & working directory: See
.github/instructions/developer-workflows.instructions.mdfor canonical guidance — preferpnpm run <script>; if running Python directly, setcwd=scripts/.codeExample: ```powershell python -m format # set cwd to scripts/ python -m check # set cwd to scripts/ ```
Anti-Patterns
- •Never add payees to monthly or yearly journals. Always use a
preludes/file. - •Inserting payees out of order, or failing to correct existing order mistakes