Update to AI Board Lite

{
  "description": "Builds a working Excel file from a description: a budget, a forecast, a tracker or a simple model, with real formulas instead of typed results, clearly marked input cells and a short explanation of how it works. Use for \"make me a spreadsheet for\", \"build a budget template\", \"maak een excel voor\", \"bouw een begroting\".",
  "included_files": [],
  "name": "build-spreadsheet",
  "skill_md_contents": "---\nname: build-spreadsheet\ndescription: Builds a working Excel file from a description: a budget, a forecast, a tracker or a simple model, with real formulas instead of typed results, clearly marked input cells and a short explanation of how it works. Use for \"make me a spreadsheet for\", \"build a budget template\", \"maak een excel voor\", \"bouw een begroting\".\n---\n\n# Build Spreadsheet\n\nA spreadsheet someone else has to maintain is only useful if they can see\nhow it works. So inputs live in one place and look like inputs, every result\nis a formula, and nothing important is hidden in a typed number.\n\n## Ground rules\n\n- Every calculated cell is a formula. Never type a result.\n- Inputs are separated from calculations and visibly marked (for example a\n  light fill and an \"Inputs\" heading). Assumptions get a label and a unit.\n- Use only numbers the user gives. Where a number is missing, leave the input\n  cell empty or put in a clearly labelled placeholder, and list it at the end.\n- Answer in the language the user writes in, and label the sheet in that\n  language unless they ask otherwise.\n\n## When to use\n\nThe user describes a sheet they need: \"make me a spreadsheet for our hiring\nplan\", \"build a budget template for next year\", \"I need a tracker for these\nprojects\", \"maak een excel voor de begroting\", \"bouw een cashflowoverzicht\".\n\n## Steps\n\n1. **Clarify the shape** if it is not clear: what goes in, what must come out,\n   the period (months, quarters, years) and who will maintain it. Ask once,\n   in one message.\n2. **Propose the structure** before building: the sheets, the input block, the\n   main calculations and the output. Keep it as small as the job allows.\n3. **Build the file.** If this environment can run Python with `openpyxl` (or\n   another way to write `.xlsx`), create the workbook with:\n   - an Inputs block or sheet, marked and labelled with units;\n   - calculations as formulas referencing the inputs, never constants;\n   - totals and checks (for example a cell that shows whether two totals\n     agree);\n   - number formats, frozen header rows and readable column widths.\n   Save it only after the user agreed to the structure, and tell them where it\n   is. If files cannot be created here, give the layout as a table with the\n   formula for every calculated cell, so they can build it by hand.\n4. **Check your own work:** recalculate if possible, confirm there are no\n   formula errors, and test one result by hand.\n5. **Explain it in five lines or fewer:** where the inputs are, what the main\n   output is, and what to change next month.\n\n## Output format\n\n```markdown\n## Structure\n- **Inputs** (sheet 1): headcount plan per month, salary per role, start dates\n- **Costs** (sheet 2): monthly cost per role = salary / 12 × FTE active that month\n- **Summary** (sheet 3): cost per quarter, total for the year, check against budget\n\n## Key formulas\n| Cell | Formula | Meaning |\n|---|---|---|\n| `Costs!C5` | `=Inputs!$D5/12*Inputs!F5` | cost of role 1 in January |\n| `Summary!B4` | `=SUM(Costs!C5:E20)` | total cost Q1 |\n\n## Still to fill in\n- Salary for the data engineer role (`Inputs!D9`) is empty.\n```\n\n## Limits\n\n- Simple to medium models. A full three-statement financial model is out of\n  scope for one conversation; build it in parts.\n- Macros and VBA are not written. Everything works with standard formulas.\n- The file uses a plain, clean layout, not a corporate template, unless the\n  user provides one.\n"
}