Fin Earnings Summary Agent Skill
Summarize and analyze earnings calls (法說會) including financial highlights, management commentary, guidance, and analyst Q&A key takeaways. Use this skill when the user needs to digest an earnings call transcript, extract key financial data and forward guidance, compare actual results vs consensus estimates, or prepare for an investor meeting — even if they say 'summarize this earnings call', 'what did management say about next quarter', 'did they beat estimates', or 'key takeaways from the 法說會'.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/asgard-ai-platform/skills --skill fin-earnings-summaryWhat comes with it
6 152 bytes besides the instructionThe instruction itself
8 sections, as written by the authorEarnings Call Summary & Analysis
Framework
IRON LAW: Separate Facts from Spin
Management presentations emphasize positives and downplay negatives.
Your job is to extract: (1) hard numbers, (2) forward guidance with
specificity level, and (3) what management DIDN'T say (notable omissions).
"Strong momentum" without numbers is spin.
"Revenue grew 15% to NT$2.3B" is a fact.
Earnings Call Structure
| Section | Duration | What to Extract |
|---------|----------|----------------|
| Prepared Remarks | 15-20 min | Revenue, EPS, margins, key metrics — actual vs guidance vs consensus |
| Management Commentary | 10-15 min | Forward guidance, strategic initiatives, market outlook |
| Q&A | 20-30 min | What analysts are worried about (revealed by their questions), management's candor level |
Key Data Points to Extract
Financial Highlights (vs Consensus)
| Metric | Actual | Consensus | Beat/Miss | YoY Change |
|--------|--------|----------|-----------|-----------|
| Revenue | ${X} | ${X} | Beat/Miss by {%} | {%} |
| EPS | ${X} | ${X} | Beat/Miss by {%} | {%} |
| Gross Margin | {%} | {%} | ±{pp} | ±{pp} |
| Operating Margin | {%} | {%} | ±{pp} | ±{pp} |
Forward Guidance
| Metric | Guidance | Prior Guidance | Change | Specificity |
|--------|---------|---------------|--------|------------|
| Next Q Revenue | ${X}-${X} | ${X}-${X} | Raised/Maintained/Lowered | Specific/Vague |
| Full Year EPS | ${X}-${X} | ... | ... | ... |
Qualitative Signals
- New product/initiative announcements
- Market/demand commentary (strengthening, stable, weakening)
- Competitive positioning updates
- Capital allocation (buyback, dividend, M&A, capex)
- Tone: confident, cautious, defensive, evasive
Analysis Steps
Phase 1: Extract Numbers
- Revenue, EPS, margins — actual vs consensus vs prior guidance
- Beat or miss on each line item
Phase 2: Evaluate Guidance
- Did they raise, maintain, or lower guidance?
- How specific is the guidance? (range vs vague)
- Implied assumptions (growth rate, margin trajectory)
Phase 3: Read the Q&A
- What are analysts asking? (reveals market concerns)
- Where does management deflect or give vague answers? (red flags)
- New information that wasn't in prepared remarks
Phase 4: Compare to Market Reaction
- Stock price move post-earnings
- Does the market reaction align with the numbers? (sometimes a beat is sold off = guidance disappointed)
Output Format
# Earnings Summary: {Company} — {Quarter}
## Headline
{One sentence: beat/miss + most important takeaway}
## Financial Highlights
| Metric | Actual | Consensus | vs Consensus | YoY |
|--------|--------|----------|-------------|-----|
| Revenue | ... | ... | ... | ... |
| EPS | ... | ... | ... | ... |
## Forward Guidance
| Metric | New Guidance | Prior | Change |
|--------|------------|-------|--------|
| ... | ... | ... | Raised/Maintained/Lowered |
## Management Commentary (Key Points)
1. {key point with quote}
2. {key point}
## Q&A Highlights
- **Analyst concern**: {topic} → **Management response**: {summary}
- **Notable omission**: {what wasn't addressed}
## Market Reaction
- Post-earnings move: {+/-X%}
- Interpretation: {why the market reacted this way}
## Investment Implication
{What this means for the investment thesis — bullish/neutral/bearish signal}
Gotchas
- Beats can be "low quality": Beating EPS by cutting costs while revenue misses is a low-quality beat. Revenue beats with margin expansion is high quality. Differentiate.
- Guidance matters more than actuals: The market prices in expectations. A company that beats Q3 but lowers Q4 guidance will often sell off. Focus on forward-looking signals.
- Taiwan 法說會 specifics: Many Taiwan companies (especially TSMC, MediaTek) hold English-language calls. Others are Chinese-only. MOPS has summary notes even if you can't attend live.
- Consensus estimates can be stale: If estimates haven't been updated recently, a "beat" may just mean the bar was set too low. Check when consensus was last revised.
- One quarter doesn't make a trend: Don't overreact to a single quarter. Look at 3-4 quarters to identify real trends vs noise.
References
- For financial statement analysis, see the data-financial-analysis skill
- For Taiwan stock data sources, see the tw-stock-analysis skill
Other skills for the same job
different authors, same section of the catalogue
List OKX Agentic Wallet exclusive trading competitions, register users for contests, track participation and leaderboard rankings, and claim won rewards. Use when users want to list available trading competitions or trading cups, view competition rules / prize pool / total prizes, register or sign up or enroll or join a contest, check the leaderboard (who is winning) or their own rank (am I in the prize zone, what is my place), ask did I win or query participation / claim status, claim won rewards or prizes from completed competitions, see which wallet account they registered with, or submit Telegram / WeChat / Email / Twitter contact for prize delivery to top-tier winners.
Prepare for client review meetings with portfolio performance summary, allocation analysis, talking points, and action items. Pulls together account data into a concise meeting-ready format. Use before quarterly reviews, annual checkups, or ad-hoc client meetings. Triggers on "client review", "meeting prep for [client]", "quarterly review", "prep for [client name]", or "client meeting".
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".
Hunting skill for race condition vulnerabilities. Built from 12 public bug bounty reports including modern HTTP/2 single-packet attack cases (James Kettle DEF CON 2023 "Smashing the State Machine"; RyotaK / Flatt Security 10,000-request first-sequence-sync expansion 2024). Covers coupon double-redemption, gift-card double-spend, MFA-OTP-validate race, account-create race, faucet/crypto token double-mint, email-activation race, vote/upvote inflation, password-reset token race, rate-limit bypass via concurrent requests. Use when hunting race conditions, TOCTOU bugs, MFA-bypass-via-timing.
> Read Discord for financial research using opencli (read-only). Use this skill whenever the user wants to read Discord channels, search for messages in trading servers, view guild/channel info, monitor crypto or market discussion groups, or gather financial sentiment from Discord. "what's happening in the trading Discord", "show Discord channels", "list my servers", "Discord sentiment on BTC", "what are people saying in Discord about AAPL", "monitor crypto Discord", any mention of Discord in context of reading financial news, market research, or trading community discussions. This skill is READ-ONLY — it does NOT support sending messages, reacting, or any write operations.
> Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026). Use this skill whenever a user asks about SWIFT CSP, CSCF controls, SWIFT security attestation, KYC-SA portal, SWIFT architecture types (A1/A2/A3/A4/B), mandatory vs advisory controls, independent assessment, SWIFT secure zone, secure flow zone, MFA for operators, SWIFT messaging security, payment fraud prevention on SWIFT, gap analysis for CSCF, or compliance with SWIFT's 32 controls Environment, Know and Limit Access, Detect and Respond. Control 2.4 (Back-Office Data Flow Security) is now mandatory in v2026. v2026 attestation window is July 1– December 31, 2026. Trigger for any SWIFT CSP or CSCF compliance question.
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.
Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026). Use this skill whenever a user asks about SWIFT CSP, CSCF controls, SWIFT security attestation, KYC-SA portal, SWIFT architecture types (A1/A2/A3/A4/B), mandatory vs advisory controls, independent assessment, SWIFT secure zone, secure flow zone, MFA for operators, SWIFT messaging security, payment fraud prevention on SWIFT, gap analysis for CSCF, or compliance with SWIFT's 32 controls (25 mandatory, 7 advisory in v2026) across the three objectives: Secure Your Environment, Know and Limit Access, Detect and Respond. Control 2.4 (Back-Office Data Flow Security) is now mandatory in v2026. v2026 attestation window is July 1– December 31, 2026. Trigger for any SWIFT CSP or CSCF compliance question.
How to use it
Take asgard-ai-platform/fin-earnings-summary from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.