Skip to content
cccskills
FreePublished on GitHub

codexkit-finance-variance-story

Analyze budget-versus-actual or forecast-versus-actual performance and turn finance data into a management-ready narrative using variance logic, drivers, cash impact, and forward actions. Use when finance, FP&A, or business leaders need commentary, management accounts, or performance explanation. Do not use for bookkeeping entries, tax filing preparation, or legal accounting sign-off.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md3.2 KB
  • agents/openai.yaml197 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Finance Variance Story

Purpose

Convert raw financial movements into an explanation that managers can act on.

When to use

  • Actual results differ materially from budget or forecast.
  • A monthly business review needs finance commentary.
  • Leadership wants the story behind revenue, margin, cash, or cost movement.

When not to use

  • The request is for journal entries or bookkeeping.
  • Formal statutory accounting treatment is the main question.

Inputs

  • actuals, budget, forecast, or prior-period data
  • key business drivers and assumptions
  • notable one-offs, mix effects, or timing issues
  • audience: board, exec, functional leader, or finance team

Procedure

  1. Separate size, timing, volume, price, mix, and controllability effects where possible.
  2. Identify the 3-5 drivers that actually explain most of the movement.
  3. Connect the variance to cash, margin, runway, or operational implications.
  4. Distinguish structural change from one-off noise.
  5. Recommend actions, owners, and forecast implications.
  6. Flag missing data and confidence limits.

Output

  • executive summary of the variance story
  • driver table with impact and explanation
  • cash and margin implications
  • forward-looking actions and watchpoints
  • short management commentary in plain language

Definition of done

  • A non-finance leader can understand the business story.
  • The explanation distinguishes causes from symptoms.
  • Recommended actions follow from the analysis.

Examples

  • "Explain why gross margin missed plan this quarter and what actions we should take."
  • "Turn these budget versus actual numbers into management commentary for the board pack."

Quality Criteria

  • All claims reference specific frameworks, standards, or quantifiable data
  • Content matches the stated audience's expertise level
  • Recommendations are actionable — each includes a concrete next step
  • No unsupported assertions or generic filler language

Verification (4C)

CheckQuestion
CorrectnessDo referenced frameworks and standards match their official definitions?
CompletenessAre all key concepts covered without significant gaps for the stated audience?
Context-fitWould this be useful for someone new to this domain, or is it too advanced/too basic?
ConsequenceIf a stakeholder acted on this immediately, what could they misinterpret?

Edge Cases

  • Conflicting frameworks — State which framework takes precedence and why. Document the trade-off explicitly.
  • Rapidly changing domain — Note information currency date. Flag sections likely to need updates.
  • Audience has mixed expertise levels — Provide a glossary and mark advanced sections as optional.

Changelog

  • v1.0.0 — Initial release

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit26Updated Oct 11, 2026

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit26Updated Oct 11, 2026

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit26Updated Oct 11, 2026

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit26Updated Oct 11, 2026

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit26Updated Oct 11, 2026

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit26Updated Oct 11, 2026

See all skills by hoavdc

Report a problem with this skill