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

Blog Docs Log in Get started

imgix

Imgix integration. Manage Accounts. Use when the user wants to interact with Imgix 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/imgix/SKILL.md

Quality

Content

75%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 highly actionable with concrete, executable membrane commands and a well-structured connection workflow including state polling. Its main weaknesses are a padded introductory paragraph and missing validation/feedback loops for the destructive actions it exposes.

Suggestions

Trim the opening 'Imgix is an image processing and delivery service...' paragraph and the vague 'When to use which actions' line, since Claude already knows this.

Add an explicit validation step for destructive actions (e.g. verify asset state after `purge-asset` / `unpublish-asset`, or list assets to confirm a batch result).

Clarify error recovery for CONFIGURATION_ERROR/SETUP_FAILED with a concrete re-try or inspect step rather than just 'check the error field'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands throughout, but the opening paragraph explains what Imgix is ('image processing and delivery service...') and 'When to use which actions: Use action names and parameters as needed.' is filler Claude does not need.	3 / 5
Actionability	Copy-paste-ready membrane commands cover install, login, connection ensure/get, action list, action run, and proxy requests, plus a Popular actions table with concrete keys and a proxy flags table.	5 / 5
Workflow Clarity	The connect-to-ready flow is clearly sequenced with explicit state polling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a CONFIGURATION_ERROR branch; minor gaps are the bare 'check the error field' recovery and no validation loop for destructive actions like purge/unpublish.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references; the 16-row Popular actions table is borderline bulk inline but reasonable as a quick-reference, and no external bundle files exist to warrant separate files.	4 / 5
	Total	16 / 20 Passed

Description

52%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 names a distinct service and includes a usable trigger clause, but its capability statement is too thin and generic ('Manage Accounts') to convey what the skill concretely does. Broadening the action list and adding natural synonyms (images, assets, CDN) would lift specificity and trigger quality.

Suggestions

Replace the generic 'Manage Accounts' with concrete capabilities, e.g. 'Manage Imgix assets, sources, upload sessions, and cache purging'.

Expand trigger terms with natural synonyms users say, such as 'images, image delivery, CDN, Imgix assets, or Imgix sources'.

Make the 'when' clause more specific than 'interact with Imgix data' — e.g. 'Use when the user wants to list, upload, publish, purge, or update Imgix assets and sources.'

Dimension	Reasoning	Score
Specificity	Names the Imgix domain but the only action verb is the generic 'Manage Accounts'; there are no concrete actions covering assets, sources, uploads, or purging, matching the 'actions are minimal or generic' anchor.	2 / 5
Completeness	A 'when' clause is present ('Use when the user wants to interact with Imgix data'), but the 'what' is weak — 'Imgix integration. Manage Accounts' is vague and not comprehensive, so it falls below the clear-what/clear-when anchor.	3 / 5
Trigger Term Quality	The brand keyword 'Imgix' and the phrase 'interact with Imgix data' are relevant, but no synonyms, related terms (images, assets, CDN), or natural variations are included.	3 / 5
Distinctiveness Conflict Risk	The named service 'Imgix' is a specific niche with distinct triggers, giving minimal conflict risk with other skills.	5 / 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/imgix/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.