Name: dukaan
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

dukaan

Dukaan integration. Manage Recordses. Use when the user wants to interact with Dukaan data.

Quality

68%

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

Quality

Content

76%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 highly actionable with concrete CLI commands covering the end-to-end flow, and is reasonably concise with good section structure. Its main weakness is workflow clarity: destructive CRUD operations lack validation/verification guidance, and a "Step 2" reference is dangling.

Suggestions

Add a validation/verification checkpoint before destructive action runs (e.g. read or list the target Record and confirm with the user before running a delete/update action).

Resolve the dangling "skip to Step 2" reference by labeling the subsequent section as Step 2 or removing the cross-reference.

Consider moving the proxy flags table and clientAction field schema into a separate reference file to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples with brief, justified explanations of Membrane-specific behavior (connection states, clientAction). Minor fluff like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" could be trimmed. It fits the efficient-with-minor-over-explanation anchor; not a 5 because of those padding phrases.	4 / 5
Actionability	It provides copy-paste-ready commands for the full flow — install, login, connection ensure, action list, action run (with JSON input), and request proxy — plus a flags table. Examples cover the common cases with clearly named placeholders. It matches the fully-executable anchor.	5 / 5
Workflow Clarity	The connection setup has a real sequence with checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the skill supports destructive CRUD on Records (create/update/delete) with no validation or verification step before running such actions, which caps this dimension at 3. The dangling "skip to Step 2" reference (no labeled Step 2 exists) is an additional gap; it is not a 4 because of the missing destructive-operation validation.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no broken or nested references, and no bundle files exist to misreference. It is not a 5 because at ~135 lines some inlined detail (the proxy flags table, clientAction schema) could live in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

61%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 identifies the Dukaan platform and includes an explicit "Use when" trigger, but its capability statement is vague and contains the awkward term "Recordses". Distinctiveness is strong due to the named platform, while specificity and trigger coverage are the weak points.

Suggestions

Replace "Manage Recordses" with concrete operations, e.g. "Create, read, update, delete, and list Records in Dukaan".

Fix the malformed noun "Recordses" to "Records" to match the entity name used in the body.

Broaden trigger terms beyond the platform name, e.g. "Use when the user wants to manage Dukaan Records, products, orders, or store data".

Dimension	Reasoning	Score
Specificity	The description names the domain ("Dukaan integration") and a single generic action ("Manage Recordses"), but lists no concrete operations like create/read/update/delete/list that the body actually supports. This matches the anchor where the domain is named but actions are minimal or generic; it is not a 3 because no distinct concrete actions are enumerated.	2 / 5
Completeness	Both parts are present: a (vague) "what" ("Manage Recordses") and an explicit "when" ("Use when the user wants to interact with Dukaan data"). The explicit trigger guidance prevents the cap at 3; it is not a 5 because the "what" is thin and lacks concrete trigger phrases beyond the platform name.	4 / 5
Trigger Term Quality	The phrase "Use when the user wants to interact with Dukaan data" supplies the natural keyword "Dukaan" and a reasonable trigger phrase, but offers no synonyms or variations. It fits the anchor for some relevant keywords missing common variations; it is not a 4 because coverage is limited to the single proper noun.	3 / 5
Distinctiveness Conflict Risk	"Dukaan" is a specific named platform, giving the skill a clear niche with distinct triggers and minimal overlap risk with other skills. It is not a 4 because the proper-noun trigger is uniquely distinguishing.	5 / 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/dukaan/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.