agentleFS
shashu10shashu10/personal-finance-skills/skills/portfolio-review/SKILL.md

portfolio-review

Skill2 starsChanged 51 days agoMITView on GitHub

Review a sourced personal balance sheet, cross-account exposure, and hypothetical trades against the user's explicit limits. Use for portfolio checkups and proposal assessment, not order execution.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use thesis-tracker.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    thesis-tracker

    Use when building or updating Public Equity Investing thesis trackers. Do not use for generic news summaries, trade pitches, or first-pass memos.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Use the installed finance-core.

    line 13
  2. Very specific:

    Read the selected private workspace's setup.md and the active project's applicable AGENTS.md, when present, to resolve the interpreter and …

    line 15
  3. Very specific:

    Read ledger.json, rules.json, facts.json, and decisions.json in the selected private workspace.

    line 19
  4. Distinctive:

    Read review semantics before interpreting totals or proposals.

    line 32
  5. Distinctive:

    Do not describe securities or private investment marks as available cash.

    line 35
  6. Distinctive:

    Add such analysis only with sources and a stated method.

    line 41
  7. Very specific:

    Read the user's actual limits.

    line 43
  8. Very specific:

    Use the proposal contract.

    line 51
  9. Distinctive:

    Do not describe a limit flag from the calculation as a broker block or execution safeguard.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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

Portfolio review

Explain the portfolio's condition and the effect of a proposed change using verified inputs. A stock's research rating and suitability for this portfolio are separate questions.

Load the current state

Use the installed finance-core; inspect finance-core --help if needed. The runtime must be installed from the trusted project checkout in a dedicated environment. Read the selected private workspace's setup.md and the active project's applicable AGENTS.md, when present, to resolve the interpreter and any documented status, summary, or research adapter. Preserve the project's existing context and risk checks. Run the commands yourself; explain results and needed inputs in ordinary language. Read ledger.json, rules.json, facts.json, and decisions.json in the selected private workspace. Resolve superseded records and distinguish confirmed decisions from earlier model suggestions. This skill is usable without sibling skills.

Run finance-core validate --workspace /private/path, then finance-core summary --workspace /private/path --as-of YYYY-MM-DD using the review date. Review source dates, currency/FX dates, included accounts, restricted assets, and known coverage gaps. Confirm that wrapper accounts are not counted twice. Missing, stale, unverified, estimated, or future-dated data cannot support a definitive within-limits finding. A successful schema check does not establish complete coverage.

Explain the balance sheet

Read review semantics before interpreting totals or proposals. Distinguish gross assets, liabilities, net worth, unrestricted cash, and restricted or illiquid assets. Label unknown totals and partial coverage explicitly. Do not describe securities or private investment marks as available cash.

Aggregate a security across included accounts using the actual security identity. Confirm any mapping between share classes, ADRs, or listings before combining them. The core aggregates exact symbols; it does not infer economic equivalence, fund look-through exposure, sector classification, correlations, or option delta exposure. Add such analysis only with sources and a stated method.

Read the user's actual limits. null means report only, not zero and not permission to choose a threshold on their behalf. If the user explicitly sets a limit, update only the relevant rule and record that confirmed choice with its date and source. Explain observed concentration or leverage even when no threshold is configured.

Evaluate a proposal

Capture account alias, security, side, quantity, proposed price, and as-of date. Use the proposal contract; keep the input in the private workspace. Run finance-core review --workspace /private/path --proposal /private/path/proposal.json. Report its status and reasons, including needs_data or report-only results. The calculation uses a hypothetical cash-funded transaction and does not execute it.

Do not describe a limit flag from the calculation as a broker block or execution safeguard. The calculation also does not model taxes, fees, lot selection, slippage, settlement, or future price paths. Research those separately when they affect the user's requested decision. Unknown tax basis or jurisdiction cannot be replaced by an assumed zero tax cost. State a proposal's funding source; do not infer margin authorization from buying power.

Write and save the review

Lead with the material finding and its practical implication. Compare current and proposed values on the same as-of date and valuation basis, with a short assumptions table where useful. Cite the exact private snapshot, rules, and proposal files. Separate measured facts, model-generated research, and your conditional assessment.

Save the review privately. Record an unaccepted idea only as proposal; a confirmed decision is not an executed trade. Reconcile actual fills through subsequent account evidence before updating positions. No command in this workflow places orders.

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.