Agent skill

SenseNova PPT Workbench

by OpenSenseNova in OpenSenseNova/SenseNova-Skills

Opens the PPT Workbench web editor for an existing SenseNova HTML slide deck so you can preview, inspect and visually edit it without regenerating.

MITAuto-check: notesDocuments & Office

Install SenseNova PPT Workbench

skills CLI

$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-ppt-workbench -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install OpenSenseNova/SenseNova-Skills sn-ppt-workbench --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sn-ppt-workbench .claude/skills/sn-ppt-workbench && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "sn-ppt-workbench" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-ppt-workbench into .claude/skills/sn-ppt-workbench/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-ppt-workbench", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-ppt-workbench

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-ppt-workbench -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install OpenSenseNova/SenseNova-Skills sn-ppt-workbench --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sn-ppt-workbench .agents/skills/sn-ppt-workbench && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sn-ppt-workbench" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-ppt-workbench into .agents/skills/sn-ppt-workbench/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-ppt-workbench", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-ppt-workbench -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install OpenSenseNova/SenseNova-Skills sn-ppt-workbench --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sn-ppt-workbench .cursor/skills/sn-ppt-workbench && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sn-ppt-workbench" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-ppt-workbench into .cursor/skills/sn-ppt-workbench/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-ppt-workbench", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/OpenSenseNova/SenseNova-Skills.git --path skills/sn-ppt-workbench

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-ppt-workbench -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install OpenSenseNova/SenseNova-Skills sn-ppt-workbench --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sn-ppt-workbench .gemini/skills/sn-ppt-workbench && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sn-ppt-workbench" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-ppt-workbench into .gemini/skills/sn-ppt-workbench/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-ppt-workbench", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install OpenSenseNova/SenseNova-Skills sn-ppt-workbench

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-ppt-workbench -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sn-ppt-workbench .github/skills/sn-ppt-workbench && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sn-ppt-workbench" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-ppt-workbench into .github/skills/sn-ppt-workbench/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-ppt-workbench", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-ppt-workbench -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install OpenSenseNova/SenseNova-Skills sn-ppt-workbench --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sn-ppt-workbench .opencode/skills/sn-ppt-workbench && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sn-ppt-workbench" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-ppt-workbench into .opencode/skills/sn-ppt-workbench/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-ppt-workbench", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sn-ppt-workbench
GitHub stars: 5.7k
Token cost: ~2.5k tokens
SKILL.md length: 1,008 words
Files: 28 (incl. scripts, references)
Skills in repo: 36
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Opens the PPT Workbench web editor for an existing SenseNova HTML slide deck so you can preview, inspect and visually edit it without regenerating.

Works in 8 steps: Do not run sn-ppt-entry,… → Do not edit slide files directly. The… → If deck_dir is missing, auto-detect only… → …
Opening a previously generated SenseNova slide deck in the visual editor
SKILL.md covers Use Cases, Hard Rules, Invocation and CLI Subcommands (direct launch…, plus 5 more sections
Runs JavaScript and Python scripts from its folder; calls python3, node and python; needs API_SERVER_KEY and WORKBENCH_GATEWAY_API_KEY

What it does

The skill starts or reuses the editing web UI for a deck that already exists, running scripts/open_workbench.py with a deck folder or, if none is given, auto-detecting the latest deck under ppt_decks in the current workspace. A deck folder may hold task_pack.json, per-slide or per-page HTML files, or a root-level HTML deck.

It never regenerates or edits slide files itself and refuses to run the generation or export skills; editing happens in the web UI. If startup fails or is skipped, it reports why instead of falling back to generation. The helper prefers forwarded or canvas URLs when you may be on SSH, chat or another device, binds to localhost on native hosts, and binds to all network interfaces under Docker or WSL so remote users can reach it. task_pack.json is treated as progress state and outline.md as the editable story.

When your agent uses it

Opening a previously generated SenseNova slide deck in the visual editor
Inspecting or previewing slides without regenerating them
Locating the most recent deck in the current workspace and opening it

Example prompts

“Open the PPT Workbench for the deck in ./ppt_decks/q3-roadmap.”
“Open the latest deck in this workspace in the visual editor.”
“I'm on SSH; give me a URL I can use to edit the slides.”

Requirements

Python 3 to run the helper script
A generated SenseNova HTML deck folder

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

Do not run sn-ppt-entry, sn-ppt-standard, page-html, batch-page-html, or export.
Do not edit slide files directly. The WebUI handles user-visible editing.
If deck_dir is missing, auto-detect only under $(pwd)/ppt_decks.
If no usable deck is found, ask the user for the absolute deck_dir.
Workbench startup is best-effort. If it skips or fails, report the reason and do not attempt generation as a fallback.
Prefer a forwarded/canvas URL over localhost when the user may be on SSH, IM, or another remote device.
When launched from the unified PPT flow, use the exact absolute
Treat task_pack.json as progress/resume state and outline.md as the

What it can do on your machine

Read from SKILL.md and the folder at commit 7838651. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript and Python, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
- python3
- node
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- API_SERVER_KEY
- WORKBENCH_GATEWAY_API_KEY
- HERMES_SESSION_KEY
- WORKBENCH_AGENT_API_KEY
- HERMES_GATEWAY_API_KEY
- AI_GATEWAY_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

SenseNova PPT Workbench loads about 2.5k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 1,008 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~54
When it runs · the whole SKILL.md, loaded when a task matches: ~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:75

and key resolve (environment or Hermes `.env` files),

NoteMentions a .env fileSKILL.md:203

| `API_SERVER_KEY` | Gateway (.env) | Shared secret |

NoteMentions a .env fileSKILL.md:214

- Gateway: set `API_SERVER_KEY` in `.env`, restart gateway

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from OpenSenseNova/SenseNova-Skills at commit 7838651, republished under its MIT licence (© OpenSenseNova). 1,008 words, ~2,514 tokens.

Download SKILL.mdSave it as .claude/skills/sn-ppt-workbench/SKILL.md (or your agent's skills folder). This skill also uses 27 other files; get the full folder from GitHub.

name: sn-ppt-workbench
description: Use when the user asks to open, preview, inspect, or visually edit an existing SenseNova HTML presentation in the PPT Workbench, using an explicit deck_dir or the latest deck in the current workspace.
metadata.project: SenseNova-Skills
metadata.tier: aux
metadata.category: ppt
metadata.user_visible: true

sn-ppt-workbench

Start or reuse the AI PPT editing WebUI for an existing HTML slide deck. The helper prefers Hermes/canvas/port-forward URLs when available. Without a forwarded URL, native hosts bind to localhost by default, while Docker/WSL bind to 0.0.0.0 so remote users can reach the WebUI through the host network.

Use Cases

The user already generated a deck and asks to open the WebUI/editor/workbench.
The user provides a deck_dir containing task_pack.json, slides/slide_NN.html, pages/page_NNN.html, or a root-level HTML deck.
The user says to inspect or edit previously generated slides without regenerating them.

Hard Rules

Do not run sn-ppt-entry, sn-ppt-standard, page-html, batch-page-html, or export.
Do not edit slide files directly. The WebUI handles user-visible editing.
If deck_dir is missing, auto-detect only under $(pwd)/ppt_decks. Other roots are considered only when the caller explicitly passes --search-root; never scan home folders by default.
If no usable deck is found, ask the user for the absolute deck_dir.
Workbench startup is best-effort. If it skips or fails, report the reason and do not attempt generation as a fallback.
Prefer a forwarded/canvas URL over localhost when the user may be on SSH, IM, or another remote device.
When launched from the unified PPT flow, use the exact absolute task_pack.deck_dir; opening the Workbench must not create or switch tasks.
Treat task_pack.json as progress/resume state and outline.md as the user-editable Story. Existing runtime builds may expose only part of these artifacts; report compatibility gaps instead of regenerating the deck.

Invocation

Use the helper directly:

bash

python3 $SKILL_DIR/scripts/open_workbench.py --deck-dir "<deck_dir>" --agent-session-id "${HERMES_SESSION_KEY:-}"

On native Windows where python3 is unavailable:

bash

python $SKILL_DIR/scripts/open_workbench.py --deck-dir "<deck_dir>" --agent-session-id "%HERMES_SESSION_KEY%"

If the user did not provide a deck path, let the helper auto-detect:

bash

python3 $SKILL_DIR/scripts/open_workbench.py --agent-session-id "${HERMES_SESSION_KEY:-}"

Pass same-session bridge details when available:

bash

python3 $SKILL_DIR/scripts/open_workbench.py \
  --deck-dir "<deck_dir>" \
  --agent-session-id "${HERMES_SESSION_KEY:-}" \
  --agent-managed 1 \
  --agent-provider hermes \
  --agent-transport gateway \
  --webui-base-url "${HERMES_WEBUI_BASE_URL:-}" \
  --gateway-base-url "${HERMES_GATEWAY_BASE_URL:-}"

--agent-transport may be omitted: the helper auto-selects gateway when the Hermes Gateway endpoint and key resolve (environment or Hermes .env files), then webui / acp / rest when only those details exist. Explicit flags and WORKBENCH_AGENT_TRANSPORT always win. With no resolvable bridge the bottom chat stays read-only by design.

For non-Hermes interactive providers, pass structured bridge details instead of scraping CLI/TUI output:

bash

python3 $SKILL_DIR/scripts/open_workbench.py \
  --deck-dir "<deck_dir>" \
  --agent-managed 1 \
  --agent-provider openclaw \
  --agent-transport rest \
  --agent-base-url "${WORKBENCH_AGENT_BASE_URL:-}" \
  --agent-api-key "${WORKBENCH_AGENT_API_KEY:-}"

python3 $SKILL_DIR/scripts/open_workbench.py \
  --deck-dir "<deck_dir>" \
  --agent-managed 1 \
  --agent-provider codex \
  --agent-transport acp \
  --acp-command "${WORKBENCH_ACP_COMMAND:-codex-acp}"

python3 $SKILL_DIR/scripts/open_workbench.py \
  --deck-dir "<deck_dir>" \
  --agent-managed 1 \
  --agent-provider box-agent \
  --agent-transport acp \
  --acp-command "${WORKBENCH_ACP_COMMAND:-${BOX_AGENT_ACP_COMMAND:-box-agent-acp}}"

When this helper runs inside Box Agent, the exported BOX_AGENT_PYTHON or BOX_AGENT_SKILL_TOOLS_ROOT environment automatically selects box-agent, acp, and the installed box-agent-acp command. Explicit WORKBENCH_AGENT_* flags or environment variables still take precedence.

For WorkBuddy, pass --agent-provider workbuddy only as provider identity. Tell the user clearly that WorkBuddy currently has no supported API or ACP interface for the interactive workbench bridge, so the WebUI can show WorkBuddy status but cannot send bottom-chat modification turns back to WorkBuddy.

CLI Subcommands (direct launch fallback)

When bypassing open_workbench.py and invoking the workbench launcher directly, use subcommands:

bash

node <launcher> start   --deck-dir "<path>" [--port 0] [--agent-managed]
node <launcher> status  --deck-dir "<path>"
node <launcher> stop    --deck-dir "<path>"

The old argument-only form (no subcommand) is deprecated — it will print a usage error.

Restart pitfall: start silently reuses an existing server instance for the same deck-dir (response contains "reused": true). If you updated the workbench code, you MUST run stop first, then start — otherwise the old process keeps serving stale code:

bash

node <launcher> stop  --deck-dir "<path>"
node <launcher> start --deck-dir "<path>" --port 0

Bind Host

The workbench resolves its bind address from --host CLI flag → WORKBENCH_HOST env var → default 127.0.0.1. When the user needs remote/LAN access, set WORKBENCH_HOST=0.0.0.0:

bash

export WORKBENCH_HOST=0.0.0.0
node <launcher> start --deck-dir "<path>" --port 0

The response url field will then show the LAN IP instead of 127.0.0.1.

Output Handling

Parse the single JSON line from stdout.

When status == "ok", echo the returned editor_url, public_url, or workbench.editorUrl for existing-deck editing requests. The helper may also return generation_url; that URL is the generation progress page at /progress, while the editor is /editor.

text

PPT 编辑工作台已启动：<editor_url>

If workbench.reused == true, say it reused the existing server.

If bind_host is 0.0.0.0, the URL is a Docker/WSL LAN fallback. Tell the user it must be reachable from their device/network; if not, ask them to provide a Hermes/canvas/port-forward URL and rerun with --public-url, or an explicit bind host with --host.

When status == "skipped" or status == "failed", echo the reason field. If reason == "nodejs_missing", ask whether the user wants NodeJS/dependencies installed; if they decline, do not open the WebUI. Ask for a valid deck_dir only if the reason says no deck was found.

Show full SKILL.md (355 more words)Show less

Environment

The helper locates the editor launcher in this order:

SENSENOVA_PPT_WORKBENCH_CLI
PPT_WORKBENCH_CLI
The runtime packaged beside this Skill
The nearest src/ppt-editor source checkout or packaged release in the current worktree
Common ~/Repository/ppt-editor fallbacks

The helper does not build the editor during an end-user launch. Packaged Skills must include workbench-runtime; source checkouts must build src/ppt-editor explicitly before using its launcher. The repository-level webui/ directory is a separate product and is not a launcher fallback for this Skill.

Remote URL discovery order:

Explicit --public-url
WORKBENCH_PUBLIC_URL, HERMES_WORKBENCH_PUBLIC_URL
Hermes/canvas/forwarding env vars such as HERMES_CANVAS_URL, HERMES_PORT_FORWARD_URL, CANVAS_URL, PORT_FORWARD_URL, TUNNEL_URL
Codespaces/Gitpod URL patterns
Localhost on native hosts, or LAN fallback from the machine's non-loopback IPv4 address on Docker/WSL

Gateway Auth Setup

For writable interactive agent bridging (chat panel in workbench), Hermes keeps using the existing WebUI/Gateway protocol. OpenClaw should be exposed through a Gateway/REST-compatible HTTP endpoint. Codex, Claude Code, and Box Agent should use ACP JSON-RPC adapters, configured with --acp-command or WORKBENCH_ACP_COMMAND. Box Agent defaults to its installed box-agent-acp entry point. Never parse provider CLI/TUI output for chat synchronization.

For writable Hermes Gateway bridging, the Gateway API server and workbench must authenticate with matching API keys.

Key env vars:

Variable	Set By	Value
`API_SERVER_KEY`	Gateway (.env)	Shared secret
`WORKBENCH_GATEWAY_API_KEY`	Workbench env	Same as `API_SERVER_KEY`; preferred explicit bridge key
`HERMES_GATEWAY_BASE_URL`	Workbench env	`http://127.0.0.1:8642`
`WORKBENCH_AGENT_PROVIDER`	Workbench env	`hermes`, `openclaw`, `codex`, `claude-code`, `box-agent`, or `workbuddy`
`WORKBENCH_AGENT_TRANSPORT`	Workbench env	`webui`, `gateway`, `rest`, or `acp`
`WORKBENCH_AGENT_BASE_URL`	Workbench env	OpenClaw/Gateway REST endpoint
`WORKBENCH_AGENT_API_KEY`	Workbench env	REST provider bearer token
`WORKBENCH_ACP_COMMAND`	Workbench env	ACP adapter command, e.g. `codex-acp`
`BOX_AGENT_ACP_COMMAND`	Box Agent / Workbench env	Optional override for the default `box-agent-acp` adapter command

Quick steps:

Gateway: set API_SERVER_KEY in .env, restart gateway
Workbench: set WORKBENCH_GATEWAY_API_KEY to same value, set HERMES_GATEWAY_BASE_URL=http://127.0.0.1:8642
If no explicit bridge key is set, the Node relay falls back to API_SERVER_KEY, HERMES_GATEWAY_API_KEY, then backend-only AI_GATEWAY_API_KEY (ppt-editor-dev by default). Prefer the explicit bridge key for custom/shared gateways.

Progress Echo

Always send a short progress message before and after the helper:

When	Example
Before helper	`正在启动 PPT 预览工作台，不会重新生成幻灯片...`
Success	`PPT 编辑工作台已启动：http://127.0.0.1:18087`
Generation progress URL available	`生成进度工作台：http://127.0.0.1:18087/progress`
Skip/failure	`PPT 工作台未启动：<reason>`

Files

SKILL.md and 27 other files (scripts, references) in skills/sn-ppt-workbench of OpenSenseNova/SenseNova-Skills.

SKILL.md
references/gateway-auth.md
scripts/open_workbench.py
workbench-runtime/bin/sensenova-ppt-workbench.mjs
workbench-runtime/dist-server/index.mjs
workbench-runtime/dist/assets/MarkdownArtifactViewer-DxLTmGwT.js
workbench-runtime/dist/assets/index-DZ8oHsQz.js
workbench-runtime/dist/assets/index-Hn-wCKPf.css
workbench-runtime/dist/favicon.svg
workbench-runtime/dist/index.html
workbench-runtime/dist/sensetime-mark.png
workbench-runtime/examples/sensenova-basic/asset_plan.json
… and 16 more

Open the folder on GitHubat commit 7838651

Compare with similar skills

SenseNova PPT Workbench next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

SenseNova PPT Workbench compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
SenseNova PPT Workbench this skillOpenSenseNova/SenseNova-Skills	5.7k	—	~2.5k	Automated safety check: Notes	MIT	today
Frontend Slideszarazhangrui/frontend-slides	30k	16 repos	~7k	Automated safety check: Pass	MIT	3 mo ago
HTML PPT Studiolewislulu/html-ppt-skill	8.6k	4 repos	~4.7k	Automated safety check: Pass	MIT	25 days ago
PPT Masterhugohe3/ppt-master	58k	1 repos	~2.5k	Automated safety check: Pass	MIT	yesterday
PowerPoint Decksanthropics/skills	180k	5 repos	~5.2k	Automated safety check: Pass	Proprietary	today
Single-File HTML Slide Decksop7418/guizang-ppt-skill	27k	1 repos	~6.3k	Automated safety check: Pass	AGPL-3.0	2 mo ago

Similar skills

Frontend Slides
zarazhangrui/frontend-slides
Builds animated HTML slide decks that run in the browser with no dependencies, or converts PowerPoint files to the web, starting from visual style previews.
30k GitHub starsUsed in 16 repos~7k tokens
Documents & OfficeAuto-check passed
HTML PPT Studio
lewislulu/html-ppt-skill
Authors static HTML presentations from a library of themes, layouts and animations, with keyboard navigation, for talks, pitch decks and reports.
8.6k GitHub starsUsed in 4 repos~4.7k tokens
Documents & OfficeAuto-check passed
PPT Master
hugohe3/ppt-master
Generates editable PowerPoint decks, rebuilds slides from images, fills .pptx templates and polishes existing presentations through routed workflows.
58k GitHub starsUsed in 1 repo~2.5k tokens
Documents & OfficeAuto-check passed
PowerPoint Decks
anthropics/skills
Official
Creates, edits, reads and validates .pptx and .potx files, using pptxgenjs for new decks and direct XML edits for existing ones, with helper scripts for thumbnails and checks.
180k GitHub starsUsed in 5 repos~5.2k tokens
Documents & OfficeAuto-check passed
Single-File HTML Slide Decks
op7418/guizang-ppt-skill
Generates single-file HTML slide decks with horizontal paging, WebGL backgrounds and a presenter view, in an editorial-magazine style or a Swiss-style layout.
27k GitHub starsUsed in 1 repo~6.3k tokens
Documents & OfficeAuto-check passed
PPTX
rvdbreemen/OTGW-firmware
Use this skill any time a .pptx file is involved in any way — as input, output, or both.
207 GitHub starsUsed in 34 repos~2.3k tokens
Documents & OfficeAuto-check passed

More from OpenSenseNova/SenseNova-Skills

All 36 skills in this repo

SN Motion HTML
OpenSenseNova/SenseNova-Skills
Builds HTML stories where one continuous camera journey advances with page progress, using researched structure, AI stills, Seedance video clips and browser QA.
5.7k GitHub stars~2.2k tokensUpdated today
Auto-check: notes
SenseNova PPT Fallback Tools
OpenSenseNova/SenseNova-Skills
Fallback scripts for web search, image search and download, and image generation that PPT skills use only when the host agent lacks or fails its own tools.
5.7k GitHub stars~575 tokensUpdated today
Auto-check: notes
SenseNova PPT Creative Renderer
OpenSenseNova/SenseNova-Skills
Turns an approved slide outline into a full-page image for every slide, one 16:9 PNG per page, and optionally packages the set into a PPTX.
5.7k GitHub stars~1.2k tokensUpdated today
Auto-check passed
SenseNova PPT Entry
OpenSenseNova/SenseNova-Skills
Entry point for SenseNova presentation generation: creates a task folder, picks depth, output format and design richness, and routes to the right PPT skill.
5.7k GitHub stars~2.7k tokensUpdated today
Auto-check: notes
China Market Open Data Search
OpenSenseNova/SenseNova-Skills
Researches Chinese market, macro, trade, procurement, listed-company and regulatory information from free official sources that need no sign-up or API key.
5.7k GitHub stars~954 tokensUpdated today
Auto-check: notes
SenseNova Image Base Tools
OpenSenseNova/SenseNova-Skills
Low-level SenseNova tools for image generation, image editing, image recognition with a VLM and text optimization with an LLM, meant to be called by higher-level skills rather than directly.
5.7k GitHub stars~3.2k tokensUpdated today
Auto-check passed

Questions about SenseNova PPT Workbench

What does SenseNova PPT Workbench do?

Opens the PPT Workbench web editor for an existing SenseNova HTML slide deck so you can preview, inspect and visually edit it without regenerating. py with a deck folder or, if none is given, auto-detecting the latest deck under ppt_decks in the current workspace.json, per-slide or per-page HTML files, or a root-level HTML deck.

When should I use SenseNova PPT Workbench?

SenseNova PPT Workbench fits situations like: opening a previously generated SenseNova slide deck in the visual editor; inspecting or previewing slides without regenerating them; locating the most recent deck in the current workspace and opening it.

How do I install SenseNova PPT Workbench in Claude Code?

Run `npx skills add OpenSenseNova/SenseNova-Skills --skill sn-ppt-workbench -a claude-code`. Or copy the skill folder (skills/sn-ppt-workbench in OpenSenseNova/SenseNova-Skills) into .claude/skills/sn-ppt-workbench in your project. Claude Code loads it when a task matches its description.

How do I install SenseNova PPT Workbench in Codex?

Run `npx skills add OpenSenseNova/SenseNova-Skills --skill sn-ppt-workbench -a codex`. Or copy the skill folder (skills/sn-ppt-workbench in OpenSenseNova/SenseNova-Skills) into .agents/skills/sn-ppt-workbench in your project. Codex loads it when a task matches its description.

Can I use SenseNova PPT Workbench in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenSenseNova/SenseNova-Skills --skill sn-ppt-workbench -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sn-ppt-workbench, .gemini/skills/sn-ppt-workbench, .github/skills/sn-ppt-workbench and .opencode/skills/sn-ppt-workbench in your project.

What does SenseNova PPT Workbench need to run?

Going by SKILL.md and its folder, SenseNova PPT Workbench needs JavaScript and Python for the scripts in its folder, the command-line tools its instructions call (python3, node and python) and credentials named API_SERVER_KEY, WORKBENCH_GATEWAY_API_KEY, HERMES_SESSION_KEY and WORKBENCH_AGENT_API_KEY. Our summary lists: Python 3 to run the helper script; A generated SenseNova HTML deck folder.

Does SenseNova PPT Workbench access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is SenseNova PPT Workbench safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does SenseNova PPT Workbench use?

SenseNova PPT Workbench is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does SenseNova PPT Workbench use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to SenseNova PPT Workbench?

Skills that share tags, products or a category with SenseNova PPT Workbench: Frontend Slides (zarazhangrui/frontend-slides, 30k stars), HTML PPT Studio (lewislulu/html-ppt-skill, 8.6k stars), PPT Master (hugohe3/ppt-master, 58k stars) and PowerPoint Decks (anthropics/skills, 180k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SenseNova PPT Workbench?

OpenSenseNova (a GitHub organization) maintains it in OpenSenseNova/SenseNova-Skills, which has 5,747 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 9, 2026.

Source: OpenSenseNova/SenseNova-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install SenseNova PPT Workbench

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

sn-ppt-workbench

Use Cases

Hard Rules

Invocation

CLI Subcommands (direct launch fallback)

Bind Host

Output Handling

Environment

Gateway Auth Setup

Progress Echo

Files

Compare with similar skills

Similar skills

More from OpenSenseNova/SenseNova-Skills

Related

Questions about SenseNova PPT Workbench