CtrlK
BlogDocsLog inGet started
Tessl Logo

genderize

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

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/genderize/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is a tight, highly actionable CLI integration guide with concrete commands, a well-handled connection state machine, and clear sectioning. Its main weaknesses are a couple of broken internal step references and an empty placeholder bullet.

DimensionReasoningScore

Conciseness

The body is largely command-focused and lean, with only minor over-explanation such as "so you can focus on the integration logic rather than auth plumbing"; it avoids explaining concepts Claude already knows and respects the token budget.

4 / 5

Actionability

It provides copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) plus a full proxy-flags table, covering the common cases with executable, concrete guidance.

5 / 5

Workflow Clarity

The connect-to-run sequence is clear with an explicit connection-state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/ERROR) and polling feedback, but the dangling "skip to Step 2" reference and a "1b" heading with no "1a" leave minor sequencing gaps.

4 / 5

Progressive Disclosure

With no bundle files present, the content is organized into well-signaled sections in a single appropriately-sized file; minor organization gaps (an empty "- **Name**" bullet, the broken step numbering) keep it just below a clean 5.

4 / 5

Total

17

/

20

Passed

Description

48%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 has an explicit trigger clause and is anchored to a named app, but its capability statement is vague and omits Genderize's core function (gender prediction from names). It reads as generic integration boilerplate rather than a precise skill summary.

Suggestions

State the concrete capability, e.g. "Predict a person's gender from their first name, individually or in batches" instead of "Manage data, records, and automate workflows".

Add natural trigger phrases users would actually say, such as "gender", "name", "predict gender", or "genderize a name".

Tighten the "Use when" clause to reference the real intent, e.g. "Use when the user wants to predict gender from one or more names."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Genderize domain but the actions are generic and abstract; notably it never states Genderize's actual concrete function (predicting gender from a name). It does not rise to anchor 3 because none of the listed actions are concrete.

2 / 5

Completeness

A "Use when the user wants to interact with Genderize data" clause is present, but the "what" is vague (generic data/records/workflows) rather than a clear statement of capability, so it sits below anchor 4 despite the explicit trigger.

3 / 5

Trigger Term Quality

"Genderize" and "interact with Genderize data" give some relevant keywords, but the natural phrases a user would actually say ("gender", "name", "predict gender") are missing, matching the anchor for some relevant keywords without common variations.

3 / 5

Distinctiveness Conflict Risk

The named app "Genderize" and the trigger "interact with Genderize data" carve a mostly distinct niche with minor overlap risk, though the generic "manage data, records, and automate workflows" phrasing could overlap with broad data-management skills.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.