Name: imagekitio
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

imagekitio

ImageKit.io integration. Manage Images, Folders, Users. Use when the user wants to interact with ImageKit.io data.

Quality

61%

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

Quality

Content

61%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 well-structured, actionable guide built around concrete Membrane CLI commands and a useful actions table, with a solid validated connection-setup workflow. It loses points for a marketing-fluff intro, missing validation before destructive/batch actions, and a slightly mismatched step-numbering ('1b', 'Step 2') that breaks the sequence.

Suggestions

Add an explicit validation/confirmation checkpoint before running destructive or batch actions (e.g., 'Before delete-file or bulk-delete-files, confirm the target file IDs with the user and verify via get-file-details').

Cut the marketing intro paragraph and the thin Overview bullet list; lead with the integration task rather than what ImageKit.io is.

Fix the broken step numbering (the '1b. Wait for the connection' and 'Step 2' references have no matching '1a'/'Step 1'/'Step 2' labels) so the connection workflow reads as a coherent numbered sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and tables, but the marketing-style intro ('cloud-based image and video optimization and delivery platform... helps developers and marketers...') and the thin 'ImageKit.io Overview' bullet list pad tokens with content Claude does not need, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands for install, login, connection ensure, action list/run, and proxy requests plus a populated popular-actions table, with only minor gaps (CONNECTION_ID placeholders, generic proxy path), matching 'mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with explicit state-based validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and polling), but destructive and batch operations (delete-file, bulk-delete-files) appear in the actions table with no validation or confirmation checkpoint before running, which caps workflow clarity at 3 per the batch/destructive rule.	3 / 5
Progressive Disclosure	No bundle files exist and the single file is well-organized with clear section headers (Overview, Working with ImageKit.io, Install, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices); at ~155 lines with the actions and proxy-options tables inlined there are minor organization gaps, fitting 'good structure; most content appropriately placed'.	4 / 5
	Total	14 / 20 Passed

Description

62%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 cleanly states both what the skill does and when to use it in third-person voice, and its product-specific naming keeps conflict risk low. Its main weakness is generic 'Manage' wording and a slightly circular trigger phrase rather than concrete, varied trigger terms.

Suggestions

Replace the generic verb 'Manage' with specific actions a user would request (e.g., 'upload, transform, organize, and purge images and folders; manage users and tags').

Broaden the trigger with natural variations and entities users actually say (e.g., 'Use when the user wants to upload, optimize, transform, tag, or manage images, folders, or media assets in ImageKit.io').

Add concrete trigger nouns/synonyms (media library, CDN cache purge, file metadata) to raise distinctiveness and trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (ImageKit.io) and lists three concrete entities ('Manage Images, Folders, Users'), but the verb 'Manage' is generic and the actions are not comprehensive, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	Both 'what' ('ImageKit.io integration. Manage Images, Folders, Users.') and 'when' ('Use when the user wants to interact with ImageKit.io data.') are present, but the 'when' is somewhat tautological and the 'what' uses a generic verb, so it is not the explicit, concrete-trigger level 5.	4 / 5
Trigger Term Quality	Includes relevant keywords ('ImageKit.io', 'Images', 'Folders', 'Users', 'interact with ImageKit.io data') but the trigger is largely the product name repeated with no synonyms or file-extension variations, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named SaaS product (ImageKit.io) giving a clear niche with low conflict risk, but generic image-management wording leaves minor overlap with other image-handling skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	14 / 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/imagekitio/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.