CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-webex

Add Webex channel integration via Chat SDK.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-webex/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clearly sequenced, validated workflow and strong error-recovery guidance — everything an agent needs to execute is concrete and copy-paste ready. The main weaknesses are moderate: a few paragraphs of design rationale that don't aid execution, and a monolithic single-file layout where a reference file could carry the detail sections.

Suggestions

Trim the directive-fence meta-explanation in the intro and the prompt-consumer design rationale in Credentials; keep only what the executing agent needs.

Move Troubleshooting (and optionally Channel Info) into a one-level-deep reference file (e.g., references/troubleshooting.md) and link to it from a brief overview, keeping SKILL.md lean.

DimensionReasoningScore

Conciseness

The body is mostly task-relevant and project-specific, but several paragraphs are design rationale rather than executable guidance (e.g., 'The mechanical steps under Apply carry nc: directive fences...', 'prompt only *asks* and binds the answer... so the same prompts could feed ncl or the OneCLI vault', 'This one line is the skill's only reach-in into core'), which could be tightened or trimmed.

3 / 5

Actionability

Fully executable throughout: exact file paths in nc:copy/nc:append directives, a pinned dependency (@bitbasti/chat-adapter-webex@0.1.0), concrete commands ('pnpm run build', 'pnpm exec vitest run src/channels/webex-registration.test.ts'), exact env var names, and precise troubleshooting API endpoints.

5 / 5

Workflow Clarity

The Apply section is a clearly sequenced four-step process with explicit validation (build guards the typed core call; the registration test proves install and registration), and the Troubleshooting section provides feedback loops for error recovery (e.g., 'red means the barrel import or the install drifted, so re-run the Apply steps').

5 / 5

Progressive Disclosure

The single SKILL.md is well-sectioned (Apply, Credentials, Webhook server, Channel Info, Troubleshooting) with no nested references, but at ~136 lines all content is inline — the Troubleshooting and Channel Info sections are candidates for a one-level-deep reference file; not anchor 5 because there is no deliberate overview-to-detail split.

4 / 5

Total

17

/

20

Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is short, accurate, and clearly scoped to Webex, but it is minimal: it states one generic action and omits any 'when to use' trigger guidance. Adding a 'Use when...' clause and one or two concrete actions (e.g., registering the adapter, storing bot credentials) would materially improve it.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user wants to add Cisco Webex as a chat channel, mentions Webex, or asks to wire a Webex bot into NanoClaw.'

Name 1-2 concrete actions beyond 'Add', e.g., 'Copies and registers the Webex adapter, pins its dependency, and stores the bot token and webhook secret.'

Include natural synonyms such as 'Cisco Webex', 'Webex bot', and 'Webex spaces' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Add Webex channel integration via Chat SDK" names the domain clearly but offers only one generic action ("Add... integration"); no concrete sub-actions like copying an adapter, registering it, or configuring credentials are stated.

2 / 5

Completeness

The 'what' is clear (add Webex channel integration), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

"Webex", "channel", and "Chat SDK" are relevant keywords a user might say, but common variations ("Cisco Webex", "Webex bot", "add a channel") and any 'Use when' phrasing are missing.

3 / 5

Distinctiveness Conflict Risk

Webex is a distinct niche, but the bare 'Add... integration' phrasing gives minor overlap risk with sibling channel-add skills (e.g., Slack or Teams adapters); it is not anchor 5 because the description lacks distinct trigger phrasing.

4 / 5

Total

12

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nanocoai/nanoclaw

Path

.claude/skills/add-webex/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.