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

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

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 delivers strong executable guidance with a clear connection workflow and state-handling feedback loop. Its main weakness is conciseness, led by an unnecessary marketing intro paragraph and a few padded explanatory sentences.

Suggestions

Trim or remove the opening marketing paragraph about Cliengo's target market and sales-conversion benefits; Claude does not need this background to use the integration.

Fix the workflow numbering (label the referenced "Step 2" and add the missing "1a") so the connection sequence is unambiguous.

Consider moving the 20-row popular-actions table into a references file and keeping only a few representative examples inline, to reduce token cost on every load.

Dimension	Reasoning	Score
Conciseness	The opening marketing paragraph ("sales-focused chatbot… improve customer engagement and increase sales conversions") and phrases like "so you can focus on the integration logic rather than auth plumbing" explain background Claude does not need, matching the anchor for mostly efficient content with some unnecessary explanation.	3 / 5
Actionability	Concrete executable commands are provided throughout (connection ensure, action list/run, request with a full flag table), giving mostly copy-paste-ready guidance with only minor gaps such as generic placeholders and no fully worked input example.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with state-based checkpoints and a poll-until-READY feedback loop, but it references an unlabeled "Step 2" and a "1b" subsection with no corresponding "1a", leaving minor gaps.	4 / 5
Progressive Disclosure	The single-file skill is well-organized with clear section headers and appropriately scoped guidance, though the ~160-line body with a 20-row actions table inlined and no external reference files keeps it just short of the ideal one-level-deep structure.	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 correctly names the target app and includes a Use-when clause, covering both what and when. It is held back by generic action verbs and thin trigger-term coverage that lack synonyms or concrete triggers.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Cliengo-specific actions such as listing/creating/updating contacts, conversations, sites, and chatbots.

Expand the trigger clause with natural phrases users would say, e.g. "Use when the user wants to manage Cliengo contacts, conversations, chatbots, or sites, or send messages in a Cliengo conversation."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Cliengo domain plus a couple of actions, but the actions are generic ("manage data") rather than concrete, matching the anchor for 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Cliengo data"), but the when-clause is generic rather than listing concrete trigger phrases, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	The only natural keyword is "Cliengo" / "Cliengo data"; common variations and synonyms a user might say are missing, matching the anchor for some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app Cliengo gives it a clear niche with minimal conflict risk, though the generic action verbs keep it just short of the fully distinct 5-anchor.	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/cliengo/SKILL.md
Commit: f484c82

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