Name: pymetrics
Rating: 59.2 (1 reviews)
Author: membranedev

pymetrics

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

Quality

69%

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

Quality

Content

72%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.

A well-structured, highly actionable CLI integration guide with copy-paste commands throughout. Its main gap is missing validation/verification steps around batch and destructive operations (action run, proxy requests), which caps workflow clarity.

Suggestions

Add explicit validation before destructive/batch operations, e.g. verify a connection is READY and confirm an action's inputSchema before running 'membrane action run'.

Include a verify-after-run step showing how to check the 'output' field or re-query to confirm batch operations succeeded.

Trim the opening 'Pymetrics is a talent assessment platform...' paragraph and 'Agent Types' aside, which describe context Claude can infer from the integration.

Dimension	Reasoning	Score
Conciseness	Largely lean command-driven reference with executable CLI snippets and a tight best-practices list; the opening 'what is Pymetrics' paragraph and 'Agent Types' aside add minor padding that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready membrane commands with flags for every key operation (login, connection ensure, polling, action list/run, proxy requests), plus concrete input/output examples.	5 / 5
Workflow Clarity	The connection flow is sequenced with state-based polling and CLIENT_ACTION_REQUIRED branches, but batch/destructive operations (action run, proxy mutations) lack explicit validation or verification checkpoints before proceeding.	3 / 5
Progressive Disclosure	Reasonably sectioned single-file overview with no external references, but the 'Pymetrics Overview' hierarchy and inline flag table could be more clearly signaled; no bundle files exist to push detail into.	3 / 5
	Total	15 / 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 names a specific platform and provides both a 'what' and an explicit 'Use when' trigger, which is above the no-trigger cap. The main weakness is generic action verbs ('Manage data, records, and automate workflows') that lack concrete Pymetrics-specific operations.

Suggestions

Replace generic verbs with concrete Pymetrics actions, e.g. 'Pull candidate game results, manage job assessments, and automate candidate-to-job matching workflows'.

Add natural trigger synonyms a user might say, e.g. 'Use when the user mentions Pymetrics, candidate assessments, or neuroscience games'.

Mention specific record types (Candidate, Game, Job, Account) referenced in the body to sharpen the 'what'.

Dimension	Reasoning	Score
Specificity	Names the domain (Pymetrics integration) and a few concrete actions ('Manage data, records, and automate workflows'), but the actions are generic verbs with no specifics about what Pymetrics operations are supported.	3 / 5
Completeness	Has a clear 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Pymetrics data'), though the 'when' is fairly generic.	4 / 5
Trigger Term Quality	Includes the natural trigger 'interact with Pymetrics data', but lacks synonyms or common variations a user might actually say; coverage is narrow.	3 / 5
Distinctiveness Conflict Risk	Pymetrics is a specific named platform with a distinct trigger, so it is clearly distinguishable from other skills 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/pymetrics/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.