Name: helpninja
Rating: 52 (1 reviews)
Author: membranedev

helpninja

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

Quality

57%

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

Quality

Content

65%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 action-oriented and mostly concise, with strong executable command examples and a well-sequenced connection workflow. Its main weaknesses are missing verification steps for data-mutating operations and inlined reference material that should be split out, plus minor navigation inconsistencies.

Suggestions

Add a verification step after running actions or proxy requests that mutate data, e.g. re-fetch the record or check the response status before reporting success.

Move the detailed clientAction state machine and the proxy flags table into a separate reference file and link to it from the body to improve progressive disclosure.

Fix navigation inconsistencies by defining 'Step 2' and renumbering the '1b' sub-step (or introducing a '1a') so the workflow reads coherently.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable command examples with little padding, but includes minor trimmable prose such as the HelpNinja overview paragraph ('HelpNinja is a help desk and knowledge base platform...used by small to medium-sized businesses') and explanatory asides about auth, matching the anchor for efficient with minor over-explanation.	4 / 5
Actionability	It provides concrete copy-paste-ready commands throughout (e.g. 'membrane connection ensure "https://helpninja.com/" --json' and the proxy flags table) with clearly signaled placeholders, but examples stay generic (uses '/path/to/endpoint' rather than a real HelpNinja endpoint), fitting the anchor for mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	The connection setup is well sequenced with explicit state checkpoints and a poll-again feedback loop ('After the user completes the action...poll again...to check if the state moved to READY'), but the data-mutating action and proxy flows (which support POST/DELETE) lack any validation or verification step, so per the destructive/batch cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The body has clear section headers and no external bundle files, but inlines reference-dense material (the full clientAction state machine and the proxy flags table) that would benefit from a separate reference, and navigation is slightly broken with an undefined 'Step 2' and a '1b' sub-step with no '1a', fitting the anchor for some structure with inline content that should be separate.	3 / 5
	Total	14 / 20 Passed

Description

50%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 correctly identifies the target app and includes both a 'what' and 'when' clause, but the actions are generic boilerplate rather than HelpNinja-specific and the trigger language lacks natural user phrases and synonyms. It is functional but would benefit from concrete capabilities and richer trigger terms.

Suggestions

Replace generic actions with concrete HelpNinja capabilities, e.g. 'create and update support tickets, manage knowledge base articles, and search customer records'.

Expand the 'Use when...' clause with natural user phrases such as 'support tickets', 'help desk inquiries', 'knowledge base', and 'customer support'.

Add file-type or entity synonyms (e.g. 'tickets', 'KB articles') to improve trigger matching and reduce overlap with other integration skills.

Dimension	Reasoning	Score
Specificity	The description names the HelpNinja domain but its actions ('Manage data, records, and automate workflows') are generic rather than concrete HelpNinja-specific operations like creating tickets or editing knowledge base articles, matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with HelpNinja data') are present, but the 'when' is generic and could be more explicit with concrete triggers, matching the anchor for both present with room for greater specificity; not a 5 because concrete trigger phrases and synonyms are missing.	4 / 5
Trigger Term Quality	The only trigger phrase is 'interact with HelpNinja data', which is generic; it lacks natural user phrases like 'support tickets', 'help desk', or 'knowledge base' and their synonyms, fitting the anchor for one or two generic keywords missing the natural phrases users say.	2 / 5
Distinctiveness Conflict Risk	Tying the description to the named app HelpNinja makes it mostly distinct, though the boilerplate 'manage data, records, and automate workflows' action language overlaps with other data-integration skills, fitting the anchor for mostly distinct with minor overlap risk.	4 / 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/helpninja/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.