Name: till-payments
Rating: 47.2 (1 reviews)
Author: membranedev

till-payments

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

Quality

50%

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

Quality

Content

42%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 CLI workflow is concrete and actionable with a usable connection state machine, but the skill is dominated by a massive, duplicated, off-topic inline entity list that wastes context. Removing that list and adding verification steps for mutating operations would substantially improve the score.

Suggestions

Delete or move the ~250-item entity list out of SKILL.md; it is padded, duplicated, and contains finance terms (Stock, Bond, Commodity, Futures) unrelated to Till Payments.

Add validation/verification steps after running actions or proxying mutating requests (e.g. re-fetch the resource to confirm the change, check the response error field).

Fix the broken step references ('skip to Step 2' with no labeled Step 2, and '1b' with no '1a') so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	A ~250-item bulleted entity list (lines 23-260) is heavily padded, includes duplicated entries (Transaction, Balance, Report, Alert, Notification, Setting, Configuration, Log, Session, Authorization, Document, Template, Schedule, Task, Counter each appear twice), and lists generic finance terms unrelated to a POS/payments product (Stock, Bond, Commodity, Future, Portfolio), matching the 'severely verbose; heavily padded' anchor.	1 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run with --input JSON, request with a flags table), matching the 'mostly executable guidance with minor gaps' anchor; it stops short of level 5 because no concrete Till Payments-specific action example with real parameters is shown and the entity list adds no actionable value.	4 / 5
Workflow Clarity	There is a clear sequence (install, login, connection ensure, poll until READY / handle CLIENT_ACTION_REQUIRED, search actions, run, proxy fallback) with a connection-state feedback loop, but running actions and proxying mutating requests (POST/PUT/DELETE) lack verification steps, and per the rubric cap, destructive/batch operations without validation cap this at 3.	3 / 5
Progressive Disclosure	Section headers organize the CLI guidance reasonably and no bundle files exist, but the ~250-item inline entity list is monolithic content of little value that should be trimmed or moved out of SKILL.md, matching the 'some structure but could be better organized; content that should be separate is inline' anchor.	3 / 5
	Total	11 / 20 Passed

Description

57%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 answers both what and when with a clear brand-specific trigger, but its action language is generic rather than concrete payment operations. Tightening the verbs to actual Till Payments capabilities and adding trigger synonyms would lift specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete Till Payments actions, e.g. 'Process payments, issue refunds, reconcile settlements, and manage transactions and customers.'

Add natural trigger synonyms and phrasings users might say, such as 'refunds', 'settlements', 'POS transactions', or 'Till Payments reports'.

Make the 'when' clause more specific by tying it to concrete intents, e.g. 'Use when the user wants to process payments, issue refunds, or query Till Payments transactions.'

Dimension	Reasoning	Score
Specificity	It names the Till Payments domain and a few actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete payment-specific operations like processing payments, issuing refunds, or managing transactions, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states a clear 'what' ('Till Payments integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Till Payments data.'), but the 'when' is generic and could be more specific, matching the 'has both what and when; when could be more explicit' anchor rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	'Till Payments' is a strong natural brand keyword and 'interact with Till Payments data' is a usable trigger phrase, but it misses common synonyms or variations a user might say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Till Payments brand name anchors a clear niche with brand-specific triggers and minimal conflict risk, though the generic 'Manage data, records, and automate workflows' phrasing leaves minor overlap with general CRM/data skills, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	13 / 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/till-payments/SKILL.md
Commit: f484c82

Reviewed: 4 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.