Name: clio-manage
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

clio-manage

Clio integration. Manage Recordses. Use when the user wants to interact with Clio data.

Quality

61%

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

Quality

Content

61%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 provides strong, executable Membrane CLI guidance with a clear connection workflow, but is held back by padded prose and an absence of validation checkpoints for the destructive CRUD/proxy operations it exposes. Structure and actionability are solid.

Suggestions

Trim marketing/conceptual prose (e.g., 'fastest way to get a connection', 'burn less tokens') to improve token efficiency.

Add a pre-flight validation or read-before-write step for destructive action runs and proxy POST/PUT/PATCH/DELETE calls (e.g., list the target record before modifying, confirm intent for deletes) to lift workflow_clarity above the destructive-operation cap.

Provide one fully-worked end-to-end example with concrete values (a specific action ID and CONNECTION_ID) to push actionability toward copy-paste-complete.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but contains padded/marketing prose ("fastest way to get a connection", "burn less tokens and make communication more secure") and conceptual explanation of Membrane that could be trimmed.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands cover install, auth, connect, search, run, and proxy use cases plus a flag table, but examples rely on placeholders (CONNECTION_ID, <actionId>, QUERY) and lack a worked end-to-end example, keeping it just below a 5.	4 / 5
Workflow Clarity	The connection-setup flow is clearly sequenced with state-branching and polling feedback loops, but the skill covers destructive CRUD and proxy (POST/PUT/PATCH/DELETE) operations with no pre-flight validation or verify steps, so the destructive-operation cap holds the score at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections and appropriately points to external official docs rather than inlining them, with only minor organization gaps; it does not reach 5 because there is no multi-file progressive split and the body exceeds 50 lines.	4 / 5
	Total	14 / 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 includes an explicit 'Use when...' trigger and names a distinct product, but the capability list is thin and contains a malformed term ('Recordses'). It is adequate but would benefit from concrete entity/action names and broader natural keywords.

Suggestions

Fix the typo 'Manage Recordses' and name concrete Clio entities and CRUD operations (e.g., 'Create, read, update, and delete matters, contacts, time entries, and bills').

Add natural trigger terms users would actually say, such as 'matters', 'contacts', 'time tracking', 'billing', or 'Clio records'.

Tighten the 'when' clause with concrete trigger phrases (e.g., 'Use when the user wants to manage matters, contacts, or billing in Clio').

Dimension	Reasoning	Score
Specificity	Names the domain ("Clio integration") and one concrete action ("Manage Recordses"), but the action is minimal and malformed, and no other operations are listed, so it is not comprehensive enough for a 4.	3 / 5
Completeness	Both a what ("Clio integration. Manage Recordses.") and an explicit when ("Use when the user wants to interact with Clio data.") are present, but the what is vague and the when is generic, so it does not reach the concrete-trigger-phrases level of a 5.	4 / 5
Trigger Term Quality	"Clio" is a distinct named term and "interact with Clio data" is a usable trigger phrase, but natural entity terms (matters, contacts, time entries) and synonyms are missing, and "Recordses" is malformed, so coverage is only partial rather than good.	3 / 5
Distinctiveness Conflict Risk	"Clio integration" targeting a named product gives a mostly distinct niche with only minor overlap risk, but the generic "interact with Clio data" framing keeps it just below the clearly-distinct 5.	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/clio-manage/SKILL.md
Commit: f484c82

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