Tessl • The management layer for AI agent skills

SkillPublic

cliengo

Cliengo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cliengo 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/cliengo/SKILL.md

Quality

Content

57%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 provides concrete, mostly copy-paste-ready Membrane CLI commands with a clear connection-setup state machine, making it genuinely actionable. Weaknesses are the padded marketing intro, a dangling 'Step 2' reference, no validation guidance for destructive actions like delete-contact, and a monolithic action catalog that belongs in a separate reference file.

Suggestions

Remove the marketing/background paragraph and the filler lines ('Use action names and parameters as needed', the Agent Types aside), keeping only what the agent needs to operate the CLI.

Fix the workflow numbering — either label 'Searching for actions' as Step 2 and the connection steps as Step 1, or drop the 'skip to Step 2' phrasing — and add a verification step before destructive actions like delete-contact (e.g. get-contact first, confirm with the user, then delete).

Add one end-to-end example of running a listed action (e.g. membrane action list --intent 'list contacts' followed by membrane action run with the returned id), and consider moving the full action catalog to a references/ file with a few key examples inline.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples and tables, but the marketing-flavored intro ('Small to medium-sized businesses... use Cliengo to improve customer engagement and increase sales conversions'), the empty line 'Use action names and parameters as needed', and the awkward Agent Types note are unnecessary padding.	3 / 5
Actionability	Concrete executable commands cover install, login (including headless fallback), connection setup with --wait polling, action search/run with JSON input, and proxy usage with a flags table. Minor gap: the popular-actions table lists keys rather than actionIds and there is no end-to-end example of invoking one of the listed actions.	4 / 5
Workflow Clarity	The setup sequence is present with state-based branching (READY / BUILDING / CLIENT_ACTION_REQUIRED with re-polling), but 'skip to Step 2' is a dangling reference (no Step 1 or Step 2 headings exist), and destructive operations like delete-contact appear in the actions table with no validation or verification guidance, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references (no bundle files exist), but the 20-row popular-actions catalog is reference material inlined in SKILL.md that could live in a separate file, and there is no layering to deeper material.	3 / 5
	Total	13 / 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 Cliengo niche and includes an explicit 'Use when' clause, giving it solid completeness and distinctiveness. However, the capability statement is generic ('Manage data, records, and automate workflows') and trigger coverage relies solely on the brand name, missing natural terms like chatbot, live chat, leads, or conversations.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete capabilities, e.g. 'List and update contacts, retrieve conversations and chat messages, send chat replies, and manage sites and users in Cliengo'.

Expand the 'Use when' clause with concrete trigger phrases users would actually say, e.g. 'Use when the user mentions Cliengo, chatbot leads, live chat conversations, or wants to manage Cliengo contacts and sites'.

Add natural synonyms (chatbot, live chat, lead qualification, CRM) so the skill triggers on domain language even when the brand name isn't spoken.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Cliengo integration') but the stated actions are generic — 'Manage data, records, and automate workflows' is minimal/generic phrasing with no concrete capabilities like listing contacts or sending chat messages.	2 / 5
Completeness	Both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Cliengo data') are explicitly present, but the what is vague and the when lacks concrete trigger phrases, matching the anchor where both exist yet could be more specific.	4 / 5
Trigger Term Quality	'Cliengo' is the natural brand keyword and 'Use when the user wants to interact with Cliengo data' includes it, but common variations users would say — chatbot, live chat, leads, conversations, CRM — are entirely missing.	3 / 5
Distinctiveness Conflict Risk	The Cliengo brand name anchors a clear niche with low wrong-skill risk, but the generic 'Manage data, records, and automate workflows' wording overlaps with many data/automation skills, so overlap risk is minor rather than minimal.	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/cliengo/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

cliengo

Table of Contents

Is this your skill?