Name: aloha-pos
Rating: 61.6 (1 reviews)
Author: membranedev

aloha-pos

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/aloha-pos/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 skill body is highly actionable with copy-paste CLI commands and a clear connect-then-poll-then-act workflow, supported by good section structure. It could improve by adding an explicit validation/retry checkpoint during connection polling and by splitting the action schema and proxy reference into one-level-deep reference files.

Suggestions

Add an explicit validation feedback loop for the BUILDING connection state (e.g. 'If state stays BUILDING past timeout, re-run connection get and inspect the error field before retrying') to lift workflow clarity.

Move the detailed clientAction object schema and proxy flag table into a short reference file (e.g. REFERENCE.md) and link to it, improving progressive disclosure.

Trim the introductory Aloha POS overview paragraph since Claude already knows what a POS system is, to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and minimal concept explanation, though sections like the opening POS overview and some prose around connection states could be trimmed slightly.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests, with flag tables and JSON usage covering the common cases.	5 / 5
Workflow Clarity	The connect-to-poll-to-action flow is clearly sequenced with explicit state branches (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and polling guidance, but the connection setup lacks an explicit validate-and-retry feedback loop checkpoint for the BUILDING state.	4 / 5
Progressive Disclosure	Content is well organized into install, auth, connection, searching, popular actions, and best-practices sections, but there are no separate reference files for the action schema or proxy options, and the overview entity list sits inline without deeper reference pointers.	4 / 5
	Total	17 / 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 is functional with both a what and an explicit when clause and a distinct app name, but its action language ('Manage data, records, and automate workflows') is generic rather than POS-specific. Tightening the actions to concrete Aloha operations would raise specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Aloha POS actions such as 'manage orders, payments, customers, products, discounts, and taxes'.

Add natural trigger synonyms a user would say, e.g. 'Use when the user wants to query orders, process payments, or manage menu items in Aloha POS'.

Drop the buzzword 'automate workflows' unless a concrete workflow capability is described, to reduce over-claiming.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Aloha POS integration') and a few generic actions ('Manage data, records, and automate workflows'), but these are minimal and non-specific rather than concrete POS operations like orders, payments, or products.	3 / 5
Completeness	It has a clear 'what' (Aloha POS integration / manage data, records, workflows) and an explicit 'when' clause ('Use when the user wants to interact with Aloha POS data'), though the trigger could be more specific.	4 / 5
Trigger Term Quality	It includes the natural keyword 'Aloha POS' and the trigger phrase 'interact with Aloha POS data', but lacks synonyms or common variations a user might say (e.g. orders, payments, restaurant POS).	3 / 5
Distinctiveness Conflict Risk	The named app 'Aloha POS' gives it a clear niche distinct from generic data skills, with only minor overlap risk against other POS or integration skills.	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/aloha-pos/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.