Name: tawkto
Rating: 56.8 (1 reviews)
Author: membranedev

tawkto

Tawk.to integration. Manage Persons, Organizations, Leads, Deals, Projects, Activities and more. Use when the user wants to interact with Tawk.to data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/tawkto/SKILL.md

Quality

Content

67%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 a well-structured, highly actionable guide to driving Tawk.to via the Membrane CLI, with a solid connection-state feedback loop. Its main weaknesses are a slightly redundant introductory paragraph and a couple of cross-reference labels that could be clearer.

Suggestions

Trim or remove the opening "Tawk.to is a free live chat application..." paragraph, which restates general knowledge Claude already has.

Fix the "skip to Step 2" reference by labeling the subsequent sections as explicit numbered steps so the navigation is unambiguous.

Consider moving the detailed clientAction state machine and the proxy flag table into a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but opens by explaining what Tawk.to is ("a free live chat application that allows businesses to communicate with visitors") — a concept Claude already knows — and includes prose that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action run, request) with flags and JSON examples; minor gaps remain where placeholders like CONNECTION_ID must be substituted.	4 / 5
Workflow Clarity	The install → authenticate → connect → search → run sequence is clear, and the connection step includes a poll-until-ready feedback loop with explicit state handling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR). The "skip to Step 2" reference points to an unlabeled step, a minor navigation gap.	4 / 5
Progressive Disclosure	No bundle files are present, so all content lives in a single ~145-line file; it is well-organized with clear section headers and the connection-state detail and proxy flag table are reasonably placed inline, though some of that detail could be split into reference files.	4 / 5
	Total	15 / 20 Passed

Description

62%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 covers both what the skill does and when to use it with a clear brand anchor, but relies on a single generic verb ("Manage") and a somewhat generic trigger clause. Tightening the action verbs and trigger phrasing would raise specificity and trigger quality.

Suggestions

Replace the generic "Manage" with specific verbs for each resource (e.g., "Create and update Persons, search Leads, track Deals, log Activities").

Expand the "Use when" clause with concrete natural triggers (e.g., "Use when the user wants to look up a Tawk.to visitor, manage tickets, or pull chat/agent reports").

Add domain-specific terms users actually say (tickets, visitors, agents, chat transcripts) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain plus several concrete resources ("Manage Persons, Organizations, Leads, Deals, Projects, Activities and more"), but the only action verb is the generic "Manage", so the actions themselves are not specific or comprehensive.	3 / 5
Completeness	Both "what" (Tawk.to integration managing Persons/Leads/Deals/etc.) and "when" ("Use when the user wants to interact with Tawk.to data") are present and explicit, though the "when" clause could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces the brand "Tawk.to" and resource names (Leads, Deals, Persons), but the trigger phrasing "interact with Tawk.to data" is generic and missing common natural variations a user would actually say.	3 / 5
Distinctiveness Conflict Risk	The "Tawk.to" brand anchors a clear niche with low conflict risk, but the generic resource terms (Leads, Deals, Organizations) overlap somewhat with general CRM-style skills.	4 / 5
	Total	14 / 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/tawkto/SKILL.md
Commit: f484c82

Reviewed: 4 days 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.