Tessl • The management layer for AI agent skills

SkillPublic

cliniko

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

Quality

Content

82%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 concrete, executable commands and a well-handled connection state machine, though conciseness and workflow clarity have minor gaps. The main defects are broken step cross-references ('Step 2', '1b') and a small amount of padding.

Suggestions

Fix the dangling references: either label the sections as Step 1/Step 2 or rewrite 'skip to Step 2' and the '1b' heading to point at real section names.

Trim the intro paragraph describing what Cliniko is and the bolded entity bullet list, or fold the entities into the actions/triggers table where they carry information.

Consider moving the full 20-row actions table to a reference file (e.g., references/actions.md) and keeping only the top few in SKILL.md to shrink context load.

Dimension	Reasoning	Score
Conciseness	The body is dominated by copy-paste commands, flags, and tables with little padding, but includes trimmable material: the 'Cliniko is practice management software...' intro paragraph and a bare seven-item bolded entity list that adds no actionable information. This fits the efficient-with-minor-over-explanation anchor rather than the every-token-earns-its-place 5 anchor.	4 / 5
Actionability	Fully executable guidance throughout: exact npm/membrane commands with flags, a JSON-parameter example for action run, a proxy options table, and a state-by-state decision guide for connections. Commands are copy-paste ready with clear placeholders, covering the common cases.	5 / 5
Workflow Clarity	The install → login → connection → discover → run workflow is clearly sequenced with explicit state-machine checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a re-poll feedback loop. However, cross-references are broken: 'skip to Step 2' and the '1b' heading point to steps that are never labeled in the document, which keeps it below the 5 anchor.	4 / 5
Progressive Disclosure	The single file is well-sectioned (install, auth, connection, actions, proxy, best practices) with no nested or buried references, and no bundle files exist to mismanage. The 20-row popular-actions table is bulk reference-style content inlined in SKILL.md, a minor organization gap versus splitting it into a reference file, so it sits at the 4 rather than 5 anchor.	4 / 5
	Total	17 / 20 Passed

Description

61%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 distinct and has an explicit 'Use when' clause, but its capability statement is generic ('manage data, records, and automate workflows') and it lacks the domain's natural vocabulary. Naming concrete operations and trigger terms would lift specificity and trigger quality.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions, e.g., 'Manage appointments, patients, invoices, and treatment notes in Cliniko'.

Expand the trigger clause with natural user phrases: 'Use when the user mentions Cliniko, appointments, patient records, or clinic billing'.

Avoid the vague word 'data' appearing twice; tie triggers to the actual Cliniko objects users will name.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Cliniko domain but the stated actions are minimal and generic, with no concrete operations (e.g., appointments, patients, invoices, billing) — matching the anchor for domain named but generic actions, below the 3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Cliniko data"), but the 'when' is a single vague trigger rather than concrete trigger phrases, so it sits at the both-present-but-could-be-more-explicit anchor rather than 5.	4 / 5
Trigger Term Quality	"Cliniko" and "interact with Cliniko data" are relevant and natural, but the description misses common user vocabulary like appointments, patients, booking, invoices, or practice management, fitting the anchor for some relevant keywords missing variations/synonyms rather than the good-coverage 4 anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific application Cliniko gives it a clear niche with distinct triggers and minimal conflict risk with other skills, since users needing this skill will say "Cliniko".	5 / 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/cliniko/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.

cliniko

Table of Contents

Is this your skill?