finance-memory
Skill2 starsChanged 51 days agoMITView on GitHub
Save and retrieve confirmed personal financial facts, decisions, and their corrections in a private workspace with provenance and supersession. Use when the user provides an update, confirms a choice, or asks to resume prior financial planning.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- finance-dashboardSkill
- finance-gatherSkill
- finance-planSkill
- finance-setupSkill
- investment-researchSkill
- portfolio-reviewSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 8 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Use the installed finance-core in its dedicated environment and selected private workspace.
- Very specific: line 16
Read the selected private workspace's setup.md and the active project's applicable AGENTS.md, when present, to find the interpreter, record …
- Very specific: line 18
Use the selected normalized workspace without overwriting a project's original records.
- Very specific: line 19
Run the commands yourself.
- Very specific: line 20
Read facts.json, decisions.json, and relevant dated reports.
- Distinctive: line 23
Read memory records for exact fields and examples.
- Distinctive: line 24
Keep personal records, source notes, and input envelopes outside the public checkout.
- Distinctive: line 25
Do not store credentials, authentication cookies, recovery codes, or unnecessary personal identifiers.
- Distinctive: line 40
If a user shares a fact during an authorized intake or asks to remember it, save their statement without adding assumptions or requesting …
- Distinctive: line 42
Ask only when the status, meaning, or material conflict cannot be resolved from context.
- Very specific: line 46
Use stable IDs. Repeating identical records is idempotent.
- Very specific: line 53
Run finance-core validate --workspace /private/path and inspect the saved records.
- Distinctive: line 63
Prefer the latest applicable confirmed fact or decision.
- Distinctive: line 72
If the user asks for deletion, inspect the affected records and references and follow the authorized removal request.
- Distinctive: line 80
Do not announce reminders, scheduled reviews, broker changes or future automatic updates unless they were separately requested and actually …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Finance memory
Preserve what the user established and decided, while keeping suggestions and unknowns distinct. Use these files to carry facts and decisions between sessions; do not claim hidden cross-chat memory or automatic session hooks.
Read before writing
Use the installed finance-core in its dedicated environment and selected private
workspace. Run finance-core --help if needed; this skill requires no sibling skill.
Read the selected private workspace's setup.md and the active project's applicable
AGENTS.md, when present, to find the interpreter, record locations, and project adapters.
Use the selected normalized workspace without overwriting a project's original records.
Run the commands yourself; explain results and needed inputs in ordinary language.
Read facts.json, decisions.json, and relevant dated reports. Resolve supersedes
chains and inspect conflicts before answering from memory.
Read memory records for exact fields and examples. Keep personal records, source notes, and input envelopes outside the public checkout. Do not store credentials, authentication cookies, recovery codes, or unnecessary personal identifiers. A private alias is usually enough.
Classify the update
- A fact is a user-confirmed statement with a date and source. Preserve whether the user reported it directly or confirmed a document's contents.
- A proposal is an idea or recommendation. It is not an accepted decision.
- A confirmed decision requires explicit user acceptance, including acceptance already present in the conversation; do not ask for it again.
- An executed decision requires evidence of completion or an explicit user report of completion. Preserve that source; a requested action or prepared order is not a fill.
Tax interpretations, model forecasts, and guessed preferences are not personal facts. Save them in a dated research/scenario report or as an unconfirmed proposal. If a user shares a fact during an authorized intake or asks to remember it, save their statement without adding assumptions or requesting duplicate confirmation. Ask only when the status, meaning, or material conflict cannot be resolved from context.
Save without rewriting history
Use stable IDs. Repeating identical records is idempotent; a changed record with the
same ID is a conflict. Correct a record with a new ID and supersedes pointing to
the old one. Explain the correction and effective date, and retain its source.
For changed decisions, distinguish a new preference from correction of an old error.
Prepare a private envelope containing facts and/or decisions, then run:
finance-core memory --workspace /private/path --input /private/path/update.json.
Run finance-core validate --workspace /private/path and inspect the saved records.
The confirmation field records supplied evidence; the CLI cannot independently prove
user consent or a transaction. Do not set it true to bypass a validation error.
Memory changes do not update balances or execute choices. Use sourced account imports for positions and cash. A newly reported purchase can be saved as a user-reported execution while the ledger remains awaiting reconciliation; state that distinction.
Use memory in later work
Prefer the latest applicable confirmed fact or decision. Explain contradictions instead of inventing an explanation for them. Preserve dates and conditional choices, such as a plan that applies only after a job starts or a debt is repaid. Review facts whose circumstances or rules may have changed before using them again.
Model-sharing rules govern exports, not memory storage. Saving a sensitive fact does not authorize uploading the file to another service or a separate model API. Reading it in a hosted agent can itself send its contents to that agent's provider; the export switches do not restrict the host's filesystem or computer-use tools. If the user asks for deletion, inspect the affected records and references and follow the authorized removal request. Append-only correction does not prohibit deleting the user's private data.
Report the result
Summarize what was saved, superseded, left unresolved, or kept as a proposal. Link the actual private files and state any remaining reconciliation need. Do not announce reminders, scheduled reviews, broker changes or future automatic updates unless they were separately requested and actually configured.
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.

