Name: chatwoot
Rating: 58.4 (1 reviews)
Author: membranedev

chatwoot

Chatwoot integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chatwoot data.

Quality

67%

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

Quality

Content

68%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 content is highly actionable with concrete CLI commands and a well-structured connection workflow, but it carries some unnecessary explanatory padding and omits validation steps for running potentially destructive Chatwoot actions. Tightening the prose and adding a verify-before-run checkpoint would raise the weaker dimensions.

Suggestions

Trim the opening paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing' to assume Claude's competence.

Add an explicit validation/verification step before running actions that mutate data, e.g. confirm the action's inputSchema and dry-run or confirm destructive operations before execution.

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

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the opening explainer of what Chatwoot is and phrases like 'so you can focus on the integration logic rather than auth plumbing', matching the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Provides copy-paste-ready CLI commands across install, login, connection, action search/run, and proxy, complete with a flags table and JSON examples covering the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection flow has explicit state-based checkpoints and a re-poll feedback loop, but running arbitrary Chatwoot actions (outward-facing, potentially destructive such as sending messages or deleting records) has no validation or verification step, triggering the destructive/batch cap at 3.	3 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and navigable structure appropriate for a CLI-integration skill; no bundle files exist to reference, and only minor content (the proxy flags table, clientAction state machine) might warrant separation, matching the good-structure anchor.	4 / 5
	Total	15 / 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 with an explicit 'Use when' clause and is clearly scoped to a named app, but its action list is generic and its trigger vocabulary is narrow. Tightening the actions to concrete Chatwoot operations and adding common synonyms would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Chatwoot operations, e.g. 'manage conversations, contacts, inboxes, and labels; send messages; run reports'.

Expand trigger terms with natural user phrasings such as 'customer conversations', 'support tickets', 'live chat', or 'helpdesk'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to read, create, or update Chatwoot conversations, contacts, or messages.'

Dimension	Reasoning	Score
Specificity	Names the Chatwoot domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Chatwoot-specific operations, fitting the 1-2 generic-actions anchor and falling short of comprehensive.	3 / 5
Completeness	Provides a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Chatwoot data'), but the 'when' is generic and could be more specific, matching the both-present-but-could-be-sharper anchor.	4 / 5
Trigger Term Quality	Includes the natural keyword 'Chatwoot' in phrases like 'Chatwoot integration' and 'interact with Chatwoot data', but lacks common variations or synonyms a user might say, matching the some-relevant-keywords anchor.	3 / 5
Distinctiveness Conflict Risk	Targets a single named application ('Chatwoot integration') with app-specific triggers, giving it a clear niche and minimal overlap risk with other 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/chatwoot/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.