Name: hankoio
Rating: 53.6 (1 reviews)
Author: membranedev

hankoio

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

Quality

60%

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

Quality

Content

63%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 for the Membrane CLI integration with a clear connection-state workflow, but it is padded with domain background Claude already knows and lacks bundle files for progressive disclosure of the action/proxy reference material.

Suggestions

Trim the introductory paragraph explaining what passwordless authentication is and why SaaS businesses want it; Claude already knows this.

Move the proxy request options table and detailed action discovery guidance into a reference file and link to it from SKILL.md to improve progressive disclosure.

Add a validation/verification step (e.g. checking action output or confirming connection state) after running actions that perform destructive or batch changes.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but includes unnecessary explanation of concepts Claude knows (e.g. 'Hanko.io provides passwordless authentication as a service... This is useful for any SaaS business') and redundant restating of the action list command.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands (login, connection ensure, action run, request proxy) with flags documented, though action discovery relies on a generic QUERY placeholder and specific Hanko actions are not enumerated.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced (ensure -> poll for READY -> handle CLIENT_ACTION_REQUIRED -> search actions -> run) with explicit state-transition checkpoints and error handling, though there is no validation step after destructive action runs.	4 / 5
Progressive Disclosure	Content is organized into clear sections but everything is inlined into SKILL.md with no bundle files (references/scripts/assets absent); the action reference and proxy options that could live in separate files are inline, and there is no one-level-deep reference structure.	3 / 5
	Total	14 / 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 correctly identifies the Hanko.io niche and includes an explicit trigger clause, but its capability phrasing is generic and missing Hanko-specific actions (passwordless auth, WebAuthn) that would make it sharper and more distinctive.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with Hanko-specific capabilities such as 'manage WebAuthn credentials, API keys, and user authentication'.

Add natural trigger terms users actually say, e.g. 'Use when the user wants to set up passwordless login, manage WebAuthn registrations, or work with Hanko.io authentication.'

Avoid 'automate workflows' buzzword that does not reflect Hanko's authentication-focused purpose.

Dimension	Reasoning	Score
Specificity	It names the domain (Hanko.io integration) but the actions ('Manage data, records, and automate workflows') are generic and minimal, with no Hanko-specific concrete actions like register WebAuthn credentials or manage API keys.	2 / 5
Completeness	It states both the 'what' (manage data, records, automate workflows) and an explicit 'when' trigger ('Use when the user wants to interact with Hanko.io data'), though the 'what' is generic and the 'when' could be more specific.	4 / 5
Trigger Term Quality	It includes relevant keywords ('Hanko.io data', 'interact with Hanko.io') but lacks natural synonyms a user would say such as 'passwordless', 'WebAuthn', 'authentication', or 'login'.	3 / 5
Distinctiveness Conflict Risk	The Hanko.io naming creates a clear niche with minimal conflict risk against other skills, though the generic 'manage data, records, and automate workflows' phrasing could overlap with other data 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/hankoio/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.