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

Blog Docs Log in Get started

nango

Nango integration. Manage Connections, Users, Groups. Use when the user wants to interact with Nango 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/nango/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 highly actionable with executable commands and a well-sequenced, validated connection workflow. It loses points mainly to a redundant intro/action-list section and some background explanation Claude does not need.

Suggestions

Remove the redundant "Popular actions" section (it repeats the action-list command) and drop the introductory background paragraph about what Nango is, since Claude already knows this.

Fix the broken step numbering ("skip to Step 2" / "1b" with no clearly labeled Step 1/2) so the multi-step workflow is unambiguous.

Standardize invocation — pick either `membrane` or `npx @membranehq/cli@latest` consistently rather than mixing both across sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-dense and efficient, but includes background prose Claude already knows ("Nango is an integration platform for SaaS applications...") and a redundant "Popular actions" section that repeats the action-list command already shown in "Searching for actions".	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (install, login, connection ensure, action run, request) with flag tables and JSON examples; the only gaps are placeholder substitution (<actionId>, CONNECTION_ID) and an inconsistent membrane vs npx invocation.	4 / 5
Workflow Clarity	A clear install → authenticate → connect → poll-for-ready → search → run sequence exists with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-user-action feedback loop; only minor gaps remain from inconsistent Step numbering and the duplicated action-search sections.	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives in SKILL.md, but it is well-organized into clearly headed sections (Overview, Authentication, Connecting, Searching, Proxy, Best practices) with nothing that clearly belongs in a separate file.	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 answers both what and when with an explicit trigger clause and is anchored to a distinct product niche. Its main weakness is thin action vocabulary (one generic "Manage" verb) and keyword coverage limited to the product name.

Suggestions

Replace the single verb "Manage" with 2-3 distinct concrete actions (e.g., "Create and authenticate Connections, browse Users, and list Groups") to lift specificity.

Expand the trigger clause with concrete natural phrases users would say, e.g. "Use when the user wants to connect to Nango, query Nango data, or manage Nango Connections, Users, or Groups."

Add common synonyms/extensions (e.g. "Nango connections", "Nango API") so the trigger matches more natural phrasings.

Dimension	Reasoning	Score
Specificity	"Manage Connections, Users, Groups" names the domain plus three concrete entities, but relies on a single generic verb ("Manage") rather than distinct concrete actions, matching the 1-2-action anchor more than the multi-action anchor.	3 / 5
Completeness	Both a clear "what" ("Nango integration. Manage Connections, Users, Groups.") and an explicit "when" ("Use when the user wants to interact with Nango data.") are present, though the "when" clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	"Nango" and "interact with Nango data" are relevant keywords but coverage is essentially just the product name with no synonyms or common variations, fitting the "some keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the specific product "Nango" gives it a clear niche with low conflict risk, but "Connections, Users, Groups" are generic entity names that could overlap with adjacent skills, keeping it just below the minimal-conflict anchor.	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/nango/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.