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

Blog Docs Log in Get started

privy

Privy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Privy 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/privy/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, packed with executable Membrane CLI commands and a clear connection-state workflow with polling feedback loops. Its main weaknesses are minor verbosity in the intro, loose step numbering, and the absence of verification guidance before destructive proxy or action calls.

Suggestions

Add an explicit verification/confirmation step before destructive operations, e.g. 'Before running a POST/PUT/DELETE action or proxy request, confirm the target with the user and inspect the outputSchema.'

Fix the loose step references: label 'Step 2' (searching/running actions) explicitly or replace 'skip to Step 2' with a concrete section link.

Trim the marketing intro paragraph and 'so you can focus on the integration logic rather than auth plumbing' to tighten token efficiency, and deduplicate 'Searching for actions' with 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with minor padding (the marketing intro paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing'), matching the 'efficient; minor instances of over-explanation that could be trimmed' anchor rather than the fully-lean anchor above.	4 / 5
Actionability	Provides copy-paste-ready executable commands for every stage (install, login, connection ensure, action list/run, request) plus a complete proxy-flag table, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connect workflow is clearly sequenced with state-based branching and a polling feedback loop ('poll again to check if state moved to READY'), but step references are loose ('skip to Step 2' with no labeled Step 2) and there is no explicit verification before potentially destructive proxy/action calls, matching the 'clear sequence with most checkpoints; minor validation gaps' anchor rather than the explicit-validation anchor above.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no nested or buried references (no bundle files exist, and the dynamic action-discovery model needs none), but at ~150 lines with minor redundancy between 'Searching for actions' and 'Popular actions' it matches 'good structure; minor organization gaps' rather than the well-split-with-references anchor.	4 / 5
	Total	17 / 20 Passed

Description

62%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 names the Privy domain and includes an explicit 'Use when' trigger, but its action language is generic and it omits the concrete Privy vocabulary (campaigns, popups, forms, email/SMS) that would sharpen triggers and distinctiveness. It is solid but could be much more specific.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Privy capabilities, e.g. 'Create and manage contacts, forms, popups, campaigns, newsletters, automations, and segments.'

Expand the trigger clause with natural user phrases, e.g. 'Use when the user wants to manage email lists, popups, campaigns, SMS, or automations in Privy.'

Mention the email-marketing/e-commerce context in the description so the skill triggers for marketing-list and conversion-popup requests.

Dimension	Reasoning	Score
Specificity	Names the domain ("Privy integration") and lists several action categories ("Manage data, records, and automate workflows"), but the actions are generic categories rather than concrete operations, fitting the 'names domain and 1-2 actions but not comprehensive' anchor and falling short of the concrete-action anchor above.	3 / 5
Completeness	Answers both 'what' ("Privy integration. Manage data, records, and automate workflows.") and 'when' ("Use when the user wants to interact with Privy data."), but the trigger is generic rather than concrete, matching the 'has both what and when; when could be more specific' anchor rather than the concrete-trigger anchor above.	4 / 5
Trigger Term Quality	Includes the core term "Privy" and generic terms ("data", "records", "workflows") but omits the natural domain vocabulary a user would actually say (email list, popup, campaign, SMS, newsletter), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform "Privy" gives it a clear niche and low conflict risk, but the surrounding action language ("manage data, records, workflows") is generic enough to leave minor overlap risk, matching 'mostly distinct; minor overlap' rather than the fully-distinct anchor.	4 / 5
	Total	14 / 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/privy/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.