Name: gender-api
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

gender-api

Gender API integration. Manage Persons. Use when the user wants to interact with Gender API data.

Quality

70%

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

Quality

Content

82%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 highly actionable with executable commands and clear connection-state checkpoints, and it is well-structured for a single-file skill, but it has minor conciseness padding and a couple of workflow loose ends (an unlabeled "Step 2" and no explicit validation for batch action results).

Suggestions

Label the post-connection section explicitly as "Step 2" (or renumber the flow) so the "skip to Step 2" reference resolves.

Add a brief validation step after running actions, especially for batch operations like get-gender-batch, e.g. checking the `output` field for errors or partial failures before reporting results.

Tighten the intro paragraph and best-practices bullets by removing background on what Gender API is used for, which Claude can infer or fetch from the linked docs.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with executable commands, a popular-actions table, and flag tables; minor over-explanation appears in the intro paragraph and the best-practices section but could be trimmed, matching the "Efficient; minor instances of over-explanation" anchor.	4 / 5
Actionability	It provides copy-paste-ready `membrane` commands for login, connection ensure, polling, action listing, action running with JSON params, and proxying, plus flag tables covering the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	There is a clear install→login→connect→poll-state→search→run sequence with state-check checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the "skip to Step 2" reference points to an unlabeled step and batch actions lack explicit result-validation feedback, fitting anchor 4.	4 / 5
Progressive Disclosure	No bundle files are provided; the ~140-line single file is organized into clearly headed sections with no nested references, though the popular-actions table and proxy-options table are inlined content that could optionally live in references, landing at anchor 4.	4 / 5
	Total	17 / 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 includes both a what and a when clause and targets a distinct external service, but its capability language ("Manage Persons") is too generic and the trigger phrasing is broad rather than concrete.

Suggestions

Replace "Manage Persons" with concrete actions, e.g. "Predict gender from names, batch-query gender, and determine country of origin."

Sharpen the trigger clause with specific phrases users would say, e.g. "Use when the user wants to predict gender from a name, batch-process names for gender, or find country of origin by name."

Include natural synonyms or file/parameter cues (e.g. "gender prediction", "name-based gender", "batch gender lookup") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Manage Persons" names the domain but uses a generic category verb rather than concrete actions like retrieve, predict, or batch-query, matching the "Names the domain but actions are minimal or generic" anchor.	2 / 5
Completeness	It states a clear "what" ("Gender API integration. Manage Persons.") and an explicit "when" ("Use when the user wants to interact with Gender API data"), but the trigger is generic rather than concrete, so it sits at anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Terms like "Gender API", "Persons", and "interact with Gender API data" are relevant and natural, but the set is thin and missing common synonyms or variations, fitting the "Some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	"Gender API integration" targets a specific external service with a distinct niche and minimal overlap risk, though the generic "Manage Persons" wording keeps it from a perfect 5.	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/gender-api/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.