Generate multi-period income statements, balance sheets, and cash flow statements with variance analysis and GAAP compliance.
Create detailed user stories, acceptance criteria, and feature specs
Example: Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example: Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example: Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example: Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Submit your Claude Code skill and start earning
epx add anthropics/knowledge-work-plugins --skill financial-statementsCompatible with
Supported agents
Supports monthly, quarterly, annual, and year-to-date reporting periods with prior-period and prior-year comparisons
Includes materiality thresholds, variance decomposition (volume, price, mix, timing effects), and investigation narratives for flagged items
Provides GAAP presentation guidance (ASC 220/210/230) covering revenue disaggregation, stock-based compe
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfinancial-statementsExecute the skills CLI command in your project's root directory to begin installation:
epx add anthropics/knowledge-work-plugins --skill financial-statementsFetches financial-statements from anthropics/knowledge-work-plugins and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/financial-statements
Restart Cursor to activate financial-statements. Access via /financial-statementsin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
travel-planner
ailabs-393/ai-labs-claude-skills · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
electron-best-practices
jwynia/agent-skills · Productivity · same category
drizzle
lobehub/lobehub · Productivity · same category
using-superpowers
obra/superpowers · Productivity · same category
alpine-js
mindrally/skills · Productivity · same category
financial-statements reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added financial-statements from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
financial-statements reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: financial-statements is focused, and the summary matches what you get after install.
I recommend financial-statements for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: financial-statements is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend financial-statements for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
financial-statements has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in financial-statements — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
financial-statements is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 32