hexabot-ai/action-creator

Use this skill for Hexabot v3 action work. Hexabot action APIs are project-defined and can evolve, so inspect the user's active Hexabot repo, custom action package, or installed package types before producing final code.

Source of truth

Before final action code or review findings, inspect the relevant current project files. If the workspace is only this packaged skill, use the bundled references and examples, then state that runtime verification still needs a Hexabot project or action package.

When the user is working inside the Hexabot monorepo, these are the usual landmarks:

• API action surface: packages/api/src/actions/**.
• Built-in API action examples: packages/api/src/extensions/actions/**.
• Runtime binding system: packages/api/src/bindings/** and action binding files under packages/api/src/extensions/actions/**/*.binding.ts.
• Workflow runtime context and services: packages/api/src/workflow/contexts/**.
• Agentic action base: packages/agentic/src/action/**, packages/agentic/src/dsl.types.ts, and packages/agentic/README.md.
• Extension discovery: packages/api/src/actions/actions.module.ts, packages/api/src/bindings/bindings.module.ts, and packages/api/README.md.

When the user is working in a separate hexabot-action-* package or application repo, inspect that package's package.json, source tree, generated templates, TypeScript path aliases, and dependency exports instead of assuming monorepo packages/* paths exist.