Name: kiotviet
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

kiotviet

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

Quality

66%

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/kiotviet/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 body is a tight, highly executable guide to driving KiotViet through the Membrane CLI, with strong command examples and a well-validated connection workflow. Its main weakness is the absence of validation guidance for the destructive Records CRUD operations that are the skill's stated purpose.

Suggestions

Add a validation/verification step before destructive Records operations (e.g., list/read the record to confirm the ID before delete, and verify the response state), so the destructive workflow clears the workflow_clarity cap.

Consider moving the verbose connection-state machine (CLIENT_ACTION_REQUIRED sub-states, proxy flag table) into a reference file and summarizing inline, to tighten the main body further.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven, with only minor padding such as "This is the fastest way to get a connection" and "so you can focus on the integration logic rather than auth plumbing" that could be trimmed, matching the efficient-with-minor-over-explanation anchor.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout — login, connection ensure/get with --wait, action list/run with --input JSON, and a proxy request path with a full flag table — covering the common cases concretely.	5 / 5
Workflow Clarity	The connection setup sequence is well-validated with state polling and READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR branches, but the skill's core purpose includes destructive Records operations (create/update/delete) with no validation or verification guidance, triggering the destructive-operations cap at 3.	3 / 5
Progressive Disclosure	Content is organized into clear, logically ordered sections with no nested references and no bundle files present; it is slightly over the 50-line simple-skill threshold, and the dense connection-state machine and proxy flag table could conceivably live in references, leaving minor organization gaps.	4 / 5
	Total	16 / 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 correctly includes an explicit "Use when" trigger and pins a distinct platform, but its capability statement is thin and contains a malformed term ("Recordses"). It conveys intent adequately while lacking concrete action coverage.

Suggestions

Replace the generic "Manage Recordses" with concrete actions, e.g. "Create, read, update, delete, and list Records (products, orders, inventory) in KiotViet", fixing the "Recordses" typo.

Expand trigger terms with natural user phrasing and entity names, e.g. "Use when the user wants to manage KiotViet data — products, orders, invoices, inventory, or customer records."

Dimension	Reasoning	Score
Specificity	It names the domain ("KiotViet integration") but the only action verb is the generic "Manage Recordses" — a single, non-comprehensive action that is also malformed ("Recordses" rather than "Records"), so it sits between naming the domain and naming concrete actions, noticeably below the midpoint.	2 / 5
Completeness	Both "what" ("KiotViet integration. Manage Recordses.") and "when" ("Use when the user wants to interact with KiotViet data.") are explicitly present; the explicit "Use when" clause lifts it above 3, though the "what" is generic and the "when" could name concrete triggers.	4 / 5
Trigger Term Quality	"KiotViet" and the trigger phrase "interact with KiotViet data" give a relevant keyword a user would say, but coverage is thin with no synonyms, entity names (products/orders/inventory), or file extensions, matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	KiotViet is a specific platform giving the skill a clear niche with minimal conflict risk, but the generic "Manage Recordses" / "interact with data" phrasing leaves minor overlap risk with broad data-management skills.	4 / 5
	Total	13 / 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/kiotviet/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.