CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

zoom-automation

Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.

Quality

70%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/zoom-automation/SKILL.md

The canonical home for this skill is zoom-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

A dense, actionable skill with named tools, parameters, and pitfalls, undermined by systematic duplication between per-workflow Pitfalls and the global 'Known Pitfalls' section, a vacuous closing section, missing pre-deletion validation for the permanent-delete workflow, and no offloading of the detailed API catalog into reference files.

Suggestions

Add an explicit verification step before permanent deletion: list recordings via ZOOM_LIST_ALL_RECORDINGS, confirm the meetingId/recording with the user, then call ZOOM_DELETE_MEETING_RECORDINGS.

Deduplicate the 'Known Pitfalls' section — remove rate limits, 'start_url' expiry, plan requirements, and UUID-encoding rules already stated per-workflow, and delete the filler 'When to Use' section.

Move the per-workflow parameter and pitfall detail into a reference file (e.g., references/zoom-tools.md), keeping SKILL.md as a lean overview with workflow triggers and the quick-reference table.

DimensionReasoningScore

Conciseness

The body mostly earns its tokens — concrete parameters, formats, and pitfalls with no explanations of known concepts — but the 'Known Pitfalls' section systematically re-duplicates per-workflow pitfalls (UUID double-encoding appears three times, 'start_url expires in 2 hours' twice, plan requirements twice), and the closing 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview') is pure filler.

3 / 5

Actionability

Highly concrete guidance: named tools, typed parameters ('start_time' ISO 8601 format, 'action': 'trash'/'delete'), rate limits, and a quick-reference table. It falls short of fully executable only in that no example tool-call payload is shown for the Rube MCP invocation pattern.

4 / 5

Workflow Clarity

Sequences are clearly ordered with [Prerequisite]/[Required]/[Optional] tags and the setup flow has explicit checkpoints (confirm connection ACTIVE), but the destructive ZOOM_DELETE_MEETING_RECORDINGS workflow ('"delete" is permanent') includes no verify-before-delete step (e.g., list and confirm the target recording first), capping workflow clarity at 3 per the destructive-operation rule.

3 / 5

Progressive Disclosure

The body is well-sectioned with headers and a quick-reference table, but 200+ lines of per-tool parameter and pitfall catalog are inlined in SKILL.md where a references file (e.g., a per-workflow detail doc) would keep the main file a lean overview — structure is present but content that should be separate is inline.

3 / 5

Total

13

/

20

Passed

Description

70%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.

A strong, specific description with good natural keywords and a distinct niche, but it lacks any 'Use when...' trigger guidance and slightly under-covers capabilities (usage reports, scheduling). Adding an explicit trigger clause would lift completeness materially.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user mentions Zoom meetings, webinars, recordings, or wants to schedule calls or track attendees.'

Mention the usage-reporting capability (daily usage statistics) to round out coverage.

Replace the generic word 'management' with concrete operations like 'update and reschedule meetings'.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Zoom meeting creation, management, recordings, webinars, and participant tracking' — but 'management' is generic and capabilities like usage reporting and scheduling are unmentioned, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

The 'what' is clear (automating Zoom meeting creation, recordings, webinars, participant tracking), but there is no 'when' clause — 'Always search tools first for current schemas' is an instruction to the agent, not trigger guidance, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural terms users would say are present: 'Zoom', 'meeting', 'webinars', 'recordings', 'participant tracking'. A few common phrasings are missing (e.g., 'schedule a meeting', 'attendees', 'invites', 'usage report'), keeping it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

'Zoom ... via Rube MCP (Composio)' carves out a clear niche with distinct triggers (Zoom meetings, webinars, recordings) and minimal overlap with other skills.

5 / 5

Total

16

/

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.

Validation — 15 / 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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/zoom-automation/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.