Name: staffology
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

staffology

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

Quality

66%

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

Quality

Content

76%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 concrete, copy-paste Membrane CLI commands and a clear connection-state flow, but it lacks validation/verification checkpoints for destructive operations and has a broken 'Step 2' reference in its workflow.

Suggestions

Add verification steps around action execution and proxy requests—e.g. confirm a pay run's status before/after running, or dry-run/inspect results before mutating calls.

Fix the step numbering: the body references 'Step 2' but never labels Step 1 or Step 2; either introduce explicit numbered steps or remove the dangling reference.

Trim the opening marketing sentence about UK accountants to keep the overview focused on what the skill does.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, built around executable commands, though the opening marketing sentence ('Accountants and businesses of all sizes in the UK use it to streamline their payroll and HR administration.') and the 'auth plumbing' aside are minor padding.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case—install, login, connection ensure, polling, action list/run, and proxy requests—with a concrete flags table and JSON-output guidance.	5 / 5
Workflow Clarity	A rough install→login→connect→search→run sequence exists with a connection-state polling checkpoint, but the 'Step 2' reference is unlabeled/broken and running payroll actions or mutating proxy requests (POST/PUT/DELETE) lacks validation/verification steps, capping destructive/batch workflow clarity at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references and no bundle files needed, though everything is inlined in one ~146-line file where some reference material (e.g. the proxy flags table) could live separately.	4 / 5
	Total	16 / 20 Passed

Description

57%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 clearly identifies the Staffology niche and includes a usable 'Use when' trigger, but its action verbs are generic and it omits the domain-specific terms (payroll, HR, HMRC) that would make triggers more natural and specific.

Suggestions

Replace generic verbs with concrete Staffology capabilities, e.g. 'Run payroll, manage employee records, and submit HMRC reporting'.

Add domain trigger terms users actually say, such as 'payroll', 'payslips', 'HMRC', or 'pay runs', to the 'Use when' clause.

Tighten the 'when' clause to specific scenarios, e.g. 'Use when the user wants to run UK payroll, manage employees, or handle HMRC reporting in Staffology'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Staffology) but its actions ('Manage data, records, and automate workflows') are generic and minimal rather than concrete operations like 'run payroll' or 'submit HMRC reports'.	2 / 5
Completeness	It answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Staffology data'), though the 'when' clause is somewhat generic and could name the concrete payroll/HR scenarios.	4 / 5
Trigger Term Quality	'Staffology' is a strong natural trigger keyword, but the surrounding terms ('data', 'records', 'workflows') are generic and miss common synonyms a user might say like 'payroll', 'HMRC', or 'payslips'.	3 / 5
Distinctiveness Conflict Risk	The named product 'Staffology' gives it a clear niche and distinct trigger, with only minor overlap risk from the generic 'data/records/workflows' phrasing against other HR/payroll skills.	4 / 5
	Total	13 / 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/staffology/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.