agentleFS
Sign inStart free
d-wweid-wwei/openclaw-financial-services/skills/fsi-er-morning-note/SKILL.md

fsi-er-morning-note

Skill16 starsChanged 9 months agoApache-2.0View on GitHub

Draft concise morning meeting notes summarizing overnight developments, trade ideas, and key events for coverage stocks. Designed for the 7am morning meeting format — tight, opinionated, actionable. Triggers on "morning note", "morning meeting", "what happened overnight", "trade idea", "morning call prep", or "daily note".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep it tight — a morning note should be readable in 2 minutes:

    line 37
  2. Distinctive:

    If a coverage company reported, provide a quick reaction:

    line 66
  3. Distinctive:

    Keep to 1 page max — PMs and traders won't read more

    line 83
  4. Distinctive:

    If you're wrong, own it in the next morning note — credibility matters more than being right every time

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Morning Note

Workflow

Step 1: Overnight Developments

Scan for relevant events across coverage universe:

Earnings & Guidance

  • Any coverage companies reporting overnight or pre-market?
  • Earnings surprises (beat/miss on revenue, EPS, key metrics)
  • Guidance changes (raised, lowered, maintained)

News & Events

  • M&A announcements or rumors
  • Management changes
  • Product launches or regulatory decisions
  • Analyst upgrades/downgrades from competitors
  • Macro data or policy changes affecting the sector

Market Context

  • Overnight futures / pre-market moves
  • Sector ETF performance
  • Relevant commodity or currency moves
  • Key economic data releases today

Step 2: Morning Note Format

Keep it tight — a morning note should be readable in 2 minutes:

[Date] Morning Note — [Analyst Name] [Sector Coverage]

Top Call: [Headline — the one thing PMs need to hear]

  • 2-3 sentences on the key development and why it matters
  • Stock impact: price target, rating reiteration/change

Overnight/Pre-Market Developments

  • [Company A]: One-line summary of earnings/news + our take
  • [Company B]: One-line summary + our take
  • [Sector/Macro]: Relevant sector-wide development

Key Events Today

  • [Time]: [Company] earnings call
  • [Time]: Economic data release (expectations vs. our view)
  • [Time]: Conference or investor day

Trade Ideas (if any)

  • [Long/Short] [Company]: 1-2 sentence thesis + catalyst
  • Risk: What would make this wrong

Step 3: Quick Takes on Earnings

If a coverage company reported, provide a quick reaction:

MetricConsensusActualBeat/Miss
Revenue
EPS
[Key metric]
Guidance

Our Take: 2-3 sentences — is this good or bad for the stock? Does it change our thesis?

Action: Maintain / Upgrade / Downgrade rating? Adjust price target?

Step 4: Output

  • Markdown text for email/Slack distribution
  • Word document if formal distribution is needed
  • Keep to 1 page max — PMs and traders won't read more

Important Notes

  • Be opinionated — morning notes that just summarize news without a view are useless
  • Lead with the most important thing — don't bury the headline
  • "No news" is a valid morning note — say "nothing material overnight, maintaining positioning"
  • Distinguish between actionable events (earnings, M&A) and noise (minor analyst notes, non-events)
  • Time-stamp your takes — if you're writing at 6am, note that pre-market may change by open
  • If you're wrong, own it in the next morning note — credibility matters more than being right every time

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.

Check your setup, free