Run any Skill in Manus with one click

$pwd:

add-payee

Name: Add Payee
Author: polyipseity

// Add a new payee (merchant, person, organization, or UUID) to the correct preludes journal file, maintaining strict lexicographical order.

Run Skill in Manus

$ git log --oneline --stat

stars:1

forks:0

updated:April 19, 2026 at 11:40

File Explorer

3 files

SKILL.md

readonly

name	add-payee
description	Add a new payee (merchant, person, organization, or UUID) to the correct preludes journal file, maintaining strict lexicographical order.

Skill: Add Payee

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.

Example & guidance: See ./examples.md for a short example of adding a payee to preludes/self.journal. Validate with bun run format and bun run check after adding.

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/*.journal file.
Locate the payee section
- Find the block of lines starting with payee in the chosen preludes file.
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.
Validation

Note: Use the canonical formatting and validation workflow: see .agents/instructions/developer-workflows.instructions.md and .agents/instructions/common-workflows.instructions.md for steps and examples (prefer bun run format and bun run check).

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.
Payees must be in strict lexicographical (ASCII/Unicode) order. When adding, scan the entire payee section and correct any out-of-order entries proactively.

related-skills.json

same repository

edit-journals.md

from "polyipseity/ledger"

Edit hledger journal files following best practices and conventions. Includes prelude includes, balance assertions, tagging, formatting, and validation procedures with anti-patterns to avoid.

2026-05-271

add-transactions.md

from "polyipseity/ledger"

Transcribe transactions from source documents into the hledger ledger. Handles raw data (receipts, invoices, bank statements, OCR text) with proper status markers, tagging, and account registration. For multiple entries, uses a separate subagent for each transaction to enable parallelization and focused scope.

2026-05-061

upsert-octopus-transactions.md

from "polyipseity/ledger"

Strict, step-by-step workflow for upserting Octopus card transactions to the ledger. Requires explicit user clarification for any ambiguity. Enforces contextual matching, mapping, and privacy rules. No guessing or inference allowed.

2026-05-051

match-octopus-statement-transactions.md

from "polyipseity/ledger"

Match Octopus Wallet statement rows to journal transactions and update transaction datetimes. Runs only when explicitly requested.

2026-04-191

monthly-migration.md

from "polyipseity/ledger"

Perform monthly journal migration using hledger close --migrate to close the previous month and open the new month with proper balance assertions and account initialization.

2026-04-191

validate-journals.md

from "polyipseity/ledger"

Validate hledger journal files using check/format scripts. Includes validation procedures and local hook (Husky + lint-staged) verification.

2026-04-191

package.json

"author": "polyipseity"

"repository": "polyipseity/ledger"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Bookkeeping, Accounting, and Auditing ClerksOffice and Administrative Support Occupations43-3031L4

Skill: Add Payee

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.

Example & guidance: See ./examples.md for a short example of adding a payee to preludes/self.journal. Validate with bun run format and bun run check after adding.

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/*.journal file.

Locate the payee section

Find the block of lines starting with payee in the chosen preludes file.

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.

Validation

Note: Use the canonical formatting and validation workflow: see .agents/instructions/developer-workflows.instructions.md and .agents/instructions/common-workflows.instructions.md for steps and examples (prefer bun run format and bun run check).

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.

Payees must be in strict lexicographical (ASCII/Unicode) order. When adding, scan the entire payee section and correct any out-of-order entries proactively.

add-payee

Skill: Add Payee

When to Use

Steps

Anti-Patterns

More from this repository

More from this repository

Skill: Add Payee

When to Use

Steps

Anti-Patterns