Sap Extension Creator
Create Super Agent Party (SAP) extensions.
Install
npx skills add heshengtao/super-agent-party --skill sap-extension-creator -g -a claude-code -y- Repository
- heshengtao/super-agent-party2.8k
- Category
- Design
- Updated
- 9d ago
- License
- AGPL-3.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Create Super Agent Party (SAP) extensions. This skill should be used when users want to create, build, or scaffold a new extension for Super Agent Party - including static HTML extensions (pure frontend) and Node.js backend extensions. Triggers on requests like "create a new SAP extension", "build an extension for Super Agent Party", "scaffold a plugin", "make a chat UI extension", or when working with sap extension projects.
SAP Extension Creator
Overview
Create Super Agent Party extensions, self-contained packages that extend the platform with custom chat UI and tools. Two modes are supported:
- Static extension: Pure HTML/CSS/JS frontend, served directly by SAP from the extension folder
- Node.js extension: Full-stack with Express backend, auto-managed by SAP (
npm install+node index.js <port>)
Both modes support MCP tool registration (the register_node_extension_mcp protocol message works for ANY extension via WebSocket, despite the "node" in its name).
Quick Decision Tree
User wants to create an extension?
├─ Only needs UI (chat, display, simple interactions)? → Static Extension
└─ Needs backend logic (API calls, DB, file processing)? → Node.js Extension
Core Files Every Extension Needs
| File | Required | Purpose |
|---|---|---|
package.json | ✅ | Metadata, dependencies, window config |
index.html | ✅ | Main UI (full HTML page, single-file app) |
index.js | Node only | Node.js entry point |
node_modules/ | Node only | Auto-installed by SAP via npm install |
Workflow
Step 1: Gather Requirements
Ask the user:
- Extension name? (hyphen-case, e.g.,
my-weather-widget) - Description? (one sentence)
- Static or Node.js? (Node.js only if backend logic/server-side code is needed)
- For Node.js: what npm dependencies?
- Should it register custom tools for the AI? (works in both static and Node.js modes via WebSocket MCP)
- GitHub repository URL? (optional, for updates)
- Transparent window? (frameless, always-on-top, for mini widgets like music controllers)
- Default window size? (width/height in pixels)
Step 2: Scaffold the Extension
Use the templates in assets/ as starting points:
- Static: Copy
assets/static-template/ - Node.js: Copy
assets/node-template/
