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

humanity

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

Quality

68%

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

Quality

Content

86%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 with executable commands and a clear connection-polling workflow. Minor gaps are an undefined 'Step 2' reference and some light padding in the intro.

Suggestions

Define or remove the dangling 'Step 2' reference so the connection workflow is fully self-contained.

Add a brief validation step after running actions (e.g. check the output/error field before proceeding) for batch or mutating operations.

Trim the opening overview paragraph and the auth-plumbing aside to reduce tokens without losing clarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with direct commands and brief explanations; minor padding like the opening paragraph on what Humanity is and the 'so you can focus on integration logic' aside could be trimmed.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (login, connection ensure, action run with --input JSON, proxy flags table) covering the common cases.	5 / 5
Workflow Clarity	Clear connection sequence with explicit polling states and error-recovery guidance, but the referenced 'Step 2' is never defined and result validation before acting on output is missing.	4 / 5
Progressive Disclosure	Well-organized into logical sections with no nested references and no need for external bundle files; content is appropriately scoped and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

51%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 answers both what and when, but relies on generic action verbs and a proper-noun trigger rather than the natural keywords users would actually say. It is functional but indistinct from other data-integration skills.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with Humanity-specific actions such as scheduling shifts, tracking time and attendance, and managing leave.

Add natural trigger phrases users would say, e.g. 'Use when the user wants to schedule employees, track time and attendance, or manage leave in Humanity.'

Tighten the 'when' clause with concrete triggers like 'Humanity', 'shift scheduling', 'time clock', or 'payroll' to reduce overlap with other integration skills.

Dimension	Reasoning	Score
Specificity	Names the Humanity domain plus a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than Humanity-specific (no scheduling, shifts, time clock, or leave).	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Humanity data') are present, though the trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	Only the proper noun 'Humanity' and the generic phrase 'interact with Humanity data' appear; the natural terms users would say (schedule, shifts, time clock, payroll, leave) are missing.	2 / 5
Distinctiveness Conflict Risk	The named Humanity app gives a niche, but the generic surrounding language ('manage data, records, automate workflows') overlaps with many integration skills.	3 / 5
	Total	12 / 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/humanity/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.