Name: clio
Rating: 64 (1 reviews)
Author: membranedev

clio

Clio integration. Manage Matters, Contacts, Tasks, Events, Bills, Users. Use when the user wants to interact with Clio data.

Quality

76%

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

Quality

Content

73%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 executable CLI commands and a clear popular-actions reference, and is reasonably concise. Its chief gap is the absence of validation/verification checkpoints in batch and create/update workflows, which caps workflow clarity at 3.

Suggestions

Add explicit validation steps to batch and create/update workflows, e.g., verify a created matter's fields by running get-matter with the returned id before considering the operation complete.

Remove the redundant overview tree (lines 23-36) since the Popular actions table already covers the same entities more usefully, and drop filler like 'Use action names and parameters as needed.'

Add a brief feedback-loop note for failed action runs (e.g., inspect the --json error, then retry or fall back to membrane request) to satisfy the destructive/batch validation expectation.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands and a focused actions table, but the redundant overview tree and filler like 'Use action names and parameters as needed.' could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready membrane CLI commands throughout, a complete popular-actions table with keys, and a proxy flags table covering the common cases of list/get/create/update/proxy.	5 / 5
Workflow Clarity	Setup is sequenced (install, login, connect, search actions, run) with output-field guidance, but batch list operations and create/update operations lack explicit validation or verification checkpoints, capping workflow clarity at 3 per the destructive/batch guideline.	3 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear section headers and no nested references; structure is good but the overview tree and actions table overlap, keeping it just below a clean 5.	4 / 5
	Total	16 / 20 Passed

Description

78%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 is concise and specific, naming a clear product niche and six concrete resource types with an explicit 'Use when' trigger. Its main weakness is a generic trigger clause and missing synonyms that keep completeness and trigger-term quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Names the Clio domain and enumerates six concrete resource types (Matters, Contacts, Tasks, Events, Bills, Users), though 'Manage' is a single generic verb rather than distinct named actions, placing it just below a comprehensive 5.	4 / 5
Completeness	Provides a clear 'what' (manage listed Clio resources) and an explicit 'Use when the user wants to interact with Clio data' clause, but the trigger is generic rather than listing concrete situational triggers.	4 / 5
Trigger Term Quality	Includes natural terms a Clio user would say (Matters, Contacts, Tasks, Events, Bills, Users) with good coverage, but misses common synonyms such as 'cases', 'clients', 'invoices', and 'calendar'.	4 / 5
Distinctiveness Conflict Risk	'Clio integration' anchored on a specific named SaaS product gives it a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/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.