Name: humaans
Rating: 59.2 (1 reviews)
Author: membranedev

humaans

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

Quality

69%

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/humaans/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 body is highly actionable with copy-paste commands and a well-organized section structure, but its workflow sequencing has gaps (an undefined "Step 2", no validation after destructive action/proxy calls) and minor conciseness redundancy.

Suggestions

Add explicit verification after running actions and proxy write requests (e.g. re-fetch the record or check the response status) to satisfy the destructive/batch feedback-loop requirement and lift workflow clarity above 3.

Fix the dangling "Step 2" reference by labeling the post-connection stages (e.g. "Step 2: Discover actions", "Step 3: Run or proxy").

De-duplicate the action-list command shared between "Searching for actions" and "Popular actions", and trim marketing phrasing like "This is the fastest way to get a connection."

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with lean prose, but carries minor over-explanation such as "This is the fastest way to get a connection" and a duplicated action-list command across "Searching for actions" and "Popular actions", fitting the anchor for efficient content with trimmable padding.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, interactive and headless login, connection ensure, polling, action list/run with JSON input, proxy with a full flag table), fully executable and matching the anchor for comprehensive concrete coverage.	5 / 5
Workflow Clarity	The connection flow has a real sequence and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but it references a "Step 2" that has no heading and provides no validation after running actions or proxy DELETE/POST requests; because the skill performs potentially destructive HR-data operations without verification, workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	With no bundle files present, the body is organized into clear labeled sections (Overview, Authentication, Connecting, Searching, Running, Proxy, Best practices) keeping content appropriately inline; minor gaps like the broken "Step 2" reference and slight section redundancy keep it just short of a 5.	4 / 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 successfully pairs a what-statement with an explicit "Use when" trigger and leverages the distinct Humaans product name for low conflict risk. Its main weakness is generic action vocabulary and missing HR-specific trigger terms like employee, time off, or onboarding.

Suggestions

Replace generic verbs with concrete HR operations, e.g. "Manage employee records, time off, and onboarding; automate HR workflows."

Add natural trigger terms users would say, such as "Use when the user asks about employees, time off, onboarding, or other Humaans HR data."

Mention file/data types or HRIS context to sharpen distinctiveness against generic data-management skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Humaans domain and 2-3 actions, but the verbs are generic ("manage", "automate") rather than concrete HR operations, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	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 Humaans data"), but the "what" is generic and the trigger could name concrete HR scenarios, so it sits at the anchor where both are present yet the when could be more specific.	4 / 5
Trigger Term Quality	The description relies on the product name "Humaans" plus generic terms ("data", "records", "workflows") and omits the natural HR phrases users would say (employee, time off, onboarding, HRIS), so it has some relevant keywords but misses common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Humaans" gives it a clear niche with minimal conflict risk, but the surrounding "manage data/records/workflows" phrasing is broad enough to invite minor overlap with generic data skills, so it is mostly distinct rather than fully niche-bound.	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/humaans/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.