Name: appointo
Rating: 51.2 (1 reviews)
Author: membranedev

appointo

Appointo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Appointo data.

Quality

56%

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

Quality

Content

63%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 is highly actionable with executable Membrane CLI commands and a well-sequenced, state-aware connection workflow, but it carries some redundant prose and inlines reference material that could live in a separate file.

Suggestions

Trim the opening paragraph and the redundant 'Popular actions' section, or actually enumerate a few popular Appointo actions there.

Move the proxy options table and action input/output schema details into a references/ file and link to it from the body.

Label 'Step 2' explicitly (e.g. add a '### Running actions' anchor) so the connection workflow's forward references resolve.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the introductory paragraph explaining what Appointo is and the redundant 'Popular actions' section (which repeats the action-list command) add padding Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready executable bash commands for install, login, connection, action listing, action running, and proxying, with only minor gaps such as the 'Popular actions' section not actually naming any actions.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (poll again after the user acts), though the referenced 'Step 2' is not explicitly labeled.	4 / 5
Progressive Disclosure	It is a single ~145-line file with no bundle references, and API-reference-style content (the proxy options table, action schema fields) is inlined rather than split into a separate reference file.	3 / 5
	Total	14 / 20 Passed

Description

50%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 both a what and a when clause and is anchored to a distinct brand niche, but its action language is generic and it misses the natural trigger terms (appointments, bookings, scheduling) a user would actually say.

Suggestions

Replace generic verbs with Appointo-specific actions, e.g. 'Create and manage appointments, bookings, classes, and customer records in Appointo.'

Expand the trigger clause to include natural synonyms: 'Use when the user wants to manage Appointo appointments, bookings, scheduling, or customer data.'

Drop the vague 'automate workflows' phrasing unless you can name a concrete workflow it supports.

Dimension	Reasoning	Score
Specificity	The description names the Appointo domain but its actions ('Manage data, records, and automate workflows') are generic and buzzwordy rather than concrete, Appointo-specific operations.	2 / 5
Completeness	It answers both 'what' ('Appointo integration. Manage data, records, and automate workflows') and 'when' with an explicit 'Use when the user wants to interact with Appointo data' clause, though the triggers are somewhat generic.	4 / 5
Trigger Term Quality	It relies almost entirely on the brand name 'Appointo' plus the generic phrase 'interact with Appointo data', omitting natural terms users would say such as appointments, bookings, or scheduling.	2 / 5
Distinctiveness Conflict Risk	The Appointo branding gives it a clear, distinct niche with low conflict risk, but the generic action language ('manage data, records') leaves minor overlap with other integration skills.	4 / 5
	Total	12 / 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/appointo/SKILL.md
Commit: f484c82

Reviewed: 3 days 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.