Name: imagga
Rating: 48 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

imagga

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

Quality

51%

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

Quality

Content

65%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 executable commands and a clear connection workflow, but it does not validate destructive actions and inlines reference material that would benefit from separate files. Mild over-explanation slightly reduces token efficiency.

Suggestions

Add a validation/verification step before destructive actions such as delete-upload (e.g. confirm the upload ID exists and prompt before deletion) to lift the workflow-clarity cap.

Move the popular-actions table and proxy flag reference into a separate reference file and link to it from SKILL.md to improve progressive disclosure.

Trim the marketing-style overview paragraph about who uses Imagga, keeping only what Claude needs to choose the right action.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands, but includes some unnecessary framing (the e-commerce/advertising usage paragraph and "rather than auth plumbing") that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready CLI commands for every stage — install, login, connection ensure, action list/run, and proxy requests — with flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear with state-polling branches, but destructive operations like delete-upload have no validation or feedback loop, which caps this skill at 3 per the destructive/batch rule.	3 / 5
Progressive Disclosure	No bundle files exist and all content (including the popular-actions table and proxy reference) is inlined in one file with headers; structure is present but content that could be split out is not.	3 / 5
	Total	14 / 20 Passed

Description

37%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 Imagga and includes a usable trigger clause, but the capability description is generic boilerplate ("manage data, records, automate workflows") that does not reflect Imagga's actual image-recognition actions. It is distinguishable mainly because the app name is unique.

Suggestions

Replace "Manage data, records, and automate workflows" with Imagga's concrete capabilities, e.g. "Tag, categorize, crop, and moderate images, extract text (OCR), colors, and faces."

Add natural trigger terms users would say, such as image tagging, auto-cropping, content moderation, OCR, or image categorization.

Tighten the trigger clause to reference these image-analysis tasks so it does not read as a generic data-management skill.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Imagga domain but the actions are minimal and generic, matching the score-2 anchor rather than the more concrete score-3.	2 / 5
Completeness	It has an explicit "Use when the user wants to interact with Imagga data" trigger, but the "what" ("Manage data, records, and automate workflows") is vague, so what-and-when is present but what is weak.	3 / 5
Trigger Term Quality	The only natural keyword is "Imagga"; "interact with Imagga data" is generic and lacks the natural phrases or synonyms users would say, fitting between no-keywords and partial-coverage.	2 / 5
Distinctiveness Conflict Risk	Naming a specific app (Imagga) gives it a niche with low conflict risk, but the generic "manage data, records, automate workflows" boilerplate keeps it from being fully distinct.	3 / 5
	Total	10 / 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/imagga/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.