Name: nets-group
Rating: 55.2 (1 reviews)
Author: membranedev

nets-group

Nets Group integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nets Group data.

Quality

62%

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

Quality

Content

75%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 copy-paste-ready Membrane commands and a clear connection-state workflow including feedback loops. It would benefit from trimming introductory padding and adding an explicit verification step for proxy/batch operations.

Suggestions

Trim the opening Nets Group overview paragraph and phrases like 'you can focus on the integration logic rather than auth plumbing' to save tokens.

Add an explicit verification step after proxy/batch requests, e.g. check the response status and confirm row counts before proceeding, to satisfy the destructive/batch feedback-loop requirement.

Consider moving the proxy flag reference table into a separate REFERENCE.md and linking to it, keeping SKILL.md as a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what Nets Group does and a few padded phrases ('This will burn less tokens', 'you can focus on the integration logic rather than auth plumbing') are unnecessary context Claude largely already has.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case — install, login, connection ensure, polling, action list/run with JSON input, and a complete proxy flag table — covering the main workflow end to end.	5 / 5
Workflow Clarity	The install→auth→connect→wait→search→run sequence is clear with explicit state-handling feedback loops (BUILDING polling, CLIENT_ACTION_REQUIRED re-poll, error states), but proxy/batch operations lack an explicit post-call verification step, which caps it below 5.	4 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections with no nested references, and the proxy flag table is reasonably scoped; the API-detail material is inlined rather than split into a separate file, leaving a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

50%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 names a distinct vendor niche, but its capability verbs are generic and its trigger terms lack natural synonyms or file extensions. Tightening the action list with concrete operations and richer keywords would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Search payments, manage payouts and merchants, retrieve reports, and proxy custom Nets Group API requests.'

Add natural trigger terms and synonyms users would actually say, such as 'Nets Group payments, payouts, merchants, transactions, or Nets API requests'.

Keep the explicit 'Use when' clause but expand the trigger to mention the specific Nets Group resources (Payment Requests, Payouts, Merchants, Reports) for clearer routing.

Dimension	Reasoning	Score
Specificity	Names the Nets Group domain and lists 'Manage data, records, and automate workflows', but the verbs are generic ('Manage', 'automate') rather than concrete actions — matching the 'names domain but actions minimal/generic' anchor rather than score 3's clearly concrete actions.	2 / 5
Completeness	It states what it does ('Manage data, records, and automate workflows') and gives an explicit when ('Use when the user wants to interact with Nets Group data'), satisfying both halves; the 'when' is explicit but the 'what' is generic and lacks concrete trigger phrases, so it does not reach the fully-concrete anchor 5.	4 / 5
Trigger Term Quality	Only 'Nets Group', 'data', 'records', and 'workflows' appear; these are generic/technical with no natural synonyms or file extensions a user would naturally say, placing it just above the no-keywords anchor but well short of good keyword coverage.	2 / 5
Distinctiveness Conflict Risk	The named vendor 'Nets Group' carves a clear, mostly-distinct niche with low conflict risk, though the surrounding generic verbs leave minor overlap risk with adjacent integration skills.	4 / 5
	Total	12 / 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/nets-group/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.