@beehexa/hexasync-ai-toolkit
HexaSync AI toolkit: agent skills for HexaSync profile templates plus the HexaSync Template IDE MCP server, installable into Claude Code, Codex, Cursor, Antigravity, pi, OpenClaw and VS Code.
Package details
Install @beehexa/hexasync-ai-toolkit from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@beehexa/hexasync-ai-toolkit- Package
@beehexa/hexasync-ai-toolkit- Version
2611.8.3- Published
- Nov 7, 2026
- Downloads
- 916/mo · 234/wk
- Author
- beehexa-corp
- License
- MIT
- Types
- skill
- Size
- 2.3 MB
- Dependencies
- 0 dependencies · 0 peers
Pi manifest JSON
{
"skills": [
"./skills"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
@beehexa/hexasync-ai-toolkit
Teach your AI coding agent HexaSync profile templates. One command installs:
- The HexaSync Template IDE MCP server: the official knowledge base, 1,000+ YAML examples and project validation, as tools your agent can call.
- 16 HexaSync agent skills: templates in general, pullers, pushers, webhooks, API steps, control and data steps, the Query DSL, expressions, transformations, validations, connections, tables and tasks, startup tasks and scheduling, metrics and reports, error handling and field mapping. Entry/API/control/expression skills route grouped frontend requests to the same KB-owned frontend reference, not a second authored grammar.
Supported agents: Claude Code, Codex, Cursor, Antigravity, pi, OpenClaw and VS Code (GitHub Copilot). Works on Linux, macOS and Windows.
Prerequisites
Node.js 22.13 or newer (node --version).
Choose an exact toolkit release and replace <toolkit-version> below. The installer, generated manifests
and skill installation references select the standalone MCP server at that same version, never a moving
release or an automatic fallback. If the matching server is unpublished/missing, registry-backed activation
is blocked; do not substitute another version or publish automatically.
Install
npx -y '@beehexa/hexasync-ai-toolkit@<toolkit-version>' install --client all
Then restart your agent. Skills load conditionally when the host selects them; installation does not inject instructions globally or prove that a skill has loaded.
| Option | Effect |
|---|---|
--client claude,codex,cursor,antigravity,pi,openclaw,vscode |
only these agents (default: all) |
--scope user / --scope project |
your user profile (default) or the current project |
--skills-only / --mcp-only |
install only one of the two |
--dry-run |
show what would change, write nothing |
Your existing agent configuration is kept, and a backup is written before a file is changed. In a VS Code that already has the HexaSync Template IDE extension, only the skills are added, because the extension provides the server.
Update, list, remove
npx -y '@beehexa/hexasync-ai-toolkit@<toolkit-version>' update
npx -y '@beehexa/hexasync-ai-toolkit@<toolkit-version>' list
npx -y '@beehexa/hexasync-ai-toolkit@<toolkit-version>' uninstall
Install as a plugin
- pi:
pi install 'npm:@beehexa/hexasync-ai-toolkit@<toolkit-version>' - OpenClaw:
openclaw plugins install 'npm:@beehexa/hexasync-ai-toolkit@<toolkit-version>'
Try these prompts
- "How do I configure
wherein a Query DSL step? Show a full example." - "Write a puller that pulls a paged REST endpoint incrementally and saves each field to a snake_case column."
- "Handle HTTP and response errors in this puller with one classification step and an Error step."
- "Which roots can I use in an expression inside a pusher step?"
- "Validate this project and explain each problem."
- "Explain grouped getReadyFlows with runtime frontend and the frontend-step expression position."
The entry, API, control/data and expression skills link the
canonical frontend guide
through their localized references.
They qualify frontend type lookups with runtime: 'frontend'; omitted runtime remains worker.
Use frontend-step for frontend expressions. Missing frontend knowledge is unavailable, not a worker
fallback. Refer to the KB for the complete contract and runtime prerequisites; schema acceptance is not
deployed-runtime support or router/provider/user-receipt proof.
Troubleshooting
- The agent ignores HexaSync: restart it, then ask explicitly, e.g. "use hexasync-template-ide to explain…".
- The server does not start: check Node.js is 22.13 or newer.
- "No project" when validating: open the template folder in your agent, or re-run with
--scope projectfrom that folder. - Missing matching MCP release: activation is blocked. Local verification uses the actual installed
VSIX's
dist/mcp/server.jswithout fetching from the registry. A generated manifest or matching version alone is not installed-tool or skill-loading proof.