Name: cloudtalk
Rating: 60 (1 reviews)
Author: membranedev

cloudtalk

CloudTalk integration. Manage Persons, Organizations, Deals, Activities, Notes, Files and more. Use when the user wants to interact with CloudTalk data.

Quality

70%

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 ./skills/cloudtalk/SKILL.md

Quality

Content

75%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 concrete commands and a well-sequenced, state-checked connection workflow, and it is organized into clear navigable sections. The main weakness is conciseness: an encyclopedic/marketing intro and a redundant overview tree add tokens that do not earn their place.

Suggestions

Cut the opening encyclopedic/marketing paragraph ("CloudTalk is a cloud-based phone system… used by businesses of all sizes looking to improve their communication and customer service") and the redundant Overview tree; keep only operational specifics.

Label the action-search/run section as "Step 2" (or remove the "skip to Step 2" cross-references) so the workflow's stated checkpoints resolve to real headings.

Consider moving the full popular-actions table and proxy flag reference into a separate reference file linked from the body, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly useful operational guidance, but it opens with an encyclopedic/marketing paragraph ("cloud-based phone system designed for sales and support teams… used by businesses of all sizes") and a redundant Overview tree that restate what Claude already knows or what the action table already covers.	3 / 5
Actionability	It provides copy-paste-ready commands for every phase (login, connection ensure, action list/run, request) plus a concrete flag-reference table and a real action-key catalog, fully covering the common cases.	5 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clearly ordered with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, though the "skip to Step 2" reference points to an unlabeled section.	4 / 5
Progressive Disclosure	There are no bundle files and the body is organized into well-labeled sections, but the sizable 12-row popular-actions catalog and proxy flag table are inline reference material that could plausibly live in separate files.	4 / 5
	Total	16 / 20 Passed

Description

66%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 answers both what and when and is clearly anchored to the named CloudTalk product, but it leans on one generic verb and an entity list that does not match the natural trigger language for a phone-system skill. Tightening the verb diversity and aligning triggers with CloudTalk's actual capabilities (calls, SMS, agents) would raise specificity and trigger quality.

Suggestions

Replace the single generic verb "Manage" with several concrete actions (e.g., "Place and retrieve calls, send SMS, manage agents and contacts") to improve specificity.

Align trigger terms with how users actually refer to CloudTalk (calls, SMS, agents, contacts, phone system) instead of CRM-style entities like Deals and Notes that the body does not cover.

Make the "Use when" clause more specific, e.g., "Use when the user wants to send or look up CloudTalk calls, SMS, agents, or contacts."

Dimension	Reasoning	Score
Specificity	The description names the CloudTalk domain and a concrete set of entities ("Manage Persons, Organizations, Deals, Activities, Notes, Files"), but relies on a single generic verb ("Manage") and explicitly hedges with "and more," so the concrete actions are not comprehensive.	3 / 5
Completeness	Both "what" (Manage the listed entities) and "when" ("Use when the user wants to interact with CloudTalk data") are present, but the "when" clause is general and could be more explicit about specific triggering scenarios.	4 / 5
Trigger Term Quality	It surfaces "CloudTalk" and "CloudTalk data" as triggers, but the entity list (Persons, Organizations, Deals, Activities, Notes, Files) is not the natural language a CloudTalk user would say, and common synonyms (calls, SMS, agents, contacts, phone system) are missing.	3 / 5
Distinctiveness Conflict Risk	CloudTalk is a named product with a clearly scoped trigger ("interact with CloudTalk data"), giving it a distinct niche with minimal risk of triggering for unrelated skills.	5 / 5
	Total	15 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/cloudtalk/SKILL.md
Commit: f484c82

Reviewed: ~11 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.