New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Webex Channel for NanoClaw

by nanocoai in nanocoai/nanoclaw

Adds Cisco Webex support to NanoClaw through the Chat SDK bridge, using a third-party adapter package and a bot made in the Webex Developer Portal.

MITAuto-check: notesProductivity & Automation

Install Webex Channel for NanoClaw

skills CLI
$ npx skills add nanocoai/nanoclaw --skill add-webex -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nanocoai/nanoclaw add-webex --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/add-webex .claude/skills/add-webex && rm -rf skills-src

Use ~/.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/

Facts

Skill name
add-webex
GitHub stars
31k
Token cost
~1.5k tokens
SKILL.md length
789 words
Files
3
Skills in repo
59
Repo updated
First seen
Licence
MIT

At a glance

Adds Cisco Webex support to NanoClaw through the Chat SDK bridge, using a third-party adapter package and a bot made in the Webex Developer Portal.

  • Works in 4 steps: Copy the adapter and its registration test → Register the adapter → Install the adapter package → …
  • Connecting a NanoClaw agent to Cisco Webex spaces
  • SKILL.md covers Apply, Credentials, Next Steps and Channel Info, plus 1 more section
  • Calls ngrok and pnpm; reaches webexapis.com; needs WEBEX_BOT_TOKEN and WEBEX_WEBHOOK_SECRET

What it does

The Webex adapter is copied from the `channels` branch and registered with a single import. Its package comes from the third-party `@bitbasti` namespace rather than the main chat adapter family, so it carries its own pinned version and does not follow the chat core version.

After installing the package, the skill builds and runs a registration test that asserts `webex` is in the channel registry. The bot has to be created by hand in the Webex Developer Portal, and a webhook is set up so messages reach NanoClaw. Until then the adapter compiles but cannot receive anything. Delivery in a real Webex space is checked manually.

When your agent uses it

  • Connecting a NanoClaw agent to Cisco Webex spaces
  • Creating a Webex bot for an agent
  • Re-applying the Webex adapter after a NanoClaw update

Example prompts

  • “Add Webex to NanoClaw and explain how to create the bot in the Developer Portal.”
  • “Install the Webex adapter and run its registration test.”
  • “Set up the Webex webhook so my agent receives space messages.”

Requirements

  • A NanoClaw installation with pnpm
  • A Webex bot created in the Webex Developer Portal

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Copy the adapter and its registration test
  2. Register the adapter
  3. Install the adapter package
  4. Build and validate

What it can do on your machine

Read from SKILL.md and the folder at commit 66f0823. 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

    Shell commands in SKILL.md call:

    • ngrok
    • pnpm

    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:

    • webexapis.com

    Also links to:

    • developer.webex.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • WEBEX_BOT_TOKEN
    • WEBEX_WEBHOOK_SECRET

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Webex Channel for NanoClaw loads about 1.5k tokens when it runs. Until then it costs about 13 tokens; SKILL.md has 789 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~13
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:86
    ed `ncl` or the OneCLI vault instead of `.env` by swapping only the consumer.
  • NoteMentions a .env fileSKILL.md:87
    Here they go to `.env` (set-if-absent — a value you've already filled in is
  • NoteMentions a .env fileSKILL.md:128
    webhook with a known secret and update `.env` to match.

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from nanocoai/nanoclaw at commit 66f0823, republished under its MIT licence (© nanocoai). 789 words, ~1,496 tokens.

Download SKILL.mdSave it as .claude/skills/add-webex/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
add-webex
description
Add Webex channel integration via Chat SDK.

Add Webex Channel

Adds Cisco Webex support via the Chat SDK bridge. NanoClaw doesn't ship channels in trunk — this skill copies the Webex adapter in from the channels branch.

The mechanical steps under Apply carry nc: directive fences: an agent reads the prose and applies them, and a parser can apply them deterministically from the same document. Every directive is idempotent, so the whole skill is safe to re-run; anything a parser can't apply falls back to the prose beside it.

Apply

1. Copy the adapter and its registration test

Fetch the channels branch and copy the Webex adapter and its registration test into src/channels/ (overwrite — the branch is canonical):

nccopy
src/channels/webex.ts
src/channels/webex-registration.test.ts
2. Register the adapter

Append the self-registration import to the channel barrel (skipped if the line is already present). This one line is the skill's only reach-in into core:

ncappend
import './webex.js';
3. Install the adapter package

Pinned to an exact version — the supply-chain policy rejects ranges and latest. The Webex adapter ships under the third-party @bitbasti/* namespace, not @chat-adapter/*, so it carries its own version line (0.1.0) rather than tracking the chat core version:

ncdep
@bitbasti/chat-adapter-webex@0.1.0
4. Build and validate

Build first: it guards the typed createChatSdkBridge(...) core call and proves the dependency is installed. Then run the one integration test.

ncrun
pnpm run build
ncrun
pnpm exec vitest run src/channels/webex-registration.test.ts

webex-registration.test.ts imports the real channel barrel and asserts the registry contains webex. It goes red if the import line is deleted or drifts, if the barrel fails to evaluate, or if @bitbasti/chat-adapter-webex isn't installed (the import throws) — so it also covers the dependency from step 3. End-to-end delivery against a real Webex space is verified manually once the service runs — see the webhook setup below.

Credentials

Webex bot setup is human and interactive — these steps are prose, not directives (no parser can click through the Webex Developer Portal). A recipe rebuild produces a compiling, registered adapter that cannot receive a message until they're done.

Create the Webex bot
  1. Go to developer.webex.com and create a new bot.
  2. Copy the Bot Access Token.
  3. Set up a webhook:
    • Use the Webex API or Developer Portal to create a webhook pointing to https://your-domain/webhook/webex.
    • Set a webhook secret for signature verification.
Store the credentials

Capture the two values, then write them. prompt only asks and binds the answer to a name; a separate directive consumes it — so the same prompts could feed ncl or the OneCLI vault instead of .env by swapping only the consumer. Here they go to .env (set-if-absent — a value you've already filled in is never overwritten):

ncprompt
Paste the Bot Access Token — from the Webex bot you created.
ncprompt
Paste the webhook secret you set for signature verification.
ncenv-set
WEBEX_BOT_TOKEN={{bot_token}}
WEBEX_WEBHOOK_SECRET={{webhook_secret}}
Webhook server

The Chat SDK bridge automatically starts a shared webhook server on port 3000 (WEBHOOK_PORT to change it), handling /webhook/webex. This port must be publicly reachable for Webex to deliver events. Running locally, expose it with ngrok (ngrok http 3000), a Cloudflare Tunnel, or a reverse proxy on a VPS — the resulting public URL is the base for the webhook URL above.

Show full SKILL.md (311 more words)Show less

Next Steps

If you're in the middle of /setup, return to the setup flow now. Otherwise run /manage-channels to wire this channel to an agent group.

Channel Info

  • type: webex
  • terminology: Webex has "spaces." A space can be a group conversation or a 1:1 direct message with the bot.
  • how-to-find-id: Open the space in Webex, click the space name > Settings — the Space ID is listed there. Or use the Webex API (GET /rooms) to list spaces and their IDs.
  • supports-threads: yes
  • typical-use: Interactive chat — team spaces or direct messages
  • default-isolation: Same agent group for spaces where you're the primary user. Separate agent group for spaces with different teams or sensitive information.

Troubleshooting

Sends fail with 401. The Bot Access Token is shown once, on the bot's page under developer.webex.com → My Apps — it is not the 12-hour personal access token from the API docs pages, which is the classic mix-up (that one works briefly, then everything 401s). Regenerate the token on the bot page if needed; regenerating invalidates the old value, so update WEBEX_BOT_TOKEN right away.

Messages in the space never reach the agent. Webex delivers only to the webhook you created: it must target your public host at /webhook/webex (shared webhook server, port 3000) with resource messages. List your webhooks with GET https://webexapis.com/v1/webhooks using the bot token — Webex flips a webhook to inactive after repeated delivery failures, and it stays off until you re-enable or recreate it.

Events arrive but are rejected. Signature mismatch: the secret set at webhook creation must equal WEBEX_WEBHOOK_SECRET exactly. Recreate the webhook with a known secret and update .env to match.

Adapter installed but silent. Run pnpm exec vitest run src/channels/webex-registration.test.ts — red means the barrel import or the @bitbasti/chat-adapter-webex install drifted, so re-run the Apply steps. If green, restart the service so it loads the adapter and the tokens, then watch logs/nanoclaw.log for the webhook hit.

© nanocoai, 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 2 other files in .claude/skills/add-webex of nanocoai/nanoclaw.

  • SKILL.md
  • REMOVE.md
  • apply-fixtures.json

Open the folder on GitHubat commit 66f0823

Compare with similar skills

Webex Channel for NanoClaw 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.

Webex Channel for NanoClaw compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Webex Channel for NanoClaw this skillnanocoai/nanoclaw31k—~1.5kAutomated safety check: NotesMIT
Ak Dev New Messaging Integrationyaalalabs/agent-kernel191—~4.2kAutomated safety check: PassApache-2.0
Feishu LarkOpenClaudia/openclaudia-skills711—~7.4kAutomated safety check: NotesMIT
Ak Add Integrationyaalalabs/agent-kernel191—~2.6kAutomated safety check: PassApache-2.0
Integrate Whatsappgokapso/agent-skills175—~4.8kAutomated safety check: PassNone
Paper Feishu Digestchtc66/academic-skills360—~348Automated safety check: PassMIT

Similar skills

  • Ak Dev New Messaging Integration

    yaalalabs/agent-kernel

    Step-by-step guide for adding a new messaging platform integration to Agent Kernel.

    191 GitHub stars~4.2k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Feishu Lark

    OpenClaudia/openclaudia-skills

    Send messages and interactive cards to Feishu (飞书) and Lark channels via webhooks or Bot API.

    711 GitHub stars~7.4k tokensUpdated 20 days ago
    Productivity & AutomationAuto-check: notes

  • Ak Add Integration

    yaalalabs/agent-kernel

    Add a messaging platform integration to an existing Agent Kernel project.

    191 GitHub stars~2.6k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Integrate Whatsapp

    gokapso/agent-skills

    Connect WhatsApp to your product with Kapso: onboard customers with setup links, detect connections, receive events via webhooks, and send messages/templates/media.

    175 GitHub stars~4.8k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Paper Feishu Digest

    chtc66/academic-skills

    monitor recent arxiv papers and produce a chinese digest when the user needs a filtered paper watchlist, a ranked update for agent or rag related topics, or an optional feishu webhook push from…

    360 GitHub stars~348 tokensUpdated 6 mo ago
    Backend & APIsAuto-check passed

  • Chat SDK

    databuddy-analytics/Databuddy

    Build multi-platform chat bots with Chat SDK (chat npm package).

    1.2k GitHub stars~2.6k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from nanocoai/nanoclaw

All 59 skills in this repo

  • Iron Proxy Gateway for NanoClaw

    nanocoai/nanoclaw

    Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.

    31k GitHub stars~4.6k tokensUpdated 2 days ago
    Auto-check: notes

  • Agent Browser

    nanocoai/nanoclaw

    Drives a web browser from the shell with the agent-browser CLI: open pages, read an element snapshot, click and fill by reference, grab text and screenshots.

    31k GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check passed

  • NanoClaw OneCLI Gateway Installer

    nanocoai/nanoclaw

    Installs or refreshes OneCLI as the gateway provider for NanoClaw, copying the adapter files, registering the provider and running the setup script.

    31k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check: notes

  • OpenClaw to NanoClaw Migration

    nanocoai/nanoclaw

    Guides a conversational migration from an OpenClaw install to NanoClaw v2, carrying over identity, channel credentials, scheduled tasks and workspace files.

    31k GitHub stars~6k tokensUpdated 2 days ago
    Auto-check: notes

  • Add A Second Dial Phone Number

    nanocoai/nanoclaw

    Wires up an additional phone number onto an already-installed Dial channel, so one NanoClaw install answers SMS and AI voice calls on more than one line.

    31k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • NanoClaw LLM Wiki Setup

    nanocoai/nanoclaw

    Adds a persistent wiki knowledge base to a NanoClaw group following Karpathy's LLM Wiki pattern, with folders, a tailored container skill and a CLAUDE.md section.

    31k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

Categories

Questions about Webex Channel for NanoClaw

What does Webex Channel for NanoClaw do?

Adds Cisco Webex support to NanoClaw through the Chat SDK bridge, using a third-party adapter package and a bot made in the Webex Developer Portal. The Webex adapter is copied from the `channels` branch and registered with a single import. Its package comes from the third-party `@bitbasti` namespace rather than the main chat adapter family, so it carries its own pinned version and does not follow the chat core version.

When should I use Webex Channel for NanoClaw?

Webex Channel for NanoClaw fits situations like: connecting a NanoClaw agent to Cisco Webex spaces; creating a Webex bot for an agent; re-applying the Webex adapter after a NanoClaw update.

How do I install Webex Channel for NanoClaw in Claude Code?

Run `npx skills add nanocoai/nanoclaw --skill add-webex -a claude-code`. Or copy the skill folder (.claude/skills/add-webex in nanocoai/nanoclaw) into .claude/skills/add-webex in your project. Claude Code loads it when a task matches its description.

How do I install Webex Channel for NanoClaw in Codex?

Run `npx skills add nanocoai/nanoclaw --skill add-webex -a codex`. Or copy the skill folder (.claude/skills/add-webex in nanocoai/nanoclaw) into .agents/skills/add-webex in your project. Codex loads it when a task matches its description.

Can I use Webex Channel for NanoClaw 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 nanocoai/nanoclaw --skill add-webex -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-webex, .gemini/skills/add-webex, .github/skills/add-webex and .opencode/skills/add-webex in your project.

What does Webex Channel for NanoClaw need to run?

Going by SKILL.md and its folder, Webex Channel for NanoClaw needs the command-line tools its instructions call (ngrok and pnpm) and credentials named WEBEX_BOT_TOKEN and WEBEX_WEBHOOK_SECRET. Our summary lists: A NanoClaw installation with pnpm; A Webex bot created in the Webex Developer Portal.

Does Webex Channel for NanoClaw access the network?

SKILL.md names 2 domains. In commands or code: webexapis.com; the agent is likely to contact it when it follows the instructions. As links in the text: developer.webex.com. This is read from the text; nothing was executed.

Is Webex Channel for NanoClaw safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Webex Channel for NanoClaw use?

Webex Channel for NanoClaw 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 Webex Channel for NanoClaw use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Webex Channel for NanoClaw?

Skills that share tags, products or a category with Webex Channel for NanoClaw: Ak Dev New Messaging Integration (yaalalabs/agent-kernel, 191 stars), Feishu Lark (OpenClaudia/openclaudia-skills, 711 stars), Ak Add Integration (yaalalabs/agent-kernel, 191 stars) and Integrate Whatsapp (gokapso/agent-skills, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Webex Channel for NanoClaw?

nanocoai (a GitHub organization) maintains it in nanocoai/nanoclaw, which has 30,897 GitHub stars. The repository holds 59 skills in this directory. The repository was last updated on October 6, 2026.

Source: nanocoai/nanoclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.