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

Blog Docs Log in Get started

printautopilot

PrintAutopilot integration. Manage Organizations. Use when the user wants to interact with PrintAutopilot data.

Quality

68%

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/printautopilot/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 body is a strong, executable CLI integration guide with a well-sequenced connection workflow and concrete commands throughout. Its main weakness is conciseness: a marketing-style intro and a duplicated actions section add tokens that don't earn their place.

Suggestions

Delete the product-marketing intro paragraph ("PrintAutopilot is a SaaS application... marketing agencies...") and the "so you can focus on the integration logic rather than auth plumbing" aside; Claude does not need them.

Merge the near-duplicate "Searching for actions" and "Popular actions" sections into a single discovery section to remove the repeated `action list --intent` examples.

Fix the broken step numbering: define "Step 1"/"Step 2" (or remove the "Step 2" references and the orphaned "1b" heading) so the connection workflow reads as one coherent numbered sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly an efficient CLI reference, but the marketing-style intro ("used by print service providers and marketing agencies to streamline the process..."), the "focus on the integration logic rather than auth plumbing" aside, and the duplicated action-list sections ("Searching for actions" vs "Popular actions") are unnecessary padding that could be trimmed.	3 / 5
Actionability	Every workflow ships copy-paste-ready commands (install, login incl. headless completion, connection ensure/get with --wait, action list/run with --input, and a full proxy flag table) covering the common cases.	5 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with explicit state branches (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but "Step 2" is referenced without being defined and the "1b" heading sits oddly without a matching "1a"/"Step 1".	4 / 5
Progressive Disclosure	No bundle files exist and all content lives inline in a reasonably sectioned ~140-line SKILL.md; structure is good with minor gaps (the near-empty "Popular actions" header and redundancy with "Searching for actions").	4 / 5
	Total	16 / 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 answers both what and when and is anchored to a distinctive product name, but its capability list and trigger phrases are generic rather than comprehensive. Tightening the actions and adding concrete natural-language triggers would lift specificity and trigger-term quality.

Suggestions

Replace the generic "Manage Organizations" / "interact with PrintAutopilot data" with several concrete actions users perform (e.g. create and track print jobs, manage files and orders, query organization data).

Add natural trigger phrasings and synonyms users would actually say, such as "print jobs", "print orders", "print production workflows", or "PrintAutopilot API".

Keep the explicit "Use when..." clause but make the trigger concrete, e.g. "Use when the user wants to create or track print jobs, manage print files, or query PrintAutopilot organizations."

Dimension	Reasoning	Score
Specificity	Names the domain (PrintAutopilot) and one concrete action ("Manage Organizations") but the remaining capability is described abstractly ("interact with PrintAutopilot data"), so coverage is not comprehensive.	3 / 5
Completeness	Both a (weak) "what" ("PrintAutopilot integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with PrintAutopilot data.") are present, though the trigger clause is generic rather than concrete.	4 / 5
Trigger Term Quality	The product name "PrintAutopilot" is a real natural term, but there are no synonyms, common phrasings (e.g. "print jobs", "print orders"), or file extensions, so keyword coverage is thin.	3 / 5
Distinctiveness Conflict Risk	The named product gives a clear niche with a distinct trigger unlikely to fire for unrelated skills; only minor overlap risk exists with other print-oriented skills.	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/printautopilot/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.