Name: subscribe-hr
Rating: 60 (1 reviews)
Author: membranedev

subscribe-hr

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

Quality

70%

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/subscribe-hr/SKILL.md

Quality

Content

78%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 highly actionable with concrete CLI commands and a well-structured connection workflow, but it carries inline reference content that would benefit from external files and omits result-validation guidance for the actions it runs.

Suggestions

Move the long entity list and the proxy-flag reference table into a separate reference file and link to it from the overview to improve progressive disclosure.

Add a validation/inspection step after `membrane action run` and `membrane request` (e.g. check the `output`/status fields and handle errors) to close the workflow-clarity gap for potentially destructive operations.

Trim incidental padding like "so you can focus on the integration logic rather than auth plumbing" to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands and short prose, though a few lines pad concepts Claude already knows ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection").	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection setup, action search/run, and proxying, with parameterized placeholders (CONNECTION_ID, QUERY) clearly indicated.	5 / 5
Workflow Clarity	The connection-readiness flow is well sequenced with explicit state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and polling feedback, but running/proxying actions lacks validation of results beyond "the result is in the output field".	4 / 5
Progressive Disclosure	Content is organized into clear sections, but a large inline entity list and the proxy-flag table are reference material that could live in separate files, and there are no bundle references to offload detail.	3 / 5
	Total	16 / 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 "Use when" trigger with a named-product niche, but its capability list is generic. Tightening the actions to concrete Subscribe-HR operations would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Subscribe-HR operations such as "create employees, submit and approve time-off requests, manage accruals and workflows".

Expand the "Use when" clause to name natural user phrases (e.g. "when the user mentions Subscribe-HR, employee records, time off, or leave requests").

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Subscribe-HR domain and a few action areas, but the actions are generic rather than concrete (no specific operations like "create employee" or "approve leave").	3 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Subscribe-HR data"), though the "what" is generic and the "when" could name concrete scenarios.	4 / 5
Trigger Term Quality	It surfaces the product name "Subscribe-HR" plus generic terms ("data", "records", "workflows") and the natural phrase "interact with Subscribe-HR data", but misses common synonyms and variations a user might say.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the named product "Subscribe-HR" gives it a clear niche with low conflict risk, but the generic action verbs leave minor overlap with other data-management skills.	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/subscribe-hr/SKILL.md
Commit: f484c82

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