Name: privyid
Rating: 61.6 (1 reviews)
Author: membranedev

privyid

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

Quality

72%

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

Quality

Content

75%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 a well-structured, actionable CLI integration guide with concrete commands and a clearly sequenced connection workflow including validation feedback loops. The main gaps are minor: a little concept padding, placeholder-heavy examples, and inconsistent step numbering.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with little padding, but contains a few trims like the opening paragraph explaining what PrivyID is and the industries that use it, plus the 'focus on the integration logic rather than auth plumbing' aside.	4 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure/get, action list/run, request) and a flag table, but examples lean on placeholders like CONNECTION_ID and QUERY that keep them just short of fully copy-paste-ready.	4 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checkpoints and a poll/retry feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), though the step numbering is inconsistent ('Step 2', '1b') which introduces a minor navigation gap.	4 / 5
Progressive Disclosure	There are no bundle files, but the single SKILL.md is well-organized into clear sections and keeps bulk API detail behind a discovery command rather than inlining it; minor gaps like the inlined request flag table keep it just below 5.	4 / 5
	Total	16 / 20 Passed

Description

70%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 answers both what and when with a distinctive PrivyID trigger, but its capability list leans on generic abstractions ('manage data', 'automate workflows') rather than concrete, verifiable actions. Tightening the action verbs and adding more concrete triggers would lift it toward the top anchor.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete PrivyID-specific capabilities such as identity verification, KYC/AML checks, document upload, or signer/template management.

Expand the 'when' clause with concrete natural triggers, e.g. 'Use when the user wants to verify identities, run KYC/AML checks, or manage PrivyID users, credentials, and templates.'

Add common synonyms or related phrasings (e.g. 'identity verification', 'KYC', 'e-signature') so the description matches how users actually phrase the request.

Dimension	Reasoning	Score
Specificity	It names the PrivyID domain plus several actions ('Manage data, records, and automate workflows'), but the actions are generic abstractions rather than concrete capabilities, so it sits at the 2-3 boundary and leans toward 3 for naming multiple actions.	3 / 5
Completeness	It states both a clear 'what' ('PrivyID integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with PrivyID data'), but the triggers are not maximally specific or comprehensive, so it falls just below a 5.	4 / 5
Trigger Term Quality	'PrivyID' is a strong distinctive keyword and 'Use when the user wants to interact with PrivyID data' is a natural trigger phrase, giving good coverage though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The 'PrivyID integration' niche and the 'PrivyID' trigger make it mostly distinct with minimal conflict risk, though the generic 'manage data, records, and automate workflows' phrasing leaves minor overlap with broad data skills.	4 / 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/privyid/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.