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

Blog Docs Log in Get started

privyr

Privyr integration. Manage Recordses. Use when the user wants to interact with Privyr 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/privyr/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 delivers strong, copy-paste-ready CLI guidance with good state-handling feedback loops for connections. It is held back by marketing padding, a broken step-numbering scheme, a misnamed 'Popular actions' section, and the absence of validation steps for destructive CRUD actions.

Suggestions

Remove marketing padding (e.g. 'so you can focus on the integration logic rather than auth plumbing', 'burn less tokens') to tighten token efficiency.

Fix the step numbering (label '1a' or remove '1b', and define the referenced 'Step 2') so the connection workflow is unambiguous.

Add a verification step after running destructive actions (create/update/delete), e.g. re-query the Record or check the command's exit/output for success.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands, but includes marketing padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens and make communication more secure' that could be trimmed, fitting the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	Concrete, runnable commands are given for install, login, connection, action discovery, action runs, and proxying, with a flags table; minor gaps remain (the 'Popular actions' section only repeats the discovery command instead of listing actions, and examples use placeholders like 'QUERY').	4 / 5
Workflow Clarity	The connect-and-poll flow has explicit state checks and a re-poll feedback loop, but step numbering is broken ('1b' with no '1a', references to an undefined 'Step 2'), and destructive CRUD actions lack any result validation — the destructive-operation-without-validation cap holds this at 3.	3 / 5
Progressive Disclosure	The content is organized into clear, navigable sections in a single file with no external references needed (no bundle files exist), but the over-50-line simple-skill exception does not apply and minor structural issues (broken step numbering, misnamed 'Popular actions' section) keep it just below the top anchor.	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 explicitly covers both what the skill does and when to use it, anchored on a distinctive brand name that limits conflict risk. Its main weakness is generic, thin capability language ('Manage Recordses', with a malformed plural) and limited trigger-term variation.

Suggestions

Replace 'Manage Recordses' with concrete actions, e.g. 'Create, read, update, delete, and list Records'.

Broaden the trigger clause with synonyms a user might say, e.g. 'Use when the user wants to query, edit, or sync Privyr Records or Privyr data'.

Fix the malformed plural 'Recordses' to 'Records'.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage Recordses' names the Privyr domain and a core data object (Records) with one generic verb, but offers no concrete CRUD-style actions, so it sits at the 'domain + 1-2 actions, not comprehensive' anchor rather than the multi-action anchor above.	3 / 5
Completeness	Both 'what' ('Privyr integration. Manage Recordses.') and 'when' ('Use when the user wants to interact with Privyr data') are present and explicit, but the 'what' is generic and the odd plural 'Recordses' keeps it short of the fully concrete anchor 5.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Privyr data' surfaces the natural brand keyword 'Privyr' that users would say, but provides no synonyms or variations, matching the 'some relevant keywords, missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Privyr integration' names a unique brand with a clear niche and a brand-specific trigger, making conflict with other skills minimal — matching the 'clear niche with distinct triggers' anchor.	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/privyr/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.