build-zoom-team-chat-app

Use when building Team Chat.

Quality

43%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/zoom/skills/team-chat/SKILL.md

Quality

Content

65%

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

The body is well-paced and concise with a sensible six-step workflow and a clean references section. Its weaknesses are missing executable detail (deferred to references) and broken/incorrect reference paths that undermine navigation, plus no explicit validation checkpoints in the workflow.

Suggestions

Fix or remove the four dangling references (concepts/, examples/, troubleshooting/ paths) so every link resolves to a real bundle file.

Add at least one validation/verification checkpoint in the workflow — e.g. verify webhook signature and OAuth token refresh before sending — to satisfy the feedback-loop expectation.

Include one concrete executable snippet (a minimal message-send or webhook-handler payload) in SKILL.md so the core action is copy-paste ready, not just described.

Dimension	Reasoning	Score
Conciseness	The body is lean (~25 lines), does not explain concepts Claude already knows (no 'what is OAuth' or 'what is a webhook' padding), and every step earns its place, matching 'lean and efficient; assumes Claude's competence'.	3 / 3
Actionability	Steps name concrete components ('Team Chat API vs Chatbot API', 'JID formats, channel membership, scopes') but contain no executable code, commands, or payload shapes — the actual runnable detail is deferred to references — fitting 'some concrete guidance but incomplete' rather than copy-paste-ready level 3.	2 / 3
Workflow Clarity	Six steps are clearly sequenced, but there are no validation checkpoints or validate→fix→retry feedback loops despite token/auth and webhook operations; per the rubric's destructive/batch guideline this caps the score at 2 ('steps listed but validation gaps').	2 / 3
Progressive Disclosure	There is a clear References section signaling one-level-deep pointers, but the bundle is inconsistent: four referenced paths (concepts/api-selection.md, concepts/message-structure.md, examples/chatbot-setup.md, troubleshooting/common-issues.md) and the concepts/, examples/, troubleshooting/ directories do not exist, so navigation is partly broken — 'some structure but could be better organized' rather than clean level 3.	2 / 3
	Total	9 / 12 Passed

Description

22%

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 extremely terse — it gives a minimal trigger but no statement of what the skill does. It reads as a placeholder rather than a capability description and would struggle to distinguish itself from other chat-building skills.

Suggestions

Add a concrete what-clause naming the skill's capabilities, e.g. 'Builds Zoom Team Chat integrations: chatbots, message-card workflows, webhook automations, and user-scoped messaging.'

Expand trigger terms to natural variations users say ('Zoom Team Chat', 'ZTC', 'chatbot', 'message cards') to improve trigger coverage and distinctiveness.

Keep the 'Use when...' clause but pair it with the actions above so both what and when are explicit.

Dimension	Reasoning	Score
Specificity	The description 'Use when building Team Chat.' names no concrete actions at all — only the abstract activity 'building', matching the 'vague or no actions' anchor rather than level 2 which requires naming domain and some actions.	1 / 3
Completeness	It supplies a weak 'when' ('Use when building Team Chat') but entirely omits 'what' — no capability is stated — which matches 'missing what OR when, or both very weak'; it does not reach level 2 because there is no what clause at all.	1 / 3
Trigger Term Quality	'Team Chat' is a natural term a user would say, but it is the only keyword and common variations (Zoom Chat, ZTC, chatbot, message cards) are absent, fitting 'some relevant keywords but missing common variations' rather than the full coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	'Team Chat' points to a real niche, but the bare phrase could plausibly fire for other team-chat surfaces (Slack, MS Teams), so it sits at 'somewhat specific but could still overlap' rather than the clearly-distinct level 3.	2 / 3
	Total	6 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/zoom/skills/team-chat/SKILL.md
Commit: 11c74d6

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.