Name: unanet
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

unanet

Unanet integration. Manage data, records, and automate workflows. Use when the user wants to interact with Unanet 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/unanet/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 provides concrete, executable Membrane CLI guidance with a solid connection-polling workflow and good section structure. The main weaknesses are the verbose, duplicate-filled entity list and the absence of any Unanet-specific action examples.

Suggestions

Deduplicate and trim the entity list, or move it to a separate reference file linked from the overview, to recover token budget.

Add at least one Unanet-specific action example (e.g. `membrane action list --intent "list projects"`) and a sample `action run` against a real Unanet record type.

Fix the workflow numbering (label "Step 1"/"Step 2" consistently) so the connection sequence reads as an explicit ordered list.

Dimension	Reasoning	Score
Conciseness	The CLI instructional content is efficient, but roughly 38% of the file is an entity list (~95 lines) containing many duplicate entries (e.g. Project Invoice, Project Forecast, Project Budget appear twice), which is unnecessary padding. It is 3 (mostly efficient with a padded section) rather than 2 because the padding is confined to one section rather than spread throughout.	3 / 5
Actionability	Concrete, copy-paste-ready commands (npm install, membrane login, membrane connection ensure, membrane action list/run, membrane request) plus a flag-options table give executable guidance across common cases. It is 4 rather than 5 because every example is generic Membrane CLI usage with no Unanet-specific action example (e.g. listing projects or fetching a timesheet).	4 / 5
Workflow Clarity	The connection workflow has an explicit feedback loop (poll with --wait, branch on READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR, re-poll after the user acts), which is a real validation checkpoint. It is 4 rather than 5 because numbering is inconsistent (a "1b" subsection with no "1a", and a referenced "Step 2" that is not clearly labeled).	4 / 5
Progressive Disclosure	The body is organized into clear, well-labeled sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no bundle files to reference. It is 4 rather than 5 because the large inline entity list is content that could live in a separate reference file, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

57%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 names the Unanet domain and includes an explicit "Use when" trigger clause, but its capabilities are stated in generic, non-concrete terms. Strengthening the action list with specific Unanet capabilities would raise specificity, trigger coverage, and distinctiveness together.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Unanet capabilities such as "manage projects, timesheets, expense reports, invoices, and vendors".

Add natural trigger synonyms users would say, e.g. "Use when the user wants to query or update Unanet projects, timesheets, expense reports, or invoices".

Tie the trigger more tightly to Unanet-specific nouns (ERP, AEC firms, project financials) to reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	The description names the Unanet domain but its actions ("Manage data, records, and automate workflows") are generic and minimal rather than concrete capabilities. It fits anchor 2 because the domain is named while the actions are abstract categories, and it is not 3 since no concrete actions are enumerated.	2 / 5
Completeness	It supplies both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Unanet data"), so it is not capped at 3. It is 4 rather than 5 because the "what" is generic rather than comprehensive with concrete triggers.	4 / 5
Trigger Term Quality	"Unanet" and "Unanet data" provide a relevant natural keyword, but common variations a user might say (ERP, projects, timesheets, invoices) are absent. It sits at anchor 3 (some relevant keywords, missing variations) rather than 4 (good coverage) because the trigger vocabulary is thin.	3 / 5
Distinctiveness Conflict Risk	Unanet is a specific ERP product giving the skill a clear niche, but the broad "Manage data, records, and automate workflows" phrasing creates minor overlap risk with other data-management skills. It is 4 (mostly distinct, minor overlap) rather than 5 due to that generic action language.	4 / 5
	Total	13 / 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/unanet/SKILL.md
Commit: f484c82

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