Name: printnode
Rating: 63.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

printnode

PrintNode integration. Manage Printers, PrintJobs, Accounts. Use when the user wants to interact with PrintNode data.

Quality

75%

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

Quality

Content

71%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 highly actionable with concrete, executable CLI commands and a well-checkpointed connection workflow, though it leans slightly verbose in its prose and keeps all detail inline without progressive disclosure to supporting files.

Suggestions

Trim the introductory prose about what PrintNode is and the "Think of it as a universal print driver" analogy to respect the token budget.

Move the proxy flag reference table and the action-discovery details into a separate reference file, linking to it from a concise overview.

Fix the inconsistent step numbering (e.g., add a labeled Step 1a and Step 2) so the connection workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the intro ("PrintNode is a service that allows users to print... Think of it as a universal print driver") and some prose explain concepts that pad the token budget. It is not a 4 because several sentences could be trimmed without losing clarity, and not a 2 because the bulk is actionable command examples.	3 / 5
Actionability	The content provides copy-paste ready commands (membrane login, connection ensure, action run, request) with a flag table and JSON parameter examples covering common cases. It is not a 4 because the examples are fully executable and specific rather than having minor gaps.	5 / 5
Workflow Clarity	The connection flow is sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop after user action. It is not a 5 because step numbering is inconsistent ("Step 2" referenced, "1b" without 1a) and not a 3 because validation checkpoints are explicitly present.	4 / 5
Progressive Disclosure	The skill is a single file with no bundle references and decent section headers, but detailed material (the proxy flag table, popular/actions guidance) that could live in separate files is inlined. It is not a 4 because there are no signaled one-level-deep references, and not a 2 because sections are reasonably organized rather than a monolithic wall.	3 / 5
	Total	15 / 20 Passed

Description

78%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 is concise, third-person, and answers both what and when with an explicit trigger clause. It is distinct and low-conflict, though the action verb and trigger phrasing could be more concrete.

Dimension	Reasoning	Score
Specificity	"Manage Printers, PrintJobs, Accounts" lists several concrete domain objects with an explicit action, though "Manage" is somewhat generic and coverage of specific sub-actions is limited. It is not a 3 because it names multiple specific objects, and not a 5 because the action verb lacks concrete, varied operations.	4 / 5
Completeness	It states both what ("Manage Printers, PrintJobs, Accounts") and when ("Use when the user wants to interact with PrintNode data"), with the trigger explicit but somewhat generic. It is not a 3 because an explicit "Use when" clause is present, and not a 5 because the trigger phrase is broad rather than concrete.	4 / 5
Trigger Term Quality	"Printers, PrintJobs, Accounts" and "interact with PrintNode data" include natural terms a user would say, with good coverage but missing common synonyms or file/extension-style variants. It is not a 3 because the keywords are relevant and user-facing, and not a 5 because synonyms and broader phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	"PrintNode integration" carves a clear niche with PrintNode-specific triggers and minimal overlap risk with other skills. It is not a 4 because the triggers are unambiguously tied to a distinct named service.	5 / 5
	Total	17 / 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/printnode/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.