Morning Meeting Brief
Turn overnight developments, trade ideas, and today’s catalysts into a concise, two-minute morning meeting note.
The skill only instructs drafting morning notes and does not specify tool permissions, external writes, or automated trading; the repository README also stages outputs for human review, so no red-line risk is evident. However, it requests trade ideas, ratings, and price targets without user-confirmation rules, data-flow disclosure, sensitive-financial-data handling, rollback, or item-level source attribution, so points are deducted.
The workflow and output format are internally coherent, with no obvious contradiction. Still, it leaves the coverage universe, data sources, consensus methodology, time zones, missing-data handling, abnormal-input behavior, diagnosable failure messages, and reproducible tests unspecified. The score remains within the static-review cap and is reduced for thin failure handling.
The audience and scenario are clear: a 7 a.m. equity-research meeting, with trigger phrases, a two-minute reading target, and email/Slack output. Inputs, non-fit boundaries, regional/time-zone requirements, and mainland-China environment fit are not defined, while terms such as “trade idea” may trigger too broadly, so points are deducted.
The name, description, workflow, and template align, and the skill includes a table, formatting examples, timestamps, and a no-news case. Repository context supplies Apache-2.0 licensing, plugin-validation CI, and contribution guidance, but the skill itself lacks versioning, changelog, named maintenance ownership, dependency notes, FAQs, and structured limitation disclosure, so points are deducted.
The template can produce a structured morning note covering overnight developments, today’s events, trade ideas, and risks. However, it supplies no retrieval, fact-checking, or citation procedure, so the output requires substantial human completion and verification; the file cannot establish correctness of opinions or price targets. The static ceiling is 7, and limited direct-usability evidence lowers the score.
The file provides a clear textual workflow but no skill-specific test suite, execution record, representative completed outputs, or third-party review evidence. Repository CI validates plugin structure rather than the morning-note key paths, so only a low score is justified.
- The skill generates trade ideas, ratings, and price targets that may influence investment decisions; users should define data cutoffs, sources, consensus methodology, and human approval responsibility.
- It does not specify behavior when overnight data is unavailable, conflicting, stale, or when the coverage universe is empty; missing information must not be silently treated as no news.
- The repository README’s human-review disclaimer is shared context and does not by itself provide complete controls in this SKILL.md.
What it does & when to use it
Morning Meeting Brief is designed for the 7 a.m. meeting format used by equity research coverage teams. It organizes earnings, company news, market context, and scheduled events around a clear investment view. The output can include stock impact, rating or price-target actions, trade ideas, and risks. Notes are intended to fit on one page and work for email or Slack distribution.
Organizes overnight and pre-market information across a coverage universe, including earnings, guidance, M&A, management changes, product launches, regulatory decisions, analyst actions, macro data, futures, sector ETFs, commodities, and currencies; produces a structured note with a top call, overnight developments, key events, and trade ideas; summarizes reported earnings in a consensus-versus-actual table with beat or miss indicators; drafts a two- to three-sentence take and suggests rating or price-target action; outputs Markdown text and can be prepared as a Word document when formal distribution is needed.
- A sell-side analyst covering multiple stocks needs a one-page morning note before the daily meeting.
- A portfolio manager wants the most material overnight company or sector developments and their stock implications.
- A trader needs a pre-market trade idea with a catalyst and an explicit risk to the thesis.
- An equity research team needs a quick post-earnings reaction with a recommendation on rating or price target.
Pros & cons
- Clear structure spanning overnight developments, market context, today’s events, and trade ideas.
- Leads with an actionable top call and requires stock impact and risk framing.
- Includes an earnings reaction table and rating or price-target actions.
- Handles a no-news morning explicitly and calls for time-stamped views.
- The SKILL.md does not specify news, market-data, or financial-data sources, nor does it define an automated data-ingestion setup.
- It depends on facts supplied by the user or runtime environment; the source does not establish that it independently performs a live market scan.
- The source provides no test suite, finished examples, or platform compatibility test record for this individual skill.
How to install
In Cowork, open Settings → Plugins → Add plugin, paste https://github.com/anthropics/financial-services, and select the needed vertical. In Claude Code, run claude plugin marketplace add anthropics/financial-services, then claude plugin install equity-research@claude-for-financial-services.
How to use
After installation, trigger it with “morning note,” “morning meeting,” “what happened overnight,” “trade idea,” “morning call prep,” or “daily note.” Provide the coverage universe, analyst name, sector, and available overnight information; it will draft a Markdown note in the morning-meeting format, limited to one page.