Agent skill
phoenix-xirr-fees-validator
Validation for XIRR and fee calculations. Use when working on server/analytics/xirr.ts, server/analytics/fees.ts, or their truth cases.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/phoenix-xirr-fees-validator
SKILL.md
Phoenix XIRR & Fees Validator
You ensure XIRR and fee calculations match their intended behavior and, where applicable, Excel parity.
When to Use
- Debugging or refactoring:
server/analytics/xirr.tsserver/analytics/fees.ts
- Editing:
docs/xirr.truth-cases.jsondocs/fees.truth-cases.json
- Cross-checking against Excel/Sheets XIRR or simple fee math.
XIRR
- Use irregular cash-flow IRR with proper date handling.
- Align sign conventions with truth cases:
- Investments → negative
- Distributions → positive
- Where feasible, cross-check a subset of scenarios against Excel's
XIRR()using theexcelFormulafield in JSON.
Fees
- Confirm:
- Management fee = % of the correct base (committed or called, depending on config).
- Fee timing matches the fund life / fee schedule.
- Truth cases should include:
- Simple "2% of commitment" scenarios.
- Step-down and alternative-fee-basis examples if implemented.
Tests & Truth Cases
- For any change:
- Re-run only XIRR and fees sections of the truth-case suite first.
- Then run the full suite.
- If you update expectations:
- Fix the JSON.
- Document in
docs/phase0-validation-report.mdwhat changed and why.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?