CtrlK
BlogDocsLog inGet started
Tessl Logo

nhanh-vn

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

55

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nhanh-vn/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 delivers concrete, executable Membrane CLI guidance with a clear connection state-machine, but suffers from broken step numbering and no validation/verification for the destructive CRUD operations it advertises. Organization is solid for a single-file skill though some detail could be offloaded to references.

Suggestions

Add a validation/verification step after running destructive actions (e.g. re-list or get the record to confirm the create/update/delete succeeded, and check the response error field).

Fix the dangling cross-references: label a real "Step 2" (Searching for actions) and rename "1b" to a consistent step number so "skip to Step 2" resolves.

Consider moving the detailed clientAction state-machine and the proxy flags table into a reference file, keeping SKILL.md as a concise overview with one-level-deep links.

DimensionReasoningScore

Conciseness

The body is mostly lean executable commands with brief explanations, but contains minor editorializing such as "so you can focus on the integration logic rather than auth plumbing" that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

It provides concrete, runnable CLI commands (login, connection ensure, action run, request) plus a flags table, but placeholders like <agentType>, CONNECTION_ID, and QUERY must be substituted and no fully worked end-to-end example is given, matching the 'mostly executable guidance; minor gaps' anchor.

4 / 5

Workflow Clarity

The connection flow is sequenced with polling checkpoints, but destructive record operations (create/update/delete) lack any validation or verification step and the numbering is broken ("skip to Step 2" with no Step 2; "1b" with no "1a"), so the destructive-operation validation cap applies.

3 / 5

Progressive Disclosure

It is a single well-sectioned file (Overview, Authentication, Connecting, Searching, Proxy, Best practices) with no nested references and no bundle files, giving good structure with minor organization gaps rather than the clean overview-to-details split of the top anchor.

4 / 5

Total

15

/

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 pairs a what with a Use-when trigger in third person, but its capability list is sparse and generic ("Manage Recordses") and the natural-keyword coverage is narrow. It is distinct thanks to the Nhanh niche yet underdeveloped on specificity and trigger synonyms.

Suggestions

Replace the generic "Manage Recordses" with concrete actions, e.g. "Create, read, update, delete, and list Records in Nhanh".

Broaden trigger terms to include natural variations a user might say, such as "Nhanh.vn orders, products, or inventory data".

Fix the malformed plural "Recordses" to the correct entity name to avoid ambiguity.

DimensionReasoningScore

Specificity

The phrase "Manage Recordses" names the Nhanh domain and the records entity but offers only one generic action verb, matching the anchor 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

It states a what ("Nhanh integration. Manage Recordses.") and a when ("Use when the user wants to interact with Nhanh data"), but the what is thin rather than comprehensive, fitting the 'has both what and when; when could be more explicit or specific' anchor.

4 / 5

Trigger Term Quality

"Nhanh" and "Nhanh data" plus the natural "Use when the user wants to interact with Nhanh data" clause give some relevant keywords, but no synonyms or file extensions are present, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Nhanh is a specific platform niche with a distinct trigger, giving mostly distinct behavior with minor overlap risk against other integration skills, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.