Name: alttextai
Rating: 49.6 (1 reviews)
Author: membranedev

alttextai

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

Quality

54%

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/alttextai/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 well-structured, mostly executable guide to driving AltText.ai through the Membrane CLI, with a clear sequenced workflow and state-based checkpoints. It loses points to a marketing-fluff intro and missing concrete examples of the core alt-text generation task.

Suggestions

Cut the marketing intro (who uses AltText.ai and why) — Claude already knows what alt text is for.

Fill in the empty Description column in the Popular actions table and add one concrete `membrane action run generate-alt-text` example with a real `--input` payload.

Add a brief verification note after running an action (e.g. check the `output` field / error state) to close the workflow loop.

Dimension	Reasoning	Score
Conciseness	The bulk is tight, executable command blocks, but the opening marketing paragraph ("It's used by website owners, bloggers, and e-commerce businesses to optimize their online content") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready membrane commands with concrete flags for install, auth, connection, action listing/running, and proxying, but the Popular actions table has empty descriptions and there is no concrete example of the core task (generating alt text) with real input parameters.	4 / 5
Workflow Clarity	The install → auth → connect → wait → search → run sequence is clear, and the connection-state handling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) with re-polling acts as explicit checkpoints and a feedback loop, though no post-run verification of action output is specified.	4 / 5
Progressive Disclosure	The body is a single self-contained file with well-organized section headers and no bundle files to reference, but the thin "Overview" list and the Popular actions table with blank descriptions leave minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

41%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 signals its niche via the AltText.ai brand and includes a "Use when" clause, but it describes the skill with vague, generic action language and omits the natural alt-text/SEO/accessibility trigger terms a user would actually say.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Generate alt text for images, search and list images, scrape pages for images."

Add natural trigger terms users say — "alt text", "image alt text", "SEO", "accessibility" — to the Use when clause.

Make the "what" explicit (e.g. "automatically generate alt text for images") instead of "Manage data, records, and automate workflows".

Dimension	Reasoning	Score
Specificity	The description names the domain ("AltText.ai integration") but the stated actions are generic and abstract — "Manage data, records, and automate workflows" — with no concrete capabilities like generating alt text or processing images.	2 / 5
Completeness	Both a "what" and an explicit "Use when..." trigger are present, but the "what" is vague ("Manage data, records, and automate workflows") and does not clearly state the skill's real function, so it sits below the both-clear level.	3 / 5
Trigger Term Quality	It relies on generic terms ("data", "records", "workflows") and omits the natural phrases users would actually say ("alt text", "image alt text", "SEO", "accessibility"), offering only one or two generic keywords.	2 / 5
Distinctiveness Conflict Risk	The AltText.ai brand name carves a clear niche and a brand-specific trigger, with only minor overlap risk from the generic action verbs ("manage data", "records", "workflows").	4 / 5
	Total	11 / 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/alttextai/SKILL.md
Commit: f484c82

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