Name: ekata
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ekata

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

Quality

65%

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/ekata/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 body is a well-structured, highly actionable CLI usage guide with clear connection-state checkpoints and feedback loops. Its weaknesses are some padded prose, placeholder-only examples without a worked end-to-end case, and slightly incoherent step numbering.

Suggestions

Trim marketing-style prose ('focus on the integration logic rather than auth plumbing', 'burn less tokens') to keep the body lean.

Fix the step numbering: add a labeled 'Step 2' target and either add a '1a' or renumber '1b' so the 'skip to Step 2' reference resolves.

Add one fully worked example with concrete values (a real intent and connectionId) so the action list/run flow is end-to-end copy-pasteable.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but includes padded prose such as 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens and make communication more secure' that Claude does not need, matching the mostly-efficient anchor with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxying with a flag table, matching the mostly-executable anchor; it is not a 5 because examples use placeholders (QUERY, CONNECTION_ID) without a fully worked end-to-end example.	4 / 5
Workflow Clarity	The install -> login -> connect -> poll-for-ready -> search -> run sequence has explicit state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and feedback loops (re-poll after user action), matching the clear-sequence anchor; it is not a 5 because step numbering is incoherent ('skip to Step 2' with no labeled Step 2, a '1b' with no '1a').	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (Overview, Connecting, Searching, Popular actions, Best practices) with no nested references, matching the good-structure anchor; it is not a 5 because the proxy flag table and clientAction state details could be split into a one-level-deep reference file for the moderately long body.	4 / 5
	Total	15 / 20 Passed

Description

62%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 uses third person and includes both a 'what' and a 'when' clause tied to a distinct named product. Its main weakness is generic action language and sparse trigger terms that miss the natural vocabulary of identity verification and fraud prevention.

Suggestions

Replace generic verbs with concrete Ekata capabilities, e.g. 'Verify customer identities, run fraud checks, and look up identity records'.

Expand the 'Use when' clause with natural trigger phrases such as 'identity verification', 'fraud prevention', or 'Ekata identity lookup'.

Mention the concrete record types/actions (e.g. Report, Investigation, Account) that the body already exposes.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the Ekata domain plus a couple of actions, but the actions are generic rather than concrete Ekata-specific operations (e.g. identity verification, fraud checks), matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states both a 'what' ('Ekata integration. Manage data, records, and automate workflows.') and a 'when' ('Use when the user wants to interact with Ekata data'), matching the anchor where both are present but the 'when' could be more explicit or specific; it is not a 5 because the trigger phrases are not concrete enough.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Ekata data' surfaces the 'Ekata' keyword but lacks natural synonyms a user would say (identity verification, fraud detection, identity lookup), matching the anchor with some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific SaaS 'Ekata' gives it a clear niche with low conflict risk, matching the mostly-distinct anchor; it is not a 5 because the surrounding actions ('manage data, records') are generic and the trigger phrasing is not sharply differentiated.	4 / 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/ekata/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.