Name: athenahealth
Rating: 60.8 (1 reviews)
Author: membranedev

athenahealth

Athenahealth integration. Manage Patients, Appointments, Providers, Practices, Departments, Claims. Use when the user wants to interact with Athenahealth data.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/athenahealth/SKILL.md

Quality

Content

63%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.

A well-structured, command-driven integration guide with strong actionability and a clear connection-state workflow. It is held back by an explanatory intro paragraph and inline reference tables that would benefit from being split into separate files.

Suggestions

Trim the opening Athenahealth overview paragraph and the "auth plumbing" commentary to assume Claude's competence and reduce tokens.

Move the Popular actions table and proxy flag reference into a dedicated references file (e.g. ACTIONS.md) and link to it from SKILL.md to improve progressive disclosure.

Fill in the blank Description column in the Popular actions table so each action is self-explanatory without a separate lookup.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what Athenahealth is and phrases like "so you can focus on the integration logic rather than auth plumbing" are noticeable padding, though the bulk is reasonably tight CLI documentation.	3 / 5
Actionability	Concrete, executable commands (npm install, membrane login, connection ensure, action list/run, request) with documented flags are mostly copy-paste ready, though the Popular actions table leaves descriptions blank.	4 / 5
Workflow Clarity	The connection setup is a clear state-machine sequence (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with polling and a feedback loop (poll again after user action), with only minor step-labeling inconsistency ("Step 2" referenced without a labeled Step 1).	4 / 5
Progressive Disclosure	Sections are clearly headed, but ~150 lines of inline reference material (the Popular actions table, proxy flag table) that could live in separate reference files are kept in SKILL.md, and no bundle files exist to offload detail.	3 / 5
	Total	14 / 20 Passed

Description

78%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.

A concise, third-person description that names the platform and its core entities and provides an explicit use-when clause. It is distinct and free of fluff, with only minor gaps in action verb variety and trigger synonym coverage.

Dimension	Reasoning	Score
Specificity	"Manage Patients, Appointments, Providers, Practices, Departments, Claims" lists several specific entities, but the single generic verb "Manage" applied across all of them leaves minor gaps versus multiple distinct concrete actions.	4 / 5
Completeness	It explicitly states both what ("Manage Patients, Appointments...") and when ("Use when the user wants to interact with Athenahealth data"), but the when-clause is somewhat generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	"Athenahealth", "Patients, Appointments, Providers, Practices, Departments, Claims", and "interact with Athenahealth data" give good keyword coverage, though common synonyms like EHR or medical/health records are missing.	4 / 5
Distinctiveness Conflict Risk	"Athenahealth integration" targeting a named healthcare platform with domain-specific entities is a clear niche with distinct triggers and minimal conflict risk.	5 / 5
	Total	17 / 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/athenahealth/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.