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…
Build and analyze three-statement financial models with integrated income statement, balance sheet, and cash flow projections, scenario analysis, and key driver assumptions.
$ npx -y skills add CoWork-OS/CoWork-OS --skill financial-modeling --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/financial-modelingContext preview
The summary Claude sees to decide when to auto-load this skill.
Build and analyze three-statement financial models with integrated income statement, balance sheet, and cash flow projections, scenario analysis, and key driver assumptions.
name: financial-modeling description: "Build and analyze three-statement financial models with integrated income statement, balance sheet, and cash flow projections, scenario analysis, and key driver assumptions." version: "1.0.0" metadata: author: CoWork OS Contributors <info@coworkosapp.com>
Build and analyze three-statement financial models with integrated income statement, balance sheet, and cash flow projections, scenario analysis, and key driver assumptions.
| Name | Type | Required | Description | |---|---|---|---| | modelType | select | Yes | Type of financial model to build | | company | string | Yes | Company name or ticker symbol | | question | string | Yes | Your specific modeling question | | historicalData | string | No | Historical financial data or key metrics (e.g., last 3 years revenue, margins) | | assumptions | string | No | Key assumptions to use (e.g., 15% revenue growth, 30% EBITDA margin target) |
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.