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

greythr

GreytHR integration. Manage data, records, and automate workflows. Use when the user wants to interact with GreytHR 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/greythr/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 content is a well-structured, actionable guide to driving GreytHR through the Membrane CLI, with concrete commands and a connection-readiness feedback loop. Its main weaknesses are a padded product-intro paragraph, some unresolved placeholders, and minor structural redundancy.

Suggestions

Trim the opening paragraph that explains what GreytHR is; assume that knowledge or compress it to one line linking to the official docs.

Resolve or clearly annotate the CONNECTION_ID placeholder and reconcile the "Step 2" references with explicit numbered step labels so the workflow sequence is unambiguous.

Merge the redundant "Searching for actions" and "Popular actions" sections to remove the duplicated action-list command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands, but the opening paragraph explaining what GreytHR is ("cloud-based HR and payroll software designed for small and medium-sized businesses...") and the vague line "Use action names and parameters as needed." add unnecessary padding that could be tightened.	3 / 5
Actionability	It provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) with flags explained, fitting mostly-executable guidance with only minor gaps such as unresolved CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-for-ready → search → run sequence is clear, with explicit state-based checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a polling feedback loop, though the "skip to Step 2" references are weakened by inconsistent step labeling.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections with headers, and there are no external bundle files to mismanage; minor redundancy between "Searching for actions" and "Popular actions" keeps it just below a perfect score.	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 is third-person, names a clear niche, and includes an explicit "Use when" trigger, so it answers both what and when. It is held back by generic action verbs and limited trigger-term coverage rather than concrete HR-specific capabilities.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete GreytHR capabilities such as employee records, leave, attendance, payslips, and Form 16.

Expand the trigger clause to mention common user phrasings and synonyms, e.g. "Use when the user wants to query or update GreytHR employee, payroll, attendance, or leave data."

Dimension	Reasoning	Score
Specificity	The description names the domain ("GreytHR integration") and a couple of actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete HR-specific capabilities, matching the anchor for domain + 1-2 actions that are not comprehensive.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with GreytHR data"), though the "when" clause is explicit but somewhat generic, matching the anchor for both present with the "when" able to be more specific.	4 / 5
Trigger Term Quality	It surfaces the natural term "GreytHR" and the phrase "interact with GreytHR data", but offers few synonyms or common variations a user might say, fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"GreytHR integration" is a clear, narrow niche with a distinct trigger unlikely to collide with other skills, though the generic "data, records, workflows" phrasing leaves minor overlap risk with other integration 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/greythr/SKILL.md
Commit: f484c82

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