Name: gorgias
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

gorgias

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

Quality

63%

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

Quality

Content

78%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 clear connection-state workflow including a polling loop, though it lacks a destructive-operation validation step and uses no progressive-disclosure bundle files. Conciseness is strong with only minor padding in the intro.

Suggestions

Add an explicit validation/check step before running batch or destructive actions (e.g. confirm target ticket IDs or dry-run before bulk updates) to close the workflow checkpoint gap.

Move the detailed clientAction handling and proxy options into a reference file under references/ and link to it from the body to improve progressive disclosure.

Trim the opening 'Gorgias is a customer service platform...' paragraph, which restates general knowledge Claude already has, to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient executable commands and a tight options table, assuming Claude's competence; only minor over-explanation (e.g. the opening paragraph on what Gorgias is) could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready, executable CLI commands for install, login, connection ensure, polling, action list/run, and proxy, plus a concrete flags table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling feedback loop, but there is no validation step for destructive or batch action runs, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	Structure is reasonable with section headers, but no bundle files exist and all content is inlined in one file with no clearly signaled one-level references; content that could be split (e.g. full clientAction handling, proxy reference) stays inline.	3 / 5
	Total	16 / 20 Passed

Description

48%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 names Gorgias and includes a 'Use when' trigger, but its action language is generic ('Manage data, records, and automate workflows') rather than concrete Gorgias capabilities, capping specificity and completeness. It is distinct but could be much sharper.

Suggestions

Replace generic verbs with concrete Gorgias actions, e.g. 'Search and manage tickets, messages, and users, and run or proxy Gorgias API actions.'

Add natural trigger synonyms users actually say, e.g. 'Use when the user wants to work with Gorgias tickets, customer support conversations, or Gorgias API endpoints.'

Tighten the 'what' so it explicitly enumerates ticket/message/user management rather than the abstract 'data, records'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Gorgias) but the actions are generic ('Manage data, records, and automate workflows') — these are minimal and not tied to concrete Gorgias capabilities like tickets, messages, or users.	2 / 5
Completeness	It has an explicit 'Use when...' clause giving a 'when', but the 'what' ('Manage data, records, and automate workflows') is vague, so the pair is present yet only weakly concrete rather than the clear-both anchor at 4-5.	3 / 5
Trigger Term Quality	It includes the natural term 'Gorgias' and a reasonable trigger phrase ('interact with Gorgias data'), but lacks common variations or domain-specific synonyms a user might say (e.g. tickets, support, customer service, e-commerce).	3 / 5
Distinctiveness Conflict Risk	The Gorgias name is a distinct niche with its own trigger ('Gorgias data'), giving mostly distinct triggers with only minor overlap risk against other generic data-management 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/gorgias/SKILL.md
Commit: f484c82

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