Name: asin-data-api
Rating: 55.2 (1 reviews)
Author: membranedev

asin-data-api

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

Quality

62%

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/asin-data-api/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, actionable guide to driving the ASIN Data API through the Membrane CLI, with a clear state-driven connection workflow and copy-paste-ready commands. Its main weakness is conciseness — background prose and an inline field taxonomy add tokens Claude does not strictly need.

Suggestions

Trim the introductory paragraph about who uses the API and use cases (market analysis, competitive research); Claude does not need the pitch.

Move the nested ASIN data-field taxonomy (Title, Brand, UPC, Listing Health, etc.) into a references/ file and link to it from the overview to keep SKILL.md lean.

Add one concrete end-to-end example, e.g. looking up a product by ASIN with a real action name and input, so the generic membrane commands connect to an actual ASIN use case.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph ('used by e-commerce businesses, researchers, and developers... market analysis, competitive research...') is background padding Claude does not need, and some prose could be tightened.	3 / 5
Actionability	It provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request with a flags table), with only minor gaps such as placeholder CONNECTION_ID/actionId values and no concrete example of a real ASIN query.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, though step numbering is slightly loose ('skip to Step 2' without a clean enumerated Step 1/2).	4 / 5
Progressive Disclosure	The body is well-organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files; the inline data-field taxonomy is the one block that could justify a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

57%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 has an explicit 'Use when' trigger and a distinct niche, but its action language is generic and padded with buzzwords rather than naming concrete ASIN-related capabilities. Trigger-term coverage is thin and lacks common synonyms users would actually say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions, e.g. 'Look up Amazon product data by ASIN — pricing, reviews, sales rank, listing health, and inventory.'

Add natural trigger terms users would say, such as 'Amazon product data', 'ASIN lookup', 'product pricing/reviews', or 'Buy Box price'.

Drop the buzzword 'automate workflows', which over-claims and adds overlap risk without naming a concrete capability.

Dimension	Reasoning	Score
Specificity	The description names the domain ('ASIN Data API integration') but its actions are generic buzzwords — 'Manage data, records, and automate workflows' — rather than concrete capabilities like looking up pricing, reviews, or sales rank by ASIN.	2 / 5
Completeness	It states both a 'what' ('ASIN Data API integration. Manage data, records...') and an explicit 'when' ('Use when the user wants to interact with ASIN Data API data.'), though the 'when' trigger is single and could be more specific.	4 / 5
Trigger Term Quality	It repeats 'ASIN Data API' and the trigger 'interact with ASIN Data API data', but misses common natural variations a user would say such as 'Amazon product data', 'ASIN lookup', 'product pricing', or 'reviews'.	3 / 5
Distinctiveness Conflict Risk	'ASIN Data API' is a clear niche with minimal conflict risk, but the generic 'manage data, records, and automate workflows' phrasing introduces minor overlap with other data-handling skills.	4 / 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/asin-data-api/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.