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

Blog Docs Log in Get started

krayin

Krayin integration. Manage data, records, and automate workflows. Use when the user wants to interact with Krayin 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/krayin/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 content is a well-structured, command-first integration guide with a clear sequenced connection workflow and explicit state-machine checkpoints. It is highly actionable and mostly lean; the only notable drag is marketing prose in the intro and slightly thin worked examples in the action-discovery section.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, copy-paste CLI commands and a compact flags table; the main over-explanation is the marketing-style intro ('businesses of all sizes looking for a customizable and scalable solution') that could be trimmed, keeping it just below a 5.	4 / 5
Actionability	It provides concrete, executable commands for install, login, connection ensure/get, action list/run, and request proxying, including a real JSON-input example; minor gaps (pervasive placeholders like CONNECTION_ID/<actionId> and a thin 'Popular actions' section that just repeats the discovery command) hold it at 4 rather than 5.	4 / 5
Workflow Clarity	The connection flow is a well-sequenced state machine with explicit checkpoints (READY skip, BUILDING poll, CLIENT_ACTION_REQUIRED subtypes, CONFIGURATION_ERROR/SETUP_FAILED error checks) and a re-poll feedback loop; validation is thinner on the action-run and proxy steps, leaving minor gaps.	4 / 5
Progressive Disclosure	With no bundle files present, all content lives in one SKILL.md organized into clear, logically ordered sections with no nested references; structure is good and navigation is easy, though some detail (e.g. the full connection state machine or proxy flag reference) could be externalized.	4 / 5
	Total	16 / 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 is competent — it states the domain, lists a few actions, and includes an explicit 'Use when' trigger — but the actions are generic verbs rather than Krayin-specific operations, and trigger coverage is thin on synonyms and entity names. It is clearly distinct thanks to the named platform but leaves room to be more concrete and trigger-rich.

Suggestions

Replace the generic verbs with Krayin-specific actions, e.g. 'Create and update leads, deals, persons, and organizations; automate workflows.' to lift specificity.

Broaden trigger coverage with natural variations users would actually say — 'Krayin CRM', 'Krayin store', 'leads', 'deals', 'contacts' — so differently-phrased requests still match.

Tighten the 'when' clause to name concrete triggers (e.g. 'Use when the user wants to manage Krayin CRM leads, deals, contacts, or organizations') to further reduce overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain plus a couple of actions, but the verbs are generic ('manage', 'automate') rather than concrete Krayin-specific operations like creating leads or updating deals.	3 / 5
Completeness	Both 'what' ('Krayin integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Krayin data.') are present; the 'when' is explicit but could be more specific, matching the anchor rather than the level-5 concrete-trigger examples.	4 / 5
Trigger Term Quality	It surfaces 'Krayin' and 'Krayin data' as the trigger, but offers little variation or synonyms — a user saying 'Krayin CRM', 'Krayin store', or naming entities (leads/deals) would not be matched by additional keywords.	3 / 5
Distinctiveness Conflict Risk	Krayin is a named platform, so 'interact with Krayin data' is a mostly-distinct trigger with minimal conflict risk, though the generic 'manage data, records, and automate workflows' phrasing could overlap with other CRM/data-integration skills.	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/krayin/SKILL.md
Commit: f484c82

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