/earnings-analyzer
Analyze quarterly and annual earnings reports including EPS beat/miss analysis, revenue trends, margin expansion, forward guidance parsing, and management commentary extraction.
$ npx -y skills add CoWork-OS/CoWork-OS --skill earnings-analyzer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/earnings-analyzer
Context preview
The summary Claude sees to decide when to auto-load this skill.
Analyze quarterly and annual earnings reports including EPS beat/miss analysis, revenue trends, margin expansion, forward guidance parsing, and management commentary extraction.
SKILL.md
earnings-analyzer.SKILL.mdname: earnings-analyzer
description: "Analyze quarterly and annual earnings reports including EPS beat/miss analysis, revenue trends, margin expansion, forward guidance parsing, and management commentary extraction."
Earnings Analyzer
Purpose
Analyze quarterly and annual earnings reports including EPS beat/miss analysis, revenue trends, margin expansion, forward guidance parsing, and management commentary extraction.
Routing
- Use when: Use when the user asks about earnings reports, quarterly results, EPS beat/miss, revenue analysis, margin trends, earnings guidance, earnings quality, or management commentary from earnings calls.
- Do not use when: Do not use when the request is about building a financial model (use Financial Modeling), valuation (use DCF Valuation), or general stock screening (use Market Screener).
- Outputs: Outcome from Earnings Analyzer: comprehensive earnings analysis with EPS assessment, revenue decomposition, margin waterfall, guidance evaluation, quality indicators, and key takeaways.
- Success criteria: Returns a structured earnings analysis with beat/miss classification, revenue and margin trends, guidance comparison to consensus, earnings quality assessment, and clear investment implications.
Trigger Examples
Positive
- Use the earnings-analyzer skill for this request.
- Help me with earnings analyzer.
- Use when the user asks about earnings reports, quarterly results, EPS beat/miss, revenue analysis, margin trends, earnings guidance, earnings quality, or management commentary from earnings calls.
- Earnings Analyzer: provide an actionable result.
Negative
- Do not use when the request is about building a financial model (use Financial Modeling), valuation (use DCF Valuation), or general stock screening (use Market Screener).
- Do not use earnings-analyzer for unrelated requests.
- This request is outside earnings analyzer scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | company | string | Yes | Company name or ticker symbol | | analysisType | select | Yes | Type of earnings analysis | | question | string | Yes | Your specific earnings analysis question | | quarter | string | No | Specific quarter to analyze (e.g., Q3 2024, FY 2024) | | earningsData | string | No | Earnings data to analyze (e.g., EPS $2.15 vs $2.05 est, revenue $15.2B vs $14.8B est) |
Runtime Prompt
- Current runtime prompt length: 1165 characters.
- Runtime prompt is defined directly in `../earnings-analyzer.json`.
Read more
name: earnings-analyzer description: "Analyze quarterly and annual earnings reports including EPS beat/miss analysis, revenue trends, margin expansion, forward guidance parsing, and management commentary extraction."
Earnings Analyzer
Purpose
Analyze quarterly and annual earnings reports including EPS beat/miss analysis, revenue trends, margin expansion, forward guidance parsing, and management commentary extraction.
Routing
- Use when: Use when the user asks about earnings reports, quarterly results, EPS beat/miss, revenue analysis, margin trends, earnings guidance, earnings quality, or management commentary from earnings calls.
- Do not use when: Do not use when the request is about building a financial model (use Financial Modeling), valuation (use DCF Valuation), or general stock screening (use Market Screener).
- Outputs: Outcome from Earnings Analyzer: comprehensive earnings analysis with EPS assessment, revenue decomposition, margin waterfall, guidance evaluation, quality indicators, and key takeaways.
- Success criteria: Returns a structured earnings analysis with beat/miss classification, revenue and margin trends, guidance comparison to consensus, earnings quality assessment, and clear investment implications.
Trigger Examples
Positive
- Use the earnings-analyzer skill for this request.
- Help me with earnings analyzer.
- Use when the user asks about earnings reports, quarterly results, EPS beat/miss, revenue analysis, margin trends, earnings guidance, earnings quality, or management commentary from earnings calls.
- Earnings Analyzer: provide an actionable result.
Negative
- Do not use when the request is about building a financial model (use Financial Modeling), valuation (use DCF Valuation), or general stock screening (use Market Screener).
- Do not use earnings-analyzer for unrelated requests.
- This request is outside earnings analyzer scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | company | string | Yes | Company name or ticker symbol | | analysisType | select | Yes | Type of earnings analysis | | question | string | Yes | Your specific earnings analysis question | | quarter | string | No | Specific quarter to analyze (e.g., Q3 2024, FY 2024) | | earningsData | string | No | Earnings data to analyze (e.g., EPS $2.15 vs $2.05 est, revenue $15.2B vs $14.8B est) |
Runtime Prompt
- Current runtime prompt length: 1165 characters.
- Runtime prompt is defined directly in `../earnings-analyzer.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill