CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-video-calls-tavus

AI video conversations - create real-time video calls with AI personas

49

Quality

53%

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 ./skills/research-tools/capabilities/ai-video-calls-tavus/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The content is well-structured and concise with usable curl examples, but the primary Create Conversation example is malformed and unexecutable, and the workflow lacks validation checkpoints. Progressive disclosure is strong given the simple single-file design.

Suggestions

Fix the Create Conversation curl block so the persona_id and conversation_name are inside the -d JSON object with a single closing brace, making it copy-paste executable.

Remove the duplicated endpoint descriptions between the Capabilities and Usage sections to tighten conciseness.

Add a brief validation step after creating a conversation (e.g. check the response for a conversation URL/ID before proceeding) and clarify that persona_id must come from the List Personas output rather than the hardcoded example value.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the endpoint descriptions are repeated ("This endpoint returns a list of all Personas" appears under both Capabilities and Usage, and the Create Conversation description is likewise restated), so it could be tightened; matches 'Mostly efficient but includes some unnecessary explanation or could be tightened'.

2 / 3

Actionability

Curl commands are concrete, but the Create Conversation example is broken — the -d JSON object closes after "/v2/conversations" and then stray "persona_id"/"conversation_name" lines follow, making it non-executable; fits 'Some concrete guidance but incomplete; missing key details'.

2 / 3

Workflow Clarity

A sequence exists (list personas, choose one, create conversation), but there are no validation or error-recovery checkpoints and the persona_id parameter is shown as a hardcoded literal value (p1b06420cfdc) rather than tied to the list step, matching 'Steps listed but validation gaps'.

2 / 3

Progressive Disclosure

The skill is a single self-contained file with clear, well-organized sections and no bundle files to navigate; per the simple-skills note this warrants 3 even without external file references.

3 / 3

Total

9

/

12

Passed

Description

50%

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 states what the skill does in third person with a relevant domain and concrete verb, but lacks an explicit trigger clause and offers only one action. It is competent but generic, scoring a uniform 2 across dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to start or join an AI video call or needs a real-time conversation with an AI persona.'

List multiple concrete actions (e.g. 'list personas, start real-time video conversations, and manage AI replica calls') to lift specificity to 3.

Include more natural keyword variations such as 'video chat', 'real-time AI conversation', and 'digital persona' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Quotes "create real-time video calls with AI personas" name the domain and one concrete action, but only a single verb is offered rather than multiple specific actions, matching the anchor 'Names domain and some actions, but not comprehensive'.

2 / 3

Completeness

It states what the skill does but provides no explicit 'Use when...' trigger guidance, so per the judging guidelines completeness is capped at 2 ('Has what, but when is missing or only implied').

2 / 3

Trigger Term Quality

Terms like "AI video conversations", "video calls", and "AI personas" are relevant but missing common variations (e.g. 'video chat', 'real-time conversation'), placing it at 'Some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The AI-video-persona niche is fairly distinct, but "AI video conversations" could still overlap with general video/calling skills, fitting 'Somewhat specific but could still overlap with similar skills' rather than a clearly unambiguous niche.

2 / 3

Total

8

/

12

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
gooseworks-ai/goose-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.