⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

univer-cli

dream-num@dream-num⭐ 79 stars· last commit 1mo ago· 3 open issues

Use when installing or operating Univer CLI for .univer files, spreadsheets, documents, slides, Base databases, Board canvases, cross-Unit embedding, worktrees, Facade authoring, inspection, verification, import/export, screenshots, or viewer handoff.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐ 79 on GitHubGitHub ↗

Growing

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

Build with Univer

License Support OS

Languages: English | 简体中文

An agent skill for building applications with the Univer Office SDK. build-with-univer tells your coding agent which Univer SDK fits the job, where to start, and what to avoid, so it stops guessing from stale training data.

What it covers

You are buildingSDK
An embedded spreadsheet, document, or slide editorWeb SDK
Real-time collaboration on your own auth and storage, Office import/exportServer SDK
A CLI or tool that lets agents read and edit Office contentAI SDK
A plain HTML page bound to live Sheet dataBinding SDK

The skill resolves package versions at build time, never blocks a proof of concept on a missing license, and lists the superseded servers, packages and API names that models still suggest.

Install

npx skills add dream-num/skills --skill build-with-univer

Add -g for a user-level install, or -a claude-code -a codex -a opencode to pick agents. Re-run the command to update.

Manual installation

Copy skills/build-with-univer into your agent's skills directory:

git clone https://github.com/dream-num/skills.git && cd skills
mkdir -p ~/.claude/skills && cp -R skills/build-with-univer ~/.claude/skills/              # Claude Code
mkdir -p ~/.agents/skills && cp -R skills/build-with-univer ~/.agents/skills/              # Codex
mkdir -p ~/.config/opencode/skills && cp -R skills/build-with-univer ~/.config/opencode/skills/   # OpenCode
mkdir -p ~/.cursor/skills && cp -R skills/build-with-univer ~/.cursor/skills/              # Cursor

Example prompts

Embed a spreadsheet editor in this React app and read and write cells from code.
Let several people edit one spreadsheet in real time, with our own login and database.
Build a CLI my coding agent can use to inspect and edit spreadsheets and slides.
Add xlsx import and export endpoints to this Node API. We have no license yet.
Make a plain HTML dashboard that charts and edits cells in our team's spreadsheet.

You do not need to name Univer or the skill; the agent loads it when the task matches.

Requirements

  • Node.js and npm
  • Network access to docs.univer.ai and the npm registry, which the skill uses for current docs and versions

Contributing

  • The skill lives in skills/build-with-univer: SKILL.md routes, references/ holds one page per SDK plus versions and what to avoid.
  • Keep SKILL.md under 500 lines, pin no versions in the text, and run npm run validate before publishing changes.

License

This repository is licensed under the Apache-2.0 License.

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/univer-cli/SKILL.md4.5 KBupstream ↗
    ---
    name: univer-cli
    description: "Use when installing or operating Univer CLI for .univer files, spreadsheets, documents, slides, Base databases, Board canvases, cross-Unit embedding, worktrees, Facade authoring, inspection, verification, import/export, screenshots, or viewer handoff."
    hidden: true
    ---
    
    # Univer CLI
    
    Terminal-native authoring and inspection for multi-Unit `.univer` files. The CLI provides isolated
    worktrees, version-matched Facade guidance, model readback, and browser review.
    
    Install:
    
    ```bash
    npm install -g univer-cli
    univer doctor
    ```
    
    ## Keep the CLI current
    
    Use these commands to compare the installed CLI with the latest public release:
    
    ```bash
    univer --version
    npm view univer-cli@latest version --registry=https://registry.npmjs.org/
    ```
    
    When a newer version is available, complete the current Univer task before updating:
    
    ```bash
    univer update
    univer doctor --json
    univer skills get core
    ```
    
    If `univer update` reports that the shared daemon must stop, rerun it with `--force` after confirming
    that stopping the daemon is safe. Reload core and the target Unit Skill after every update.
    
    ## Start here
    
    This file is the discovery entry, not the operational guide. Before using Univer commands for a
    task, load the complete core Skill from the installed CLI:
    
    ```bash
    univer skills get core          # shared model, workflow, evidence, and handoff
    univer skills get core --full   # include direct references and templates
    ```
    
    Runtime Skills ship with the CLI so their commands and Facade APIs match the installed version.
    
    ## Core Model
    
    - A `.univer` path is the authoritative multi-Unit target. Always address the file explicitly.
    - A Unit is a top-level Sheet, Doc, Slide, Base, or Board identified by `unitId`; sheet names, pages,
      tables, ranges, shapes, and records live inside that Unit.
    - `trunk` is the reviewed main line. A worktree is an isolated scope for agent changes; there is no
      implicit current worktree.
    - Command success is not correctness evidence. Read back the target model, verify task-specific
      assertions, and inspect rendered output when appearance matters.
    
    Use public CLI and Facade surfaces. The worktree commit path is the durable write boundary, and
    merge remains an explicit review decision.
    
    ## Unit Skills
    
    After core, load the Skill matching the target top-level Unit before authoring:
    
    ```bash
    univer skills get sheet
    univer skills get doc
    univer skills get slide
    univer skills get base
    univer skills get board
    ```
    
    Use `univer skills list` to discover the installed set. Each Unit Skill owns its creation recipe,
    Facade entrypoints, readback guidance, and visual verification requirements.
    
    For cross-Unit composition, load the additional Topic Skill after the host and child Unit Skills:
    
    ```bash
    univer skills get embed
    ```
    
    For a cross-Unit formula in a Sheet cell or formula-driven Shape, load its Topic Skill after the
    Host and Sheet or Base Source Unit Skills:
    
    ```bash
    univer skills get cross-unit-formula
    ```
    
    ## Task Routing
    
    | Task | Load and use |
    | --- | --- |
    | Inspect or edit spreadsheet values, formulas, formatting, charts, or tables | core + `sheet` |
    | Create or refine document paragraphs, rich text, tables, charts, or page layout | core + `doc` |
    | Build or review presentation pages, shapes, text, or images | core + `slide` |
    | Create or edit structured Base tables, fields, records, or views | core + `base` |
    | Create or edit a Board canvas, charts, and other elements | core + `board` |
    | Embed one Unit inside another Unit | core + host Unit + child Unit + `embed` |
    | Read a Sheet range or Base table column from a Sheet cell or formula-driven Shape | core + Host Unit + Source Unit + `cross-unit-formula` |
    
    ## Why Univer CLI
    
    - One `.univer` target can contain Sheet, Doc, Slide, Base, and Board Units addressed by `unitId`.
    - Worktrees isolate agent changes until review and merge.
    - Offline `api show` / `api find` resolves exact Facade symbols for the installed SDK.
    - Runtime readback and the viewer verify the stored model and rendered result.
    - Import/export and screenshots use the product runtime rather than unrelated file writers.
    
    Do not edit `.univer` storage directly or substitute unrelated writers. Follow the loaded core and
    Unit Skills for the supported path.
    
    ## Diagnose
    
    ```bash
    univer --help
    univer doctor
    univer skills list
    univer skills path
    ```
    
    Use `univer help <command>` for exact syntax. If the CLI is unavailable or `doctor` reports a
    blocking runtime failure, stop and report the diagnostic instead of switching tools.
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/dream-num-skills-skills-univer-cli.md

// REPO STATS

79 stars
3 open issues
Last commit: 1mo ago