DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to build a model whose numbers recalculate on change with Open Sheet

Write a P&L as React and export an .xlsx whose formulas update when an assumption moves.

Who it is forA finance analyst or founder who needs a model the reader can change, not a static table of numbers.

The problemSpreadsheets written by agents break silently when rows shift, because cell addresses like B7 go stale.

The outcomeAn .xlsx with live formulas and named assumptions, such as =B4*growth, that recalculates in the recipient's spreadsheet app.

What you need first

  • Node
  • npm or pnpm
  • A coding agent or text editor
  • A local dev server to preview the sheet

Steps

  1. npx @open-sheet/cli init my-sheets
  2. cd my-sheets && npm install && npm run dev
  3. Describe the P&L to your coding agent and have it write the React source using references such as ref('pl').column('revenue').
  4. Check the sheet in the viewer, then use its export option to download the .xlsx. (inferred, check the README)
  5. Open the workbook, change the growth assumption, and confirm the net income column moves.

Prompt for your agent

In the open-sheet repo at <project path>, write a P&L sheet from this description: <description of revenue, costs and assumptions>. Use references such as r.cell and ref().column, with no A1 addresses, then export the .xlsx to <output path>. Verify that changing the growth assumption in the exported file moves the net income column.

Caveat. The README says nothing is published to npm yet but also says 0.1.0 is published, so confirm the npx command resolves before relying on it.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for lianghsun/open-sheet and "Build a model whose numbers recalculate on change"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer