ToolJet Marketplace Plugin Builder
ToolJet/ToolJet
Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.
Operate WhatsApp Business Platform Cloud API through UXC with a curated OpenAPI schema, bearer-token auth, and message/profile guardrails.
Install Whatsapp Openapi Skill
$ npx skills add holon-run/uxc --skill whatsapp-openapi-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install holon-run/uxc whatsapp-openapi-skill --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/whatsapp-openapi-skill .claude/skills/whatsapp-openapi-skill && rm -rf skills-srcUse ~/.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/
Install the "whatsapp-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/whatsapp-openapi-skill into .claude/skills/whatsapp-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsapp-openapi-skill", 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 install https://github.com/holon-run/uxc/tree/main/skills/whatsapp-openapi-skillType 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.
$ npx skills add holon-run/uxc --skill whatsapp-openapi-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install holon-run/uxc whatsapp-openapi-skill --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/whatsapp-openapi-skill .agents/skills/whatsapp-openapi-skill && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "whatsapp-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/whatsapp-openapi-skill into .agents/skills/whatsapp-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsapp-openapi-skill", 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.
$ npx skills add holon-run/uxc --skill whatsapp-openapi-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install holon-run/uxc whatsapp-openapi-skill --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/whatsapp-openapi-skill .cursor/skills/whatsapp-openapi-skill && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "whatsapp-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/whatsapp-openapi-skill into .cursor/skills/whatsapp-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsapp-openapi-skill", 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 https://github.com/holon-run/uxc.git --path skills/whatsapp-openapi-skill--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add holon-run/uxc --skill whatsapp-openapi-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install holon-run/uxc whatsapp-openapi-skill --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/whatsapp-openapi-skill .gemini/skills/whatsapp-openapi-skill && rm -rf skills-srcUse ~/.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/
Install the "whatsapp-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/whatsapp-openapi-skill into .gemini/skills/whatsapp-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsapp-openapi-skill", 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.
$ gh skill install holon-run/uxc whatsapp-openapi-skillInstalls 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).
$ npx skills add holon-run/uxc --skill whatsapp-openapi-skill -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/whatsapp-openapi-skill .github/skills/whatsapp-openapi-skill && rm -rf skills-srcUse ~/.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/
Install the "whatsapp-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/whatsapp-openapi-skill into .github/skills/whatsapp-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsapp-openapi-skill", 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.
$ npx skills add holon-run/uxc --skill whatsapp-openapi-skill -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install holon-run/uxc whatsapp-openapi-skill --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/whatsapp-openapi-skill .opencode/skills/whatsapp-openapi-skill && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "whatsapp-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/whatsapp-openapi-skill into .opencode/skills/whatsapp-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsapp-openapi-skill", 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
whatsapp-openapi-skill- GitHub stars
- 116
- Token cost
- ~1.3k tokens
- SKILL.md length
- 445 words
- Files
- 5 (incl. scripts, references)
- Skills in repo
- 62
- Repo updated
- First seen
- Licence
- MIT
At a glance
Operate WhatsApp Business Platform Cloud API through UXC with a curated OpenAPI schema, bearer-token auth, and message/profile guardrails.
- Works in 4 steps: Use the fixed link command by default → Inspect operation schema first → Prefer read/setup validation before writes → …
- Tasks that involve OpenAPI specifications
- SKILL.md covers Prerequisites, Scope, API Version and Authentication, plus 4 more sections
- Runs Shell scripts from its folder; reaches graph.facebook.com; needs WHATSAPP_CLOUD_ACCESS_TOKEN
What it does
Whatsapp Openapi Skill is an agent skill from holon-run/uxc. Operate WhatsApp Business Platform Cloud API through UXC with a curated OpenAPI schema, bearer-token auth, and message/profile guardrails.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/usage-patterns.md` and `references/whatsapp-cloud.openapi.json`).
It sits in Backend & APIs, covering OpenAPI specifications. It works with WhatsApp and OpenAPI. The repository describes itself as: A unified CLI for discovering and invoking tools across OpenAPI, MCP, GraphQL, gRPC, and JSON-RPC. The licence is MIT.
When your agent uses it
- Tasks that involve OpenAPI specifications
Example prompts
- “/whatsapp-openapi-skill”
Requirements
- A Bash shell
- A credential in WHATSAPP_CLOUD_ACCESS_TOKEN
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Use the fixed link command by default
- Inspect operation schema first
- Prefer read/setup validation before writes
- Execute with key/value or positional JSON
What it can do on your machine
Read from SKILL.md and the folder at commit 562d47c. 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/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
graph.facebook.com
Also links to:
developers.facebook.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
WHATSAPP_CLOUD_ACCESS_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Whatsapp Openapi Skill loads about 1.3k tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 40 tokens; SKILL.md has 445 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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 holon-run/uxc at commit 562d47c, republished under its MIT licence (© holon-run). 445 words, ~1,300 tokens.
Download SKILL.mdSave it as
.claude/skills/whatsapp-openapi-skill/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- whatsapp-openapi-skill
- description
- Operate WhatsApp Business Platform Cloud API through UXC with a curated OpenAPI schema, bearer-token auth, and message/profile guardrails.
WhatsApp Cloud API Skill
Use this skill to run WhatsApp Business Platform Cloud API operations through uxc + OpenAPI.
Reuse the uxc skill for shared execution, auth, and error-handling guidance.
Prerequisites
uxcis installed and available inPATH.- Network access to
https://graph.facebook.com/v25.0. - Access to the curated OpenAPI schema URL:
https://raw.githubusercontent.com/holon-run/uxc/main/skills/whatsapp-openapi-skill/references/whatsapp-cloud.openapi.json
- A Meta app and WhatsApp Business account with Cloud API access.
- A valid system-user or app access token that can call the target WhatsApp assets.
- At least one
phone_number_id, and for phone number listing, the relatedwaba_id.
Scope
This skill covers a compact Cloud API request/response surface:
- phone number listing
- phone number metadata reads
- business profile reads and updates
- outbound message sends
This skill does not cover:
- inbound webhook receiver runtime
- template lifecycle management
- embedded signup or broader business onboarding flows
- media upload/download lifecycle
- the full WhatsApp Business Platform surface
API Version
This skill is pinned to Graph API v25.0, based on current Meta developer examples at implementation time. Keep the base URL versioned:
https://graph.facebook.com/v25.0
If Meta deprecates this version later, the wrapper should be revised in a follow-up update rather than assuming unversioned compatibility.
Authentication
WhatsApp Cloud API uses Authorization: Bearer <access_token>.
Configure one bearer credential and bind it to the versioned Graph API base path:
uxc auth credential set whatsapp-cloud \
--auth-type bearer \
--secret-env WHATSAPP_CLOUD_ACCESS_TOKEN
uxc auth binding add \
--id whatsapp-cloud \
--host graph.facebook.com \
--path-prefix /v25.0 \
--scheme https \
--credential whatsapp-cloud \
--priority 100Validate the active mapping when auth looks wrong:
uxc auth binding match https://graph.facebook.com/v25.0Core Workflow
Use the fixed link command by default:
command -v whatsapp-openapi-cli- If missing, create it:
uxc link whatsapp-openapi-cli https://graph.facebook.com/v25.0 --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/whatsapp-openapi-skill/references/whatsapp-cloud.openapi.json whatsapp-openapi-cli -h
Inspect operation schema first:
whatsapp-openapi-cli get:/{waba_id}/phone_numbers -hwhatsapp-openapi-cli get:/{phone_number_id}/whatsapp_business_profile -hwhatsapp-openapi-cli post:/{phone_number_id}/messages -h
Prefer read/setup validation before writes:
whatsapp-openapi-cli get:/{waba_id}/phone_numbers waba_id=123456789012345whatsapp-openapi-cli get:/{phone_number_id} phone_number_id=123456789012345whatsapp-openapi-cli get:/{phone_number_id}/whatsapp_business_profile phone_number_id=123456789012345
Execute with key/value or positional JSON:
- key/value:
whatsapp-openapi-cli get:/{phone_number_id} phone_number_id=123456789012345 fields=display_phone_number,verified_name - positional JSON:
whatsapp-openapi-cli post:/{phone_number_id}/messages '{"phone_number_id":"123456789012345","messaging_product":"whatsapp","to":"15551234567","type":"text","text":{"body":"Hello from UXC"}}'
- key/value:
Show full SKILL.md (158 more words)Show less
Operation Groups
Asset Discovery
get:/{waba_id}/phone_numbersget:/{phone_number_id}
Business Profile
get:/{phone_number_id}/whatsapp_business_profilepost:/{phone_number_id}/whatsapp_business_profile
Messaging
post:/{phone_number_id}/messages
Guardrails
- Keep automation on the JSON output envelope; do not use
--text. - Parse stable fields first:
ok,kind,protocol,data,error. post:/{phone_number_id}/messagesis a high-risk write. Require explicit user confirmation before execution.- Message delivery is still constrained by WhatsApp conversation rules, template approval rules, recipient opt-in expectations, and account policy state. Auth success does not imply a send is allowed.
- This v1 skill does not manage media uploads. If you send
imageordocumentcontent, use already hosted URLs or existing asset references as allowed by the platform. - Webhook subscription and verification are intentionally documented only. This skill does not configure a receiver runtime.
- Business profile update fields are partial. Only send the fields you intend to change.
whatsapp-openapi-cli <operation> ...is equivalent touxc https://graph.facebook.com/v25.0 --schema-url <whatsapp_openapi_schema> <operation> ....
References
- Usage patterns:
references/usage-patterns.md - Curated OpenAPI schema:
references/whatsapp-cloud.openapi.json - WhatsApp Cloud API docs: https://developers.facebook.com/docs/whatsapp/cloud-api
- Graph API access tokens: https://developers.facebook.com/docs/graph-api/overview/access-tokens/
© holon-run, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references) in skills/whatsapp-openapi-skill of holon-run/uxc.
- SKILL.md
- agents/openai.yaml
- references/usage-patterns.md
- references/whatsapp-cloud.openapi.json
- scripts/validate.sh
Open the folder on GitHubat commit 562d47c
Compare with similar skills
Whatsapp Openapi Skill 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Whatsapp Openapi Skill this skillholon-run/uxc | 116 | — | ~1.3k | Automated safety check: Pass | MIT | |
| ToolJet Marketplace Plugin BuilderToolJet/ToolJet | 41k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Step Partsearthtojake/text-to-cad | 18k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| API DesignerJeffallan/claude-skills | 12k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Use Yaakmountain-loop/yaak | 19k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Step Parts
earthtojake/text-to-cad
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers…
API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
Old Coder API Design
AmazingAng/old-coder
Reviews or designs an HTTP/JSON API's endpoints, auth, pagination, versioning and deprecations, guarding against inventing a bespoke interface or silently breaking consumers.
More from holon-run/uxc
All 62 skills in this repoContext7 MCP Skill
holon-run/uxc
Query up-to-date library documentation and code examples using Context7 MCP.
Deepwiki MCP Skill
holon-run/uxc
Ask questions and read documentation about any GitHub repository using DeepWiki MCP.
Linear Graphql Skill
holon-run/uxc
Operate Linear workspace issues, projects, and teams through Linear GraphQL API using UXC.
Notion Openapi Skill
holon-run/uxc
Operate Notion Public API through UXC with a curated OpenAPI schema for search, block traversal, page reads, content writes, and data source/database inspection.
Alchemy Openapi Skill
holon-run/uxc
Operate Alchemy Prices API reads through UXC with a curated OpenAPI schema, path-templated API-key auth, and read-first guardrails.
Uxc
holon-run/uxc
Discover and call remote schema-exposed interfaces with UXC.
Related
Categories
Questions about Whatsapp Openapi Skill
What does Whatsapp Openapi Skill do?
Operate WhatsApp Business Platform Cloud API through UXC with a curated OpenAPI schema, bearer-token auth, and message/profile guardrails. Whatsapp Openapi Skill is an agent skill from holon-run/uxc. Operate WhatsApp Business Platform Cloud API through UXC with a curated OpenAPI schema, bearer-token auth, and message/profile guardrails.
When should I use Whatsapp Openapi Skill?
Whatsapp Openapi Skill fits situations like: tasks that involve OpenAPI specifications.
How do I install Whatsapp Openapi Skill in Claude Code?
Run `npx skills add holon-run/uxc --skill whatsapp-openapi-skill -a claude-code`. Or copy the skill folder (skills/whatsapp-openapi-skill in holon-run/uxc) into .claude/skills/whatsapp-openapi-skill in your project. Claude Code loads it when a task matches its description.
How do I install Whatsapp Openapi Skill in Codex?
Run `npx skills add holon-run/uxc --skill whatsapp-openapi-skill -a codex`. Or copy the skill folder (skills/whatsapp-openapi-skill in holon-run/uxc) into .agents/skills/whatsapp-openapi-skill in your project. Codex loads it when a task matches its description.
Can I use Whatsapp Openapi Skill 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 holon-run/uxc --skill whatsapp-openapi-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/whatsapp-openapi-skill, .gemini/skills/whatsapp-openapi-skill, .github/skills/whatsapp-openapi-skill and .opencode/skills/whatsapp-openapi-skill in your project.
What does Whatsapp Openapi Skill need to run?
Going by SKILL.md and its folder, Whatsapp Openapi Skill needs a shell for the scripts in its folder and credentials named WHATSAPP_CLOUD_ACCESS_TOKEN. Our summary lists: A Bash shell; A credential in WHATSAPP_CLOUD_ACCESS_TOKEN.
Does Whatsapp Openapi Skill access the network?
SKILL.md names 2 domains. In commands or code: graph.facebook.com; the agent is likely to contact it when it follows the instructions. As links in the text: developers.facebook.com. This is read from the text; nothing was executed.
Is Whatsapp Openapi Skill safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. 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 Whatsapp Openapi Skill use?
Whatsapp Openapi Skill 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 Whatsapp Openapi Skill use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 4.9k tokens, read only when the agent opens those files.
What are the alternatives to Whatsapp Openapi Skill?
Skills that share tags, products or a category with Whatsapp Openapi Skill: ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars), Step Parts (earthtojake/text-to-cad, 18k stars), API Designer (Jeffallan/claude-skills, 12k stars) and OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Whatsapp Openapi Skill?
holon-run (a GitHub organization) maintains it in holon-run/uxc, which has 116 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on September 15, 2026.
Source: holon-run/uxc on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.