Name: toast
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

toast

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

Quality

62%

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

Quality

Content

67%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 a solid, actionable integration guide with executable CLI commands and a well-validated connection workflow. Its main weaknesses are mild marketing-fluff padding in the overview and a broken step-numbering scheme that slightly muddies the overall sequence.

Suggestions

Trim the marketing-style overview paragraph and editorial phrases (e.g. "so you can focus on the integration logic rather than auth plumbing") to assume Claude's competence.

Fix the workflow numbering: define an explicit "Step 1"/"Step 2" or remove the dangling "skip to Step 2" and "1b" references so the sequence is unambiguous.

De-duplicate action discovery, which appears in both "Searching for actions" and "Popular actions" with overlapping membrane action list commands.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational with concrete commands, but the opening Toast overview ("streamline operations and improve the customer experience") and editorial phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding that could be trimmed.	3 / 5
Actionability	It provides copy-paste ready commands throughout (membrane login, connection ensure, action list/run, request) plus a thorough proxy flag table, with only minor redundancy between the "Searching for actions" and "Popular actions" sections and placeholder substitution left to the reader.	4 / 5
Workflow Clarity	The connection-readiness flow has explicit validation and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED then re-poll, check error fields), but the broader sequence has broken numbering — a dangling "skip to Step 2" with no defined Step 2 and a "1b" header with no "1a" — leaving minor clarity gaps.	4 / 5
Progressive Disclosure	With no bundle files present, all content lives inline in well-organized, clearly headed sections (Authentication, Connecting, Searching, Running, Proxy, Best practices); structure is good for a ~155-line skill, though the detailed connection-state machine and proxy flag table could optionally live in separate reference files.	4 / 5
	Total	15 / 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 correctly includes both a what and a when clause anchored on a distinctive domain name, but its action language ("Manage data, records, and automate workflows") is generic and the trigger phrasing lacks concrete synonyms. It is functional but could be sharpened with specific Toast capabilities.

Suggestions

Replace generic verbs with concrete Toast actions, e.g. "Create and look up orders, manage customers, and automate restaurant workflows."

Add natural trigger terms users would actually say, such as "point of sale", "POS", or "restaurant orders", alongside "Toast data".

Tighten the "Use when" clause to specific intents like "Use when the user wants to query or update Toast orders, customers, or restaurant operations."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Toast integration") but its actions — "Manage data, records, and automate workflows" — are generic rather than concrete Toast-specific operations, matching the anchor for naming a domain with minimal/generic actions.	2 / 5
Completeness	It has both a "what" ("Toast integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Toast data."), though the "when" trigger is generic and could be more specific, matching the anchor for having both with room for greater explicitness.	4 / 5
Trigger Term Quality	"Toast" is a relevant natural keyword a user would say, but the phrase "interact with Toast data" is generic and common synonyms (POS, point of sale, restaurant orders) are missing, matching the anchor for some relevant keywords missing variations.	3 / 5
Distinctiveness Conflict Risk	"Toast" is a distinctive niche (a restaurant POS system) with a distinct trigger term, giving minimal conflict risk, though the generic "Manage data, records" framing leaves minor overlap risk with broad data-management skills.	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/toast/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.