Name: nexhealth
Rating: 62.4 (1 reviews)
Author: membranedev

nexhealth

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

Quality

74%

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/nexhealth/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 CLI commands and a strong connection-state feedback loop, but is held back by padded marketing prose and slightly loose workflow numbering plus missing validation guidance for destructive proxy calls.

Suggestions

Trim padded prose: remove the marketing intro ('streamline their operations and improve patient engagement') and 'so you can focus on the integration logic rather than auth plumbing', keeping only the operational facts.

Fix workflow numbering: label 'Step 1', 'Step 2' explicitly so the 'skip to Step 2' reference resolves, and add a validation note before destructive proxy calls (PUT/PATCH/DELETE) such as verifying the target id before running.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but includes padded prose such as the marketing-style NexHealth intro ('streamline their operations and improve patient engagement') and 'so you can focus on the integration logic rather than auth plumbing', which could be tightened.	3 / 5
Actionability	Commands are copy-paste ready and cover the common cases — install, login (incl. headless), connection ensure/wait, action list/run, and proxy requests with a concrete flags table — fully executable guidance.	5 / 5
Workflow Clarity	There is a clear install → auth → connect → search → run/proxy sequence with strong validation via the connection state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED polling feedback loop), but step numbering is loose ('skip to Step 2' with no labeled Step 2) and destructive proxy methods (PUT/PATCH/DELETE) lack validation guidance.	4 / 5
Progressive Disclosure	The single-file skill is self-contained with no bundle references and well-organized section headers, giving good structure; minor gaps (loose step numbering, a longish inline state-machine explanation) keep it just below the well-signaled-reference anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

73%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 is well-structured with an explicit 'Use when...' trigger and a clearly named, distinctive platform, but its capability list ('manage data, records, automate workflows') is generic rather than concrete NexHealth operations.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete NexHealth actions such as 'schedule appointments, sync patient records, send reminders, and query providers'.

Add natural trigger synonyms a user might say, e.g. 'Use when the user wants to interact with NexHealth data, schedule or manage patient appointments, or query NexHealth records.'

Dimension	Reasoning	Score
Specificity	Names the domain (NexHealth) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are fairly generic rather than concrete NexHealth-specific operations, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with NexHealth data'), but the 'what' actions are slightly generic, keeping it just below the fully-concrete anchor 5.	4 / 5
Trigger Term Quality	The natural keyword 'NexHealth' / 'interact with NexHealth data' is the term a user would actually say, giving good coverage for a named platform; only minor synonym variations are missing, fitting just above the midpoint anchor.	4 / 5
Distinctiveness Conflict Risk	NexHealth is a specific named platform with a distinct trigger, so it occupies a clear niche with minimal risk of conflicting with other skills.	5 / 5
	Total	16 / 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/nexhealth/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.