Name: humanitix
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

humanitix

Humanitix integration. Manage Events, Users, Organizations. Use when the user wants to interact with Humanitix data.

Quality

64%

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/humanitix/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 CLI guide with concrete commands and validation feedback loops, held back by minor verbosity and inconsistent step numbering.

Suggestions

Remove the filler line "When to use which actions: Use action names and parameters as needed." since it adds no guidance.

Fix step labeling: label the "Connecting to Humanitix" section as Step 1 and the "Searching for actions" section as Step 2 to match the in-text cross-references.

Provide a Humanitix-specific action example with real parameters instead of the generic '{"key": "value"}' placeholder.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands but includes filler ("When to use which actions: Use action names and parameters as needed.") and sections that could be tightened; it does not reach 4 because several unnecessary or vague lines remain.	3 / 5
Actionability	Concrete copy-paste CLI commands (install, login, connection ensure, action list/run, request) cover the common cases; it does not reach 5 because the parameter example ("--input '{\"key\": \"value\"}'") is generic rather than Humanitix-specific.	4 / 5
Workflow Clarity	A clear install→authenticate→connect→search→run sequence exists with state-validation feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED polling); it does not reach 5 because step labeling is inconsistent ("Step 2" is referenced but not labeled, "1b" appears without a "1a").	4 / 5
Progressive Disclosure	No bundle files exist and content is well-organized into clear sections with no nested references; it does not reach 5 because at ~160 lines some inline reference material (detailed clientAction states, the proxy flag table) could be split out.	4 / 5
	Total	15 / 20 Passed

Description

61%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 distinct and answers both what and when, but its capability statement is generic ("Manage") and its trigger terms omit the natural vocabulary (tickets, orders) users would actually say.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "List and retrieve Events, Tickets, Orders, and Tags".

Expand the trigger phrase to include natural user vocabulary: "Use when the user wants to list events, tickets, or orders in Humanitix."

Align the named entities with the skill's actual actions (the body covers Events/Tickets/Orders/Tags, not Users/Organizations).

Dimension	Reasoning	Score
Specificity	The description names the domain ("Events, Users, Organizations") but uses a single generic verb ("Manage") with no concrete actions, matching the anchor where the domain is named but actions are minimal or generic; it does not reach 3 because no specific concrete operations are listed.	2 / 5
Completeness	Both a clear "what" ("Manage Events, Users, Organizations") and an explicit "Use when the user wants to interact with Humanitix data" trigger are present, but the when-clause is somewhat generic; it does not reach 5 because the trigger phrases lack concrete specificity.	4 / 5
Trigger Term Quality	"Humanitix" and "interact with Humanitix data" are relevant trigger terms, but common natural variations a user would say (e.g., tickets, orders) are missing; it does not reach 4 because keyword coverage is partial rather than good.	3 / 5
Distinctiveness Conflict Risk	Leading with the named platform "Humanitix integration" establishes a clear niche with distinct triggers and minimal conflict risk with other skills; it is not below 5 because the platform name alone disambiguates the skill.	5 / 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/humanitix/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.