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

neterium

Neterium integration. Manage data, records, and automate workflows. Use when the user wants to interact with Neterium 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/neterium/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 a strong, command-driven getting-started guide with real validation checkpoints in the connection flow, weakened mainly by recurring prose padding and a dangling 'Step 2' reference.

Suggestions

Remove marketing-style padding ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') to tighten token efficiency.

Fix the dangling cross-reference: define/label 'Step 2' or replace 'Skip to Step 2' with a concrete section link so the workflow is unambiguous.

Consider splitting the full connection state machine and the proxy flag table into a referenced reference file to improve progressive disclosure and keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused but includes unnecessary explanatory padding ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection', 'This will burn less tokens'), fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'; not a 4 because the padding recurs across several sections.	3 / 5
Actionability	Provides concrete, copy-pasteable commands (login, connection ensure, action list/run) with a full proxy-flag table and JSON examples, fitting 'mostly executable guidance; concrete code or commands with minor gaps'; not a 5 because of unfilled placeholders (CONNECTION_ID, QUERY) and a few abstract directions.	4 / 5
Workflow Clarity	Sequences install -> authenticate -> connect -> poll-until-ready -> search -> run with explicit state-based validation checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), fitting 'clear sequence with most checkpoints present'; not a 5 because 'Skip to Step 2' is referenced repeatedly but Step 2 is never labeled or defined.	4 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear section headers and no external references; since no bundle files exist and the content is appropriately self-contained, this fits 'good structure; most content is appropriately placed'; not a 5 because there is no explicit overview-to-detail layering and some inline reference-style content (the flag table, full state machine) could be split out.	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 cleanly covers what and when for a distinct named-product niche, but the capability verbs are generic and the trigger guidance lacks concrete variations.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Neterium capabilities (e.g., 'verify identities, screen watchlists, manage profiles and alerts').

Add concrete trigger phrases to the 'Use when...' clause (e.g., 'Use when the user wants to verify a user identity, screen against watchlists, or review Neterium alerts').

Include natural variations/synonyms users might say (e.g., fraud screening, KYC, identity verification) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Neterium) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete capabilities, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; not a 4 because the actions lack specificity.	3 / 5
Completeness	States both what ('Neterium integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Neterium data'), but the 'when' trigger is somewhat generic rather than enumerating concrete trigger phrases, fitting the 'both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Neterium data' provides the product name as a keyword but misses natural variations or synonyms, matching 'Works with PDF files' in having some relevant keywords without common variations.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ('Neterium') creates a clear niche with distinct triggers and minimal conflict risk, matching the 'clear niche with distinct triggers; minimal conflict risk' 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/neterium/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.