Name: bluecart-api
Rating: 49.6 (1 reviews)
Author: membranedev

bluecart-api

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

Quality

55%

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

Quality

Content

52%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 actionable Membrane CLI workflow is concrete and well-sequenced with good state-handling feedback, but it is buried under a massive, heavily duplicated overview list and marketing prose that wrecks token efficiency and structure.

Suggestions

Delete or move the ~700-line "BlueCart API Overview" (especially the repeated Compliance Policy entries) into a separate reference file, keeping SKILL.md a lean overview.

Add an end-to-end worked example with a real action key and real input JSON (e.g. searching Walmart products) instead of placeholder <actionId> and {'key': 'value'}.

Number the workflow steps explicitly and add a validation/confirmation note before destructive proxy requests (POST/PUT/DELETE).

Dimension	Reasoning	Score
Conciseness	Roughly 700 of the ~975 body lines are a "BlueCart API Overview" that enumerates entity names and repeats long "Compliance Policy" entries many times over, plus a marketing intro paragraph, making the file noticeably verbose and padded even though the usage sections are lean.	2 / 5
Actionability	The usage section gives copy-paste-ready commands (install, login, connection ensure, action list/run, request) with documented flags and a concrete popular-actions table, but the run/proxy examples use placeholder IDs and generic {'key':'value'} input rather than a complete end-to-end example with real parameters.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → search → run sequence with explicit state polling and a feedback loop for CLIENT_ACTION_REQUIRED, but step numbering is loose ("skip to Step 2" with no labeled Step 2) and destructive proxy calls (DELETE/PUT) lack validation guidance.	4 / 5
Progressive Disclosure	No bundle files exist and the body is monolithic, with the giant entity/policy enumeration inlined directly in SKILL.md where it clearly belongs in a separate file (or should be removed), matching the inlined-content-that-should-be-separate anchor.	2 / 5
	Total	12 / 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 cleanly answers what and when with a specific named API and an explicit trigger clause, but its capability wording is generic boilerplate shared across sibling skills and lacks concrete API operations or synonym coverage.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete BlueCart operations such as "search Walmart products, list categories, and get product details".

Add the natural synonyms users actually say (e.g. "Walmart", "products", "orders") to the trigger clause so the skill surfaces for those queries.

Differentiate from sibling Membrane API skills by stating what is unique to BlueCart rather than reusing the shared template phrasing.

Dimension	Reasoning	Score
Specificity	The description names the domain ("BlueCart API integration") but its actions ("Manage data, records, and automate workflows") are generic abstractions rather than concrete API operations like list orders or search products, matching the minimal/generic anchor.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with BlueCart API data") are present, but the "what" is vague and the "when" could name more specific trigger phrases, fitting the both-present-but-could-be-tighter anchor.	4 / 5
Trigger Term Quality	It surfaces the core term "BlueCart API" / "BlueCart API data" in a natural trigger clause, but misses common variations and synonyms a user might actually say (e.g. Walmart, products, orders), so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ("BlueCart API") gives it a clear niche with minimal conflict, but the boilerplate phrasing overlaps with sibling Membrane API skills that share the identical "Manage data, records, and automate workflows" template, leaving minor overlap risk.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (975 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/bluecart-api/SKILL.md
Commit: f484c82

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