Name: nano-nets
Rating: 61.6 (1 reviews)
Author: membranedev

nano-nets

Nano Nets integration. Manage Organizations, Projects, Activities, Notes, Files, Users and more. Use when the user wants to interact with Nano Nets data.

Quality

72%

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/nano-nets/SKILL.md

Quality

Content

82%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 highly actionable with executable commands throughout and a well-validated connection state-machine workflow, organized into clear sections. Its main weaknesses are a dangling "Step 2" reference, missing error-recovery guidance for action runs, and a few marketing-flavored sentences.

Suggestions

Fix the dangling "skip to Step 2" reference by renumbering the connect/wait sections into an explicit Step 1 / Step 2 sequence.

Add an error-recovery note for `membrane action run` failures (e.g., inspect the `error` field, retry, or fall back to `membrane request` proxy) to complete the feedback loop.

Trim the marketing line about "focus on the integration logic rather than auth plumbing" and the "used by IT professionals" framing to tighten the intro.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with brief explanations, but the intro marketing line ("so you can focus on the integration logic rather than auth plumbing") and the "who uses it" sentence are minor over-explanation that could be trimmed, fitting the 4 anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests with a full flag table, covering the common cases with executable guidance.	5 / 5
Workflow Clarity	The connect-then-run flow has a clear sequence with validation checkpoints (polling for READY, handling CLIENT_ACTION_REQUIRED branches), but "skip to Step 2" references a non-existent Step 2 and action-run failures have no error-recovery guidance, so it stays below 5.	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives in one file, but it is well-organized with clear section headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and no nested references, matching the 4 anchor for good structure with minor organization gaps.	4 / 5
	Total	17 / 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 covers what and when in third-person voice with a named-product trigger, but the action vocabulary is a single generic verb and the trigger phrase is thin. It is solid but not exemplary, landing around the mid-upper band.

Suggestions

Replace the single generic verb "Manage" with several concrete actions (e.g., "Create, list, update, and delete Organizations, Projects, Activities, Notes, Files, and Users") to lift specificity.

Expand the trigger phrase with natural user phrasing, e.g. "Use when the user wants to query, create, or update Nano Nets records, or mentions Nano Nets organizations, projects, or activities."

Drop "and more" or replace it with the remaining concrete entities so coverage reads as complete rather than open-ended.

Dimension	Reasoning	Score
Specificity	It names the domain and a concrete verb ("Manage Organizations, Projects, Activities, Notes, Files, Users"), but only one generic action verb is used and "and more" is vague, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It states both what ("Manage Organizations, Projects, Activities, Notes, Files, Users") and when ("Use when the user wants to interact with Nano Nets data"), but the when clause is generic rather than concrete trigger phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	The only trigger phrase is "Use when the user wants to interact with Nano Nets data," which surfaces the product name but lacks natural variations or synonyms a user might say, matching the 3 anchor.	3 / 5
Distinctiveness Conflict Risk	"Nano Nets" is a specific named product, giving a clear niche with minimal conflict risk, though the entity list is generic enough to leave minor overlap risk, fitting the 4 anchor better than 5.	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/nano-nets/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.