Name: printavo
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

printavo

Printavo integration. Manage Organizations, Leads, Projects, Users, Goals, Filters. Use when the user wants to interact with Printavo data.

Quality

66%

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

Quality

Content

67%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 an actionable, well-structured integration guide with executable commands and a clear connection-state workflow including a polling feedback loop. Its main weaknesses are some padded introductory prose and slightly awkward step numbering.

Suggestions

Trim the opening background paragraph ('Printavo is shop management software... streamline their operations') to one line; Claude does not need the market context to use the CLI.

Fix the step numbering: replace the '1b' subsection with a proper 'Step 2' and ensure every 'Step N' reference points to a labeled heading.

Add one complete worked example (e.g. a real 'action list --intent' followed by an 'action run' with sample input and the 'output' field interpreted) to lift actionability to fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Mostly concrete commands, but the opening paragraph explaining what Printavo is and who uses it, plus marketing phrasing like 'burn less tokens' and 'streamline their operations', adds unnecessary padding that could be trimmed.	3 / 5
Actionability	Provides copy-paste ready bash commands for install, auth, connection, action search/run, and proxying with a full flag table, but lacks a complete end-to-end worked example with sample input and interpreted output.	4 / 5
Workflow Clarity	The connect-to-ready flow is clearly sequenced with state-based branching and a real polling feedback loop ('poll again... to check if the state moved to READY'), but step numbering is awkward ('1b', an undefined 'Step 2' reference), leaving minor gaps.	4 / 5
Progressive Disclosure	Single-file skill with no bundle files, organized into clear headed sections (auth, connecting, searching, running, proxy, best practices); content is appropriately placed with only minor organization gaps like the bare '1b' subsection.	4 / 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 establishes a clear, distinct niche via the Printavo brand and includes an explicit 'Use when' trigger, but it leans on one generic verb and lists entities that don't match the product's natural user vocabulary. It is solid but could be sharper on action specificity and trigger terms.

Suggestions

Replace the single generic verb 'Manage' with distinct concrete actions (e.g., 'create and track orders, send quotes, generate invoices, manage customers').

Align the listed entities with what users actually say about Printavo (orders, quotes, invoices, customers, tasks) rather than generic CRM nouns.

Tighten the 'Use when' clause with concrete trigger phrases, e.g. 'Use when the user wants to create orders, send quotes, or manage customers in Printavo.'

Dimension	Reasoning	Score
Specificity	Names the Printavo domain and lists six managed entities ('Organizations, Leads, Projects, Users, Goals, Filters'), but relies on a single generic verb 'Manage' rather than enumerating distinct concrete actions, so it does not reach the 'several specific actions' anchor.	3 / 5
Completeness	It answers both 'what' ('Manage Organizations, Leads, Projects, Users, Goals, Filters') and 'when' ('Use when the user wants to interact with Printavo data'), but the trigger clause is generic rather than naming concrete trigger phrases, matching the 'when could be more specific' anchor.	4 / 5
Trigger Term Quality	The brand keyword 'Printavo' and several entity nouns are present, but the listed entities (Organizations, Leads, Goals, Filters) omit the natural terms users would say for this product (orders, quotes, invoices, customers), leaving common variations missing.	3 / 5
Distinctiveness Conflict Risk	Naming a specific third-party product ('Printavo integration') gives it a clear niche with distinct triggers and minimal conflict risk with other skills.	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/printavo/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.