Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From finny
Variance analysis between two periods, two entities, or actual vs budget. Maps to open-string intent `variance_analysis`. User invocation: /finny:finance:variance-analysis [scope]
npx claudepluginhub postergully/finny-claude-plugin --plugin finnyHow this skill is triggered — by the user, by Claude, or both
Slash command
/finny:variance-analysis [base period] [comparison period] [entity] (optional — decomposer will ask if missing)[base period] [comparison period] [entity] (optional — decomposer will ask if missing)The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Compare two NetSuite financial states (period-over-period, entity-over-entity,
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Compare two NetSuite financial states (period-over-period, entity-over-entity, or actual vs budget) and surface significant variances with explanations from Finny's brain.
This command maps to the OPEN-STRING intent variance_analysis. NOT in the
bridge bless-list — passes through to Finny. Hand off to intent-decomposer
with:
intent: 'variance_analysis'user_question: <the user's full request, including $ARGUMENTS>intent-decomposer will apply Rule 4 (first-call permission gate per session).
Variance analysis usually needs at least two periods or two entities to compare. If the user gives only one, decomposer's AskUser flow will ask for the comparison target.
intent-decomposer — owns the orchestration.judging-output — handles the resulting envelope.