Skip to main content
Backend Developmentproompteng

bilig-workpaper

Use @bilig/workpaper WorkPaper state for workbook formulas, agent spreadsheet tools, MCP file-backed or remote demo editing, and XLSX formula bug reports without driving spreadsheet UI.

Stars
29
Source
proompteng/bilig
Updated
2026-05-31
Slug
proompteng--bilig--bilig-workpaper
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/proompteng/bilig/HEAD/.claude/skills/bilig-workpaper/SKILL.md -o .claude/skills/bilig-workpaper.md

Drops the SKILL.md into .claude/skills/bilig-workpaper.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Bilig WorkPaper Agent Skill

Use this skill when an agent needs spreadsheet-style formulas but the work should run through files, terminal commands, TypeScript, HTTP routes, or MCP tools instead of Excel UI automation.

When To Trigger

Trigger this skill for tasks involving:

  • workbook-shaped business logic in Node.js services;
  • formula readback after writing cells;
  • quote, budget, payout, pricing, import-validation, or forecast models;
  • agent spreadsheet tools that need deterministic cell addresses;
  • MCP clients that can run a stdio server or call a Streamable HTTP endpoint;
  • reduced XLSX formula bugs that need a local report.

Do not trigger it for manual spreadsheet editing, Office macros, VBA, pivots, charts, COM automation, or exact Excel desktop behavior unless the user explicitly asks to compare Bilig against an Excel oracle.

Command Safety

Do not build shell commands by concatenating user text. Treat the commands below as literal templates, validate workbook paths before use, and reject values containing newlines, backticks, $(, ;, &, |, <, or >. Prefer MCP client command plus args arrays or direct TypeScript calls when inserting user-provided paths or cell references.

First Choice: MCP

Use MCP when the host can run a stdio server or call a Streamable HTTP server. Configure stdio as an argument array, not a shell-concatenated string:

If the host supports installable skills, first check that the public skill package is discoverable:

npx --yes skills@latest add https://bilig.proompteng.ai --list
npx --yes skills@latest add proompteng/bilig --skill bilig-workpaper --list

Before wiring a client, an agent can check the direct WorkPaper loop with:

{
  "command": "npm",
  "args": ["exec", "--package", "@bilig/workpaper@latest", "--", "bilig-agent-challenge", "--json"]
}

For the actual file-backed MCP path, run the package-owned challenge first:

{
  "command": "npm",
  "args": ["exec", "--package", "@bilig/workpaper@latest", "--", "bilig-mcp-challenge", "--json"]
}

{
  "command": "npm",
  "args": [
    "exec",
    "--package",
    "@bilig/workpaper@latest",
    "--",
    "bilig-workpaper-mcp",
    "--workpaper",
    "./pricing.workpaper.json",
    "--init-demo-workpaper",
    "--writable"
  ]
}

Run bilig-mcp-challenge and treat its returned tools array as the source of truth for the currently published package. The core file-backed tools are:

  • list_sheets
  • read_range
  • read_cell
  • set_cell_contents
  • get_cell_display_value
  • export_workpaper_document
  • validate_formula

After a write, always read the dependent output cell and export the WorkPaper document. If the listed tool set includes set_cell_contents_and_readback, prefer it for stateless clients because the edit and dependent readback happen in one tool call. If it is absent, call set_cell_contents, then read_cell or read_range, then export_workpaper_document.

For remote MCP clients, use the stateless demo endpoint when the client supports Streamable HTTP:

https://bilig.proompteng.ai/mcp
https://bilig.proompteng.ai/mcp/workpaper

The remote endpoint is request-local and does not write user files. Use it for connector smoke tests, tool discovery, and agent onboarding; use the file-backed stdio command when the workflow must persist a project WorkPaper JSON file.

Second Choice: Direct TypeScript

Use @bilig/workpaper directly when workbook logic belongs in a service, queue worker, test, or route:

import { WorkPaper, exportWorkPaperDocument, serializeWorkPaperDocument } from '@bilig/workpaper'

const workbook = WorkPaper.buildFromSheets({
  Inputs: [
    ['Metric', 'Value'],
    ['Customers', 20],
    ['Average revenue', 1200],
  ],
  Summary: [
    ['Metric', 'Value'],
    ['Revenue', '=Inputs!B2*Inputs!B3'],
  ],
})

const inputs = workbook.getSheetId('Inputs')
const summary = workbook.getSheetId('Summary')
if (inputs === undefined || summary === undefined) {
  throw new Error('Workbook is missing required sheets')
}

workbook.setCellContents({ sheet: inputs, row: 1, col: 1 }, 32)
const revenue = workbook.getCellDisplayValue({ sheet: summary, row: 1, col: 1 })
const saved = serializeWorkPaperDocument(exportWorkPaperDocument(workbook, { includeConfig: true }))

console.log({ revenue, savedBytes: saved.length })

XLSX Formula Clinic

When the user has a reduced XLSX formula/import bug, generate a local report through an argument array:

{
  "command": "npm",
  "args": [
    "exec",
    "--package",
    "@bilig/workpaper@latest",
    "--",
    "bilig-formula-clinic",
    "./reduced.xlsx",
    "--cells",
    "Summary!B7,Inputs!B2"
  ]
}

The report is local. It does not upload workbook contents. Ask for a reduced public fixture rather than private customer spreadsheets.

Required Verification

Return readback, not vibes. A successful agent response should include:

  • the exact edited sheet and A1 cell;
  • before values for relevant inputs and dependent outputs;
  • after values read from the recalculated workbook;
  • persistence evidence from serialized or exported WorkPaper state;
  • restore or reimport checks when file boundaries matter;
  • limitations for unsupported formulas or Excel-only features.

If any readback step fails, report the blocker instead of claiming the workbook was updated.

Reference URLs