Name: trengo
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

trengo

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

Quality

62%

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/trengo/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 strong, command-heavy integration guide with a well-sequenced connection workflow and explicit state/polling checkpoints. Its main weaknesses are a verbose intro, a redundant "Popular actions" section that promises actions but repeats the discovery command, and reliance on placeholders without a worked example query.

Suggestions

Trim the opening "Trengo is a customer service platform..." paragraph and other explanatory prose to assume Claude's knowledge of the domain.

Turn "Popular actions" into an actual list of concrete example action IDs/intents, or remove the section if the discovery command suffices.

Add one worked end-to-end example with a real intent (e.g. "list recent conversations") replacing the generic "QUERY" placeholder, and clarify the "Step 2"/"1b" numbering.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening paragraph explaining what Trengo is and prose like "This is the fastest way to get a connection" add explanation that could be trimmed, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides numerous concrete, executable CLI commands (install, login, connection ensure, action list/run, request) plus a full flag table, but relies on placeholders (CONNECTION_ID) and a generic "QUERY" intent without a worked example, leaving minor gaps from a perfect 5.	4 / 5
Workflow Clarity	A clear install→auth→connect→discover→run→proxy sequence exists with explicit state-checking and a poll/handle-client-action feedback loop, but the "Step 2"/"1b" numbering is inconsistent and some checkpoints are implicit, matching the clear-sequence-with-minor-gaps anchor.	4 / 5
Progressive Disclosure	The content is well-organized into clearly-headed sections with no nested external references (no bundle files exist), but at ~140 lines the "Popular actions" section is redundant/empty rather than split out, placing it at 4 rather than a clean 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly names the platform and includes an explicit "Use when" trigger, but its action language is generic ("manage data, records, automate workflows") rather than naming concrete Trengo capabilities. Trigger coverage relies on the brand name and omits the channel/ticket terms users would naturally mention.

Suggestions

Replace generic verbs with concrete Trengo capabilities, e.g. "Manage conversations, messages, channels, and users across WhatsApp, email, and social media."

Expand the trigger phrase to include natural user terms: "Use when the user wants to manage Trengo conversations, tickets, channels, or customer messages."

Add file-format or channel synonyms (WhatsApp, email, helpdesk tickets) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the Trengo domain but the stated actions — "Manage data, records, and automate workflows" — are generic and minimal rather than concrete capabilities, matching the score-2 anchor of domain-named but minimal/generic actions.	2 / 5
Completeness	Both elements are present: a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Trengo data"), though the when could be more specific, matching the score-4 anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Trengo data" surfaces the relevant keyword "Trengo"/"data", but it misses common natural variations a user would say (WhatsApp, email, customer service, tickets, conversations), fitting the some-keywords-but-missing-variants anchor.	3 / 5
Distinctiveness Conflict Risk	Trengo is a specific named product giving the skill a mostly-distinct niche with minimal overlap risk, but the surrounding language is generic, so it sits at 4 rather than a fully-distinct 5.	4 / 5
	Total	13 / 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/trengo/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.