agentleFS
Mihir-BhargavMihir-Bhargav/Avanza-AI-trading-terminal/.claude/skills/portfolio-brief/SKILL.md

portfolio-brief

Skill1 starsChanged 22 days agoMITView on GitHub

On-demand, read-only portfolio brief for a brokerage account exposed through the portfolio MCP server — P&L, concentration, FX exposure, upcoming earnings for holdings, and news behind notable moves. Use when the user asks for a portfolio brief (daily or weekly), "how is my portfolio", or what is moving in their holdings. Never scheduled; runs only when asked. Never places, suggests placing, or prepares an order.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read-only, always: Never place, modify or cancel an order, and never call a tool that could.

    line 12
  2. Very specific:

    Every number comes from get_brief_data: Do not compute weights, percentages, totals or dates yourself.

    line 15
  3. Distinctive:

    Nothing leaves the chat: Do not write the brief, amounts or holdings into any file in the repository.

    line 18
  4. Distinctive:

    No silent gaps: If a tool fails or returns nothing (earnings lookup, news), say so in the brief.

    line 21
  5. Very specific:

    Call avanza-portfolio → get_brief_data (earnings_within_days: 30 for daily, 45 for weekly).

    line 26
  6. Distinctive:

    Write the brief in the format below.

    line 39
  7. Distinctive:

    Keep it tight. A daily brief should read in under a minute.

    line 75

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Portfolio brief

Argument: daily (default) or weekly.

Hard rules

  • Read-only, always. Never place, modify or cancel an order, and never call a tool that could. Only an explicit, unambiguous instruction from the user could change this, and the skill does not assume one.
  • Every number comes from get_brief_data. Do not compute weights, percentages, totals or dates yourself. Quote the tool's fields. If a number is not there, say it is not available rather than deriving it.
  • Nothing leaves the chat. Do not write the brief, amounts or holdings into any file in the repository. Save to a location outside the repo only if the user names one.
  • No silent gaps. If a tool fails or returns nothing (earnings lookup, news), say so in the brief. Do not omit the section.

Steps

  1. Call avanza-portfolio → get_brief_data (earnings_within_days: 30 for daily, 45 for weekly).
  2. For weekly, also call get_transactions with from_date = 7 days ago. List trades and sum commission per trade. Quote each one. State the total as "commissions paid this week" only if every trade has a commission value.
  3. News, targeted, not a firehose. Fetch news only for holdings in flags (big day move, deep loss) or in earnings.upcoming, plus the top 3 holdings by weight:

    • stocks: yahoo-finance → get_yahoo_finance_news
    • market context: efn-news → get_latest_news or get_market_commentary (one call; skim for anything touching holdings or currency and rates)

    For each flagged move, find the actual catalyst. If you cannot find one, write "no identifiable catalyst found". Do not invent a reason.

  4. Write the brief in the format below.

Format

PORTFOLIO BRIEF — <daily|weekly> — <as_of>

Value <portfolio> <currency> · invested <invested> · cash <cash> (<cash_pct>%)
Unrealized <unrealized_pnl> <currency> (<unrealized_pnl_pct>%)
1d <insights_total> · 1w <change> (<pct>%) · 1m … · ytd …

MOVERS & FLAGS
- <name> <day_change_pct>% today — <catalyst, or "no identifiable catalyst">
- <name> <pnl_pct>% unrealized — <one line: thesis intact / broken / unknown>
- stale prices: <list, or none>

CONCENTRATION
Top holding <name> <top1>% of invested · top 3 <top3>%
By type: … · By currency: … 

EARNINGS AHEAD (<within_days>d)
- <ticker> <date> (in <n> days), or "none"; list lookup failures explicitly

NEWS THAT MATTERS
- 2–5 bullets, each tied to a specific holding or to currency and rates. Source-linked.

WEEK IN TRADES (weekly only)
- <date> <BUY/SELL> <instrument>, commission <x> <currency>

WORTH A LOOK (optional, max 2)
- Observations only, e.g. "<name> is 3% of invested and down 15%: earnings in 12
  days decides whether the thesis holds." No buy or sell instructions. If the user
  asks about acting on one, apply the repository's trading rules first (take-profit
  and stop-loss before entry, leverage cap, earnings check).

Keep it tight. A daily brief should read in under a minute.

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.