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…
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.
/earnings-analyzerContext 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.
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." version: "1.0.0" metadata: author: CoWork OS Contributors <info@coworkosapp.com>
Analyze quarterly and annual earnings reports including EPS beat/miss analysis, revenue trends, margin expansion, forward guidance parsing, and management commentary extraction.
| 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) |
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
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…
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide…
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…
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,…
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.
Use when the user asks for a repository-wide or scoped-path security scan.