Name: alexishr
Rating: 56.8 (1 reviews)
Author: membranedev

alexishr

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

Quality

65%

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/alexishr/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 well-structured, actionable guide to driving AlexisHR through the Membrane CLI, with a notably strong connection-state workflow including feedback loops. Its main weaknesses are a padded marketing intro and the absence of any external reference files for the longer detailed sections.

Suggestions

Cut the marketing-style intro paragraph and the 'Use action names and parameters as needed.' filler; keep only what Claude cannot infer about the AlexisHR product.

Add a brief verification step after `membrane action run` for mutating/destructive actions (e.g. re-query to confirm the change) to strengthen the workflow's feedback loop.

Move the detailed clientAction state machine and proxy flag table into a references/ file and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The bulk is lean command examples, but the marketing-style intro ('AlexisHR is a human resources management system designed to streamline HR processes...') and filler like 'Use action names and parameters as needed.' are unnecessary explanation that could be trimmed, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands (install, login, connection ensure, action run, proxy with a full flags table) with only minor gaps such as placeholders (CONNECTION_ID, <actionId>) and the inconsistent `membrane` vs `npx @membranehq/cli` invocation, fitting anchor 4 rather than fully-executable anchor 5.	4 / 5
Workflow Clarity	The connection-readiness flow has explicit validation checkpoints and feedback loops (poll --wait, then branch on READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR and re-poll), giving a clear sequence; minor gaps are the undefined 'Step 2' reference and the lack of post-run verification for potentially destructive actions, keeping it at 4.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) at a single level with no nested references, but no bundle files exist and some detailed inline content (the full clientAction state machine, the proxy flag table) could be externalized, so it sits at 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

62%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 pairs a 'what' with an explicit 'Use when' trigger and anchors the skill to a distinct named product. Its weakness is generic action verbs and missing concrete HR trigger terms (employee, time off) that users would naturally say.

Suggestions

Replace generic verbs with concrete HR actions, e.g. 'manage employee records, track time off, and view time-off policies'.

Expand the 'Use when' clause with natural trigger phrases users say: 'Use when the user mentions AlexisHR, employee data, time off, or HR records'.

Add the file/extension or entity synonyms (employee, time off, work week) to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('AlexisHR integration') and lists actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete HR-specific operations like 'track time off' or 'update employee records', so it sits at the anchor-3 level rather than the more specific anchor 4.	3 / 5
Completeness	It has a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with AlexisHR data'), but the trigger phrases are not as concrete or varied as the anchor-5 example, placing it at 4 rather than 5.	4 / 5
Trigger Term Quality	The main natural trigger is the product name 'AlexisHR' plus 'interact with AlexisHR data', but it omits common variations a user would actually say ('employee', 'time off', 'HR', 'time-off policy'), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product 'AlexisHR' gives it a clear niche with low conflict risk, though the surrounding action language ('manage data, records, workflows') is generic enough to keep it just below the maximally-distinct anchor 5.	4 / 5
	Total	14 / 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/alexishr/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.