CtrlK
BlogDocsLog inGet started
Tessl Logo

cisco-webex

Cisco Webex integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cisco Webex data.

55

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

68%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 copy-paste CLI commands and a clear connection-state workflow, but it pads in product background and motivational prose Claude does not need, and omits validation/verification steps for destructive and batch actions. Structuring and command examples are otherwise strong.

Suggestions

Remove background filler Claude already knows (e.g. 'competitor to Zoom or Microsoft Teams', 'so you can focus on integration logic rather than auth plumbing', 'This is the fastest way to get a connection').

Add verification checkpoints for write operations: after create/update/delete actions, run a get/list to confirm the result before reporting success.

Consider moving the popular-actions table into a references file and keeping SKILL.md as an overview with a pointer, to reduce inline bulk.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but includes unnecessary hand-holding Claude does not need ('This is the fastest way to get a connection', 'so you can focus on the integration logic rather than auth plumbing') and over-explains the product ('competitor to Zoom or Microsoft Teams').

3 / 5

Actionability

Provides fully executable, copy-paste-ready commands throughout — install, login, connection ensure/get with --wait, action list/run with JSON input, and the proxy command with all flags — covering the common cases completely.

5 / 5

Workflow Clarity

The connect-to-poll-to-ready sequence is laid out with state-based branching, but destructive/batch operations (create/update/delete meeting, create message/membership) have no validation or verify-before-proceeding checkpoints, which caps clarity at 3.

3 / 5

Progressive Disclosure

Content is well-sectioned (auth, connecting, searching, popular actions, running, proxy, best practices) with no bundle files to split out; the popular-actions table could live as a reference file but the single-file structure is appropriate and navigable.

4 / 5

Total

15

/

20

Passed

Description

57%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 has a clear and explicit 'Use when' trigger tied to a named product, giving it solid completeness and distinctiveness, but its action vocabulary is vague and generic. Tightening it to name concrete Webex capabilities (meetings, rooms/spaces, messages, memberships) would raise specificity and trigger-term coverage.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Webex actions, e.g. 'List and create meetings, rooms (spaces), messages, memberships, and teams.'

Broaden trigger terms to natural synonyms: 'Use when working with Cisco Webex meetings, rooms/spaces, messages, or team collaboration.'

Avoid generic 'data, records' wording that could apply to any integration and dilutes distinctiveness.

DimensionReasoningScore

Specificity

Names the domain (Cisco Webex) but the only stated actions are generic ('Manage data, records, and automate workflows') with no concrete operations like meetings, rooms, messages, or memberships.

2 / 5

Completeness

It explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Cisco Webex data'), but the 'what' is vague and the 'when' could name concrete trigger tasks.

4 / 5

Trigger Term Quality

'Cisco Webex' is a relevant natural term and the trigger clause repeats it, but it omits common synonyms/variations a user might say (video conferencing, meetings, spaces, webinars) that the body actually covers.

3 / 5

Distinctiveness Conflict Risk

The product-named trigger 'Cisco Webex' carves a clear niche with low overlap risk against other skills; minor risk only from the generic 'Manage data, records' phrasing.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.