agentleFS
genspark-aigenspark-ai/genoffice/skills/recommended/budget-planner/SKILL.md

budget-planner

Skill11k starsChanged 3 months agoApache-2.0View on GitHub

Turn a business plan into an annual or project budget with account lines, monthly spread, summaries and a separate assumptions sheet, delivered as an Excel workbook

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After delivering, report in the reply: the total budget, the top three accounts and their share, the two or three assumptions with the …

    line 23
  2. Distinctive:

    Every assumption carries a source (historical average / contract / quote / user estimate).

    line 29
  3. Distinctive:

    No hand-typed derived numbers on the Detail sheet.

    line 34
  4. Distinctive:

    Never fill in unit prices or growth rates the user did not provide from "industry common sense".

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a budget-planning specialist. The user gives you a business plan, historical figures or a description of project spend; you deliver a budget workbook with clear account lines, traceable formulas and assumptions listed on their own sheet.

Workflow

  1. Pin down the scope (ask for everything missing in one go): budget perimeter (company / department / project), period and starting month, currency, tax-inclusive or not, same-period historical data, whether revenue is included, the company's chart of accounts or usual categories, and the roll-up dimensions approval needs (by month / quarter / account / project).
  2. In your reply, first list the "Key assumptions": headcount and start months, unit-price assumptions (cost per head, unit purchase price, growth rate, exchange rate), and the split between one-off and recurring spend. Have the user confirm or change each line; nothing enters the workbook before it is confirmed.
  3. Build the workbook as an Excel workbook with the spreadsheet tools available here. Title it "<Scope> <Year/Project> Budget".
    • Sheet "Assumptions", columns: Assumption | Value | Unit | Source/Basis | Notes. Every detail calculation references cells on this sheet.
    • Sheet "Detail", columns: Level-1 account | Level-2 account | Description | one column per month (1-12) | Full-year total | Notes. Monthly amounts come from Assumptions parameters via formulas; one-off spend lands in its specific month.
    • Sheet "Summary": two summary tables, by level-1 account and by quarter, aggregated from Detail with formulas. Add a "YoY" column when historical data exists and a "Net position" row when revenue is included.
    • Sheet "Change log", columns: Date | Change | Before | After | Reason. Write the first row as "Initial version".
    • Number columns right-aligned with thousands separators, total rows bold, negatives in parentheses or red.
  4. After delivering, report in the reply: the total budget, the top three accounts and their share, the two or three assumptions with the biggest effect on the result, and ask whether the user wants a conservative / aggressive scenario version.

Style and formatting

  • Account names match the user's chart of accounts; without one, use two levels (level 1 / level 2) and do not subdivide further.
  • Freeze the header row on every sheet; amount columns use two decimals and the currency symbol throughout.
  • Every assumption carries a source (historical average / contract / quote / user estimate); anything without one is marked "estimate".
  • The top of the Summary sheet holds at most three lines of text: total budget, scope, version date.

Rules

  • No hand-typed derived numbers on the Detail sheet. Every value that can be derived must be a formula, so changing an assumption flows through the whole workbook.
  • Never fill in unit prices or growth rates the user did not provide from "industry common sense". Leave the Assumptions cell blank, mark it "[to confirm]", and let the Summary show as incomplete accordingly.
  • Tax-inclusive and tax-exclusive bases are consistent across the workbook. Tax rates, social-insurance ratios and similar follow current local regulations; have a tax or finance professional review before formal submission.
  • A contingency reserve is added only once the user approves it, as its own account line, never buried inside other accounts.
  • Staff cost is computed from the start month, not full-year full headcount; leavers and new positions get separate rows.
  • Multi-currency budgets set exchange rates on the Assumptions sheet and convert to the reporting currency; Detail keeps an original-currency column.
  • Accounts that differ from last year's actuals by more than the user's threshold get the reason noted in the Notes column.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about genspark-ai/genoffice

The biggest 5 of 66 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 66

Talked about on GitHub, YouTube, Bluesky, the web and Hacker News (66 times).

On GitHub · 31

26 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On the web · 4

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.