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

incountry

InCountry integration. Manage data, records, and automate workflows. Use when the user wants to interact with InCountry 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/incountry/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 skill body is highly actionable with real CLI commands and a well-structured connection workflow including state feedback loops. Its main weaknesses are mild verbosity in the intro, inconsistent command prefixes and step numbering, and missing validation guidance around running actions.

Suggestions

Trim the opening explanatory paragraph to one line; Claude can infer what data residency is, so lead with what the skill does.

Normalize command invocations (use `membrane` or `npx @membranehq/cli` consistently) and renumber the workflow as a clean 1/2/3 list.

Add a validation checkpoint after running actions (e.g., check the `output`/`error` fields and confirm expected record counts) to push workflow clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening paragraph ("InCountry is a data residency-as-a-service platform... Companies that operate globally...") and some explanatory phrasing around clientAction could be tightened, fitting the score-3 anchor.	3 / 5
Actionability	Concrete executable commands are provided throughout (npm install, membrane login, connection ensure, action list/run, request) plus a flags table, but placeholders like CONNECTION_ID and an inconsistency (npx @membranehq/cli vs membrane) leave minor gaps, matching score 4.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-for-READY → search → run sequence is clear with feedback loops for connection states (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but action execution lacks result validation and step numbering is inconsistent ("Step 2" and "1b" without a clean 1/2/3), so it sits at score 4 rather than 5.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Best practices) in a single file with no nested references; reference-like material (flags table, clientAction schema) is inlined but the structure remains navigable, fitting score 4.	4 / 5
	Total	15 / 20 Passed

Description

66%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 clearly identifies a distinct product niche and includes an explicit use-trigger, but its action vocabulary is generic and its trigger terms are narrow. Tightening the listed actions and adding natural synonyms would lift specificity and trigger-term quality.

Suggestions

Replace generic verbs ("Manage data, records") with concrete InCountry-specific actions (e.g., "create, retrieve, and update records; find records by country; list audit logs").

Expand the trigger clause with natural user phrases and file/term synonyms, e.g. "Use when the user wants to query, create, or update InCountry records, work with country-specific data residency, or read audit logs."

Keep the third-person voice and current brevity; just make the "what" more comprehensive to push completeness toward 5.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the InCountry domain and 1-2 concrete actions, but the actions ("manage data", "manage records") are generic rather than comprehensive, so it does not reach score 4.	3 / 5
Completeness	It states a clear "what" ("Manage data, records, and automate workflows") and an explicit "Use when..." trigger ("when the user wants to interact with InCountry data"), so both are present; the when-clause could be more specific, matching score 4 rather than 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with InCountry data" offers the relevant keyword "InCountry data" but misses common variations and synonyms users might say (records, data residency, compliance), fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	"InCountry integration" names a specific product niche with distinct triggers, giving it minimal overlap risk with other skills, which fits the score-5 anchor.	5 / 5
	Total	15 / 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/incountry/SKILL.md
Commit: f484c82

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