Univer Skills
The build-with-univer skill picks the Univer SDK for a sheet, document or slides job and removes stale package names
- 79 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- The skill only steers the agent and runs no code itself, but it suggests npm commands and reads documentation over the network
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/univer-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill only steers the agent and runs no code itself, but it suggests npm commands and reads documentation over the network
This is third-party code. Review the repository files before installing.
What it does
Univer Skills is a set of skills for apps built on the Univer Office SDK. The main one, `build-with-univer`, reads the task and picks one of four SDKs: Web SDK for an embedded spreadsheet, document or slide editor, Server SDK for collaboration on your own auth and storage, AI SDK for agent-facing command-line tools, Binding SDK for an HTML page bound to live cells. The skill resolves package versions at build time, does not block a prototype on a missing license and lists the servers, packages and API names that models still suggest from stale data. The repository also holds skills for the CLI, theming, integration, plugins and Pro features.
Who it is for. Web developers embedding a spreadsheet or document editor into a product, and teams that need an agent tool for reading and editing Office files.
Good fit when
- You add a spreadsheet editor to a React app and read cells from code
- Several people edit one sheet in real time while login and database stay yours
- A Node service gains endpoints for importing and exporting xlsx files
- An agent needs a command-line tool that inspects and edits sheets and slides
- An HTML dashboard with charts has to pull data from the team spreadsheet
Not a fit when
- You need a one-off edit of a single xlsx file without building an app
- Your stack uses another spreadsheet library and Univer is not planned
- The agent environment has no network: the skill consults the docs and the npm registry
- You want a ready editor with no code: the skill only steers development
Example request
Embed a spreadsheet editor in this React app and read and write cells from codeLimitations
The skill uses the network: it reads documentation at docs.univer.ai and package versions from the npm registry, so hints lose accuracy without access. A Univer Pro license is not included, and some features, including collaboration and Office exchange, live in the paid `@univerjs-pro` packages. The README lists Claude Code, Codex, OpenCode and Cursor, on Linux and macOS. The main SKILL.md is short; details sit in per-SDK references the agent loads as the task needs.
How to disable. Delete the `build-with-univer` folder from the agent skills directory, for example `~/.claude/skills/`. If you installed through `npx skills`, remove the folder by hand or use your client removal command.
FAQ
How do I install the Univer skill in Claude Code?
Run `npx skills add dream-num/skills --skill build-with-univer`. The `-g` flag installs at user level and `-a claude-code -a codex -a opencode` picks agents. Running the command again updates the skill.
Do I have to name Univer in the prompt?
No. The agent loads the skill when the task is about spreadsheets, documents, collaboration or office AI, even when the library name is not mentioned.
How do the four SDKs differ?
Web SDK renders and calculates in the browser or Node, Server SDK handles collaboration, storage and Office import and export, AI SDK builds command-line tools for agents, Binding SDK binds a plain HTML page to live cells.
Do I need a license to start a prototype?
No, the skill does not block a prototype on a missing license. Pro packages need one later, and the versions and license reference says when.
What does the skill require?
Node.js, npm and network access to docs.univer.ai and the npm registry. The skill reads current docs and versions from there.
Discussion
No questions or reviews yet.
Related
Skillsdotnet-skills: a skill installer for .NET
dotnet-skills
An installer for a .NET skill catalog that picks skills from project files for Claude Code, Codex, Copilot and Gemini CLI
Official Unity skill set for agents: editor control, builds, 2D and 3D, UI, URP, audio, multiplayer and monetization
Official DevExpress skills for Copilot, Claude Code, Cursor and Codex: DevExtreme, Blazor, WPF, WinForms, Reports, XAF and VCL
UnitySkills
unity-skills
Driving the Unity editor from an agent through a REST API and skills: scenes, objects and components. Three permission modes, Unity 2022.3 and newer
A skills collection filtered and verified by JetBrains: Kotlin, Spring, Vue, deployment, documents and Google Workspace.
A Chinese skill set of coding standards for Vue3, UniApp, eight backend stacks, MySQL and Git so an agent writes in one style.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Univer Skills (this card) | yes | 79 | ||
| Excel MCP Server | no | not required | 4,297 | reads and edits Excel files over MCP, with no SDK choice or app building |
| huashu-excel | no | 464 | a skill for working with Excel files, not for building an app on Univer |
README in short
The README presents `build-with-univer` as a guide to the Univer Office SDK. It maps a task to one SDK, lists typical prompts and explains manual installation by copying the folder into the skills directory of the agent. Contributors are told to keep SKILL.md under 500 lines and run `npm run validate`.
README badge
Original SKILL.md
--- name: build-with-univer description: Build applications with Univer Office SDK, covering the Web SDK (browser Office editors, headless Sheets and Docs in Node), Server SDK (self-hosted OT collaboration, storage, auth, Office import/export), AI SDK (agent-operated Office CLIs, reviewable Worktrees), and Binding SDK (plain HTML pages bound to live Sheet data). Use when starting or designing any Univer-based app or choosing Univer packages, including when the user describes a spreadsheet, document, collaboration, or AI-office need without naming a Univer package. --- # Build with Univer Univer Office SDK is a family of npm packages, not a single library. Pick the SDK by what you are building, then follow its example repository where one exists. Do not guess APIs from memory: Univer changes quickly and older material is widely mis-remembered. ## Pick the SDK | You are building | SDK | Packages | Start from | | --- | --- | --- | --- | | An embedded spreadsheet, document, or slide editor in a web app | Web SDK | `@univerjs/*`, `@univerjs-pro/*` | [references/web-sdk.md](references/web-sdk.md) | | Generate or modify Sheet or Doc data, or calculate formulas in Node.js | Headless Web SDK | `@univerjs/*` without editor UI | [references/web-sdk.md](references/web-sdk.md#headless-in-node) | | Real-time multi-user editing with your own auth and storage | Server SDK + Web SDK client | `@univerjs-pro/collaboration-*` | [references/server-sdk.md](references/server-sdk.md), `quick-start` example | | Server-side Office import/export (xlsx, docx, pptx) | Server SDK | `@univerjs-pro/exchange-node` | [references/server-sdk.md](references/server-sdk.md), `exchange` example | | Your own CLI or tool that lets agents read and edit Office content | AI SDK | `@univer-cli/*` | [references/ai-sdk.md](references/ai-sdk.md), `01-content-operations` example | | A plain HTML/CSS/JS page showing or editing live Sheet cells | Binding SDK | `@univerjs-labs/*` | [references/binding-sdk.md](references/binding-sdk.md) (installed packages' docs) | Real products often combine them. A collaborative editor is Web SDK in the browser plus Server SDK behind it. An HTML dashboard over shared data is Binding SDK on top of a Server SDK backend. Running in Node does not by itself select Server SDK or AI SDK: use Headless Web SDK for document processing, Server SDK for collaboration/storage or Office import/export, and AI SDK for agent tools. ## The four SDKs - **Web SDK** is the engine. It runs in the browser or headless in Node and covers six products: Sheets and Docs (open source), Slides, Boards, Bases and PDFs (Pro). Choose the runtime before assembling plugins: browser editors need UI; headless Node processes document data without an editor UI. Follow each product's runtime guide rather than assuming Node support. For new Web SDK integrations, default to plugin mode; preserve existing presets or an explicit request for them. All programmatic control goes through the Facade API. - **Server SDK** is a set of Node.js packages you assemble inside your own backend: transport, endpoint, service and a database adapter, with an OT collaboration engine and history, comment and Worktree services. Your application owns users, permissions, storage and deployment. - **AI SDK** builds Office CLIs for agents. Your app owns the Commander program and its commands; the SDK supplies headless runtimes, content inspection and execution, offline Facade API search, rendering and layout lint, and Worktree-based review. - **Binding SDK** connects ordinary HTML pages to Sheet data with `data-univer-*` attributes. Pages render in a sandboxed iframe connected to a host, and need a Server SDK collaboration backend. ## Working principles