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

typingdna

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/typingdna/SKILL.md

Quality

Content

61%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 actionable and well-structured with concrete Membrane CLI commands and a clear connection-state workflow. Its main weaknesses are some unnecessary background prose, a broken cross-reference, and missing validation for destructive proxy calls.

Suggestions

Remove the opening company-background paragraph and other explanatory padding ('extra layer of security', 'auth plumbing') to improve token efficiency.

Fix the broken 'skip to Step 2' reference by labeling the subsequent sections as numbered steps or rewriting the pointer.

Add a validation/check step before running destructive proxy requests (e.g. 'Confirm method is not DELETE/PUT without verifying the target') so the workflow clears the destructive-operation cap.

De-duplicate 'Searching for actions' and 'Popular actions', which both demonstrate `action list --intent`.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused, but opens with unnecessary company background ('TypingDNA is a behavioral biometrics company... extra layer of security') and some padded prose ('so you can focus on the integration logic rather than auth plumbing'). It is not a 4 because several sentences explain context Claude already knows.	3 / 5
Actionability	Concrete, executable commands are provided throughout (npm install, membrane login, connection ensure, action list/run, request) plus a flags table. It is not a 5 because some placeholders (CONNECTION_ID, /path/to/endpoint) are not tied to a concrete worked example.	4 / 5
Workflow Clarity	The connection setup has good state-based checkpoints and a polling/feedback loop, but the 'skip to Step 2' reference is broken (no Step 2 is labeled) and there is no validation guidance before destructive proxy methods (DELETE/PUT). Per the destructive-operation cap, it cannot exceed 3.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references (no bundle files exist). It is not a 5 because the skill exceeds 50 lines without external file splits and 'Popular actions' partially duplicates 'Searching for actions'.	4 / 5
	Total	14 / 20 Passed

Description

66%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 third-person, has an explicit 'Use when' trigger, and names a distinct niche (TypingDNA), but its actions are generic and it lacks natural synonym keywords. It is solid but could be sharper on concrete capabilities.

Suggestions

Replace generic verbs with concrete TypingDNA operations, e.g. 'Enroll typing patterns, verify users, and manage records'.

Add natural trigger synonyms users would say, such as 'typing patterns', 'biometric authentication', or 'keystroke dynamics'.

Tighten the 'what' clause to list 2-3 specific capabilities instead of 'Manage data, records, and automate workflows'.

Dimension	Reasoning	Score
Specificity	Names the TypingDNA domain and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete (no 'enroll', 'verify', 'extract typing patterns'). It is not a 2 because more than a single minimal action is named, and not a 4 because no specific concrete operations are listed.	3 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with TypingDNA data'). It is not a 5 because the 'what' is vague rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	The keyword 'TypingDNA' is specific and relevant, but the description repeats it without the natural synonyms users would say (typing patterns, biometrics, keystroke dynamics, authentication). It is above a 2 because 'TypingDNA' is a specific rather than generic keyword, but below a 4 because common variations are missing.	3 / 5
Distinctiveness Conflict Risk	'TypingDNA integration' and 'interact with TypingDNA data' form a clear niche brand trigger with minimal overlap risk against other skills. It clearly matches the anchor for a distinct niche with minimal conflict risk.	5 / 5
	Total	15 / 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/typingdna/SKILL.md
Commit: f484c82

Reviewed: 3 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.