Hexabot Action Creator — build and review Hexabot v3 actions (short listing)
Short listing — license not verifiable: create, scaffold, implement, review, and document Hexabot v3 workflow actions — custom API integrations, LLM-powered actions, memory reads/writes, safe credential handling, action bindings, and plugin packages
- What
- Short listing — license not verifiable: create, scaffold, implement, review, and document Hexabot v3 workflow actions — custom API integrations, LLM-powered actions, memory reads/writes, safe credential handling, action bindings, and plugin packages
- Cost
- Free
- Needs
- an active Hexabot v3 project (monorepo, a hexabot-action-* package, or a @hexabot-ai/agentic app) to verify generated actions against; Node.js with TypeScript and NestJS familiarity
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the discovery manifest carries no verifiable license for this skill — the manifest makes faith, so no content is reproduced): @hexabot-ai's hexabot-action-creator skill, the action-authoring companion for the open-source Hexabot v3 chatbot platform. It teaches the agent to wrap business requirements as Hexabot actions: identify the capability, side effects, and target (Hexabot monorepo, custom action package, or standalone runtime); inspect the active project's real files as source of truth before final code; choose the right pattern (createAction for simple discovered actions, BaseAction for injected services, defineAction for standalone agentic examples); design the input/output/settings contract with idempotency, failure behavior, and logging; implement with Zod schemas and safe credential handling; and produce review findings ordered by severity. It ships bundled references (action-authoring guide, contract guide, settings-and-secrets guide, testing checklist) and a CRM-ticket action example. Honest caveats: license terms not verifiable — short listing with a link only, nothing copied; requires an actual Hexabot project or action package — runtime verification can't be done from the skill bundle alone; follow the source link and read the terms yourself before use. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: an active Hexabot v3 project (monorepo, a hexabot-action-* package, or a @hexabot-ai/agentic app) to verify generated actions against; Node.js with TypeScript and NestJS familiarity Install "Hexabot Action Creator — build and review Hexabot v3 actions (short listing)" for me. It gives my agent @hexabot-ai's action-authoring workflow: inspect the active Hexabot project files as source of truth, choose the right action pattern (createAction, BaseAction, or defineAction), design the input/output/settings contract with idempotency and failure behavior, implement with Zod schemas and safe credential handling, and run review checklists ordered by severity — with bundled references (authoring guide, contract guide, settings-and-secrets guide, testing checklist). IMPORTANT: the license terms were not verifiable (the discovery manifest records no license) — fetch from the link only, reproduce nothing beyond the link, and read the terms yourself before use. Repository: https://github.com/hexabot-ai/action-creator/blob/main/skills/hexabot-action-creator/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code — credentials only via my Hexabot project's vault/settings, never echoed or pasted. Verify that holds; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "hexabot-action-creator". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my Hexabot project or action package so runtime facts can be verified; confirm the target action capability and side effects). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.