CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

join-meeting

AgentCall (agentcall.dev) — Join a video meeting (Google Meet, Teams, Zoom) as an AI bot with voice and visual presence. Supports audio-only mode with voice intelligence (barge-in, interruptions), text-to-speech mode, and webpage modes for custom UI. Use when asked to join a call, attend a meeting, or participate in a video conference.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 exceptionally actionable — every command, event, and cleanup step is executable with explicit validation and recovery loops — but token efficiency is poor due to heavy duplication (screenshare, interruption handling, and CALL_LOOP each covered twice) and upsell content. Progressive disclosure is undermined by inlining reference-grade material and by nine broken examples/ links plus an orphaned references/api.md that is never linked.

Suggestions

Move the event catalogs, command tables, and the four event-reading methods out of SKILL.md into reference files (the existing but unlinked references/api.md is a natural home), leaving SKILL.md as a lean overview.

Deduplicate content that appears twice: the screenshare lifecycle and bridge-visual command tables (Modes Explained vs Pattern 5), interruption handling (Voice Strategies vs TTS Events), and the two CALL_LOOP variants — keep one canonical version each and cross-reference it.

Fix navigation: create or remove the nine broken examples/ references (the directory does not exist in the bundle) and link references/api.md from the Guides section so it is discoverable.

DimensionReasoningScore

Conciseness

The ~1,960-line body is noticeably verbose: the screenshare lifecycle and command tables are duplicated between "Modes Explained" and "Pattern 5", interruption handling is explained twice (Voice Strategies and TTS Events), two full CALL_LOOP variants plus per-framework integration tables are inlined, and it includes upsell prompts ("mention that Pro offers 4hr max duration — upgrade at https://app.agentcall.dev/add-credits") and meta-instructions to re-read the document every session. Matches anchor 2 ("noticeably verbose; several unnecessary explanations or padded sections") rather than 3 because the duplication and padding are extensive, even though most content is genuine operational detail.

2 / 5

Actionability

Fully executable throughout: exact JSON stdin commands and stdout event schemas, copy-paste bash/curl cleanup blocks (kill/SIGTERM sequence, status verification with jq and grep fallback), concrete script invocations for Python and Node, PowerShell and macOS variants, and an options/flags table. Matches anchor 5 ("copy-paste ready code or commands; specific examples cover the common cases").

5 / 5

Workflow Clarity

The CALL_LOOP algorithm is explicitly sequenced with a single exit condition (call.ended); setup (API key), join (lifecycle events with a 30-90s patience window), and cleanup are all step-numbered. Validation and feedback loops are present: command.ack/command.error watching per command, post-screenshare curl verification with two recovery paths, screenshot-based diagnosis, and mandatory API verification that the call actually ended. Matches anchor 5; no destructive/batch validation cap applies.

5 / 5

Progressive Disclosure

Good signaling exists — all nine references/guides/*.md files are real, one level deep, and listed with descriptions — but hundreds of lines of event catalogs, command tables, and a four-method event-reading tutorial are inlined in SKILL.md instead of living in the existing yet never-linked references/api.md, and nine examples/ links point to a directory that does not exist in the bundle. Matches anchor 3 ("content that should be separate is inline"); not 2 because structure is extensive and references are clearly signaled, not 4 because the inlining and broken example links are more than minor gaps.

3 / 5

Total

15

/

20

Passed

Description

87%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 description: third-person voice, concrete capability list, named platforms, and an explicit multi-phrase "Use when" trigger clause. The only gaps are a few unmentioned features (screenshare, chat, transcripts) and minor trigger synonyms, which keep specificity and trigger-term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Concrete capabilities are named — "Join a video meeting (Google Meet, Teams, Zoom) as an AI bot with voice and visual presence", "audio-only mode with voice intelligence (barge-in, interruptions), text-to-speech mode, and webpage modes for custom UI" — with specific platforms. Falls short of 5 because major capabilities (screenshare, meeting chat, transcripts, screenshots) are omitted, leaving minor-to-moderate coverage gaps; clearly above 3 since multiple distinct actions are listed.

4 / 5

Completeness

Explicitly answers both questions: the what ("Join a video meeting... as an AI bot with voice and visual presence. Supports audio-only mode... text-to-speech mode, and webpage modes") and the when ("Use when asked to join a call, attend a meeting, or participate in a video conference") with concrete trigger phrases. Matches the anchor-5 example structure exactly; a 4 would require the when-clause to be less explicit.

5 / 5

Trigger Term Quality

"Use when asked to join a call, attend a meeting, or participate in a video conference" plus platform names (Google Meet, Teams, Zoom) gives good natural-phrase coverage users would actually say. Not 5: common variants like "video call" or "hop on a call" are missing; well above 3 because both verb phrases and platform names are covered.

4 / 5

Distinctiveness Conflict Risk

Clear niche — an AI bot joining Google Meet/Teams/Zoom meetings via AgentCall — with distinct triggers (platform names plus join/attend/participate phrasing). Minimal overlap risk with any other plausible skill; matches the anchor-5 "clear niche with distinct triggers".

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1971 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 10 missing, 17 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 37 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

pattern-ai-labs/agentcall

Path

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.