Name: flipkart
Rating: 64 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

flipkart

Flipkart integration. Manage Products, Carts, Orders. Use when the user wants to interact with Flipkart data.

Quality

76%

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

Quality

Content

75%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 body is a strongly actionable CLI reference with a well-sequenced, validated connection workflow. It loses points for an unnecessary introductory explanation of what Flipkart is and for lacking post-run validation on mutating operations.

Suggestions

Remove the opening paragraph explaining what Flipkart is; Claude already knows this, so lead directly with the integration overview.

Add a validation/verification step after running mutating actions (e.g., re-fetch the order/cart to confirm the change applied) to satisfy the feedback-loop requirement for destructive/batch operations.

Consider moving the detailed connection-state handling and proxy flag table into reference files to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient CLI reference, but it opens by explaining what Flipkart is ("Flipkart is an Indian e-commerce company similar to Amazon...") and includes filler like "Use action names and parameters as needed." that Claude does not need.	3 / 5
Actionability	Provides copy-paste-ready executable commands throughout (install, login, connection ensure, action list/run, request) plus a complete proxy flag table, covering the common cases concretely.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit validation and feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED, check error field), but action-running has no post-run validation for potentially mutating cart/order operations.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with no bundle files present; over 50 lines so it cannot hit the simple-skill 5, and the proxy/connection detail could plausibly live in separate references.	4 / 5
	Total	16 / 20 Passed

Description

78%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 is concise and clearly scoped to Flipkart, covering what it does and when to use it with several concrete action areas. Its main weakness is the somewhat generic "Manage" verb and trigger phrasing that could enumerate more natural user phrases.

Suggestions

Replace the generic verb "Manage" with more specific actions per resource, e.g. "Search products, manage carts, and track orders".

Expand the "Use when" clause with concrete natural triggers, e.g. "Use when the user wants to search Flipkart products, manage their cart, or track orders."

Dimension	Reasoning	Score
Specificity	Lists several specific action areas ("Manage Products, Carts, Orders") beyond just naming the domain, though the shared verb "Manage" is somewhat generic and leaves minor coverage gaps (e.g., search, offers).	4 / 5
Completeness	Answers both what ("Manage Products, Carts, Orders") and when ("Use when the user wants to interact with Flipkart data"), but the trigger clause is fairly generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	Surfaces natural terms a user would say ("Flipkart", "Products", "Carts", "Orders") with good coverage, but misses common conversational variations like "my Flipkart cart" or "check my order".	4 / 5
Distinctiveness Conflict Risk	Targets a single named platform ("Flipkart") with platform-specific triggers, giving it a clear niche and minimal overlap with other skills.	5 / 5
	Total	17 / 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/flipkart/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.