Name: intelliprint
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

intelliprint

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

Quality

59%

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/intelliprint/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 content is actionable and reasonably well-structured, giving Claude concrete CLI commands and a clear connection workflow, but it is weakened by padding (a marketing intro and an embedded apology), a mismatch with the description's 'Manage Organizations', and the absence of validation steps around destructive delete/proxy operations.

Suggestions

Remove the product-marketing intro paragraph and the 'Official docs: I am sorry...' line; they add tokens without actionable value.

Add an explicit validation/confirmation step before destructive actions (delete-background, delete-print-job) and before proxy DELETE/PUT requests.

Reconcile the body's Print Job/Background scope with the description's 'Manage Organizations' so the skill is internally consistent.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it opens with a product-marketing paragraph and an embedded AI apology ('Official docs: I am sorry, I cannot provide an API or developer documentation URL...') that are unnecessary padding.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests, plus a popular-actions table, with only minor placeholder gaps (CONNECTION_ID, <actionId>).	4 / 5
Workflow Clarity	The connection flow is sequenced with state-based branching and polling checkpoints, but destructive operations (delete-background, delete-print-job, proxy DELETE) lack any validation/verification feedback loop, capping this at 3.	3 / 5
Progressive Disclosure	Content is organized into clearly headed sections with no nested external references, though it exceeds 50 lines and the actions/flags tables could optionally live in separate reference files.	4 / 5
	Total	14 / 20 Passed

Description

57%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 distinct app name, but its action list is minimal and generic, and 'Manage Organizations' does not reflect the Print Job/Background operations the skill actually provides.

Suggestions

Replace the generic 'Manage Organizations' with concrete capabilities drawn from the body (e.g., 'List and manage Print Jobs, Backgrounds, and files').

Expand the 'when' clause with natural trigger phrases such as 'printing management', 'print jobs', or 'printing costs'.

Add a couple of synonyms or file/domain terms to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Intelliprint integration') but the only named action 'Manage Organizations' is minimal and generic, and notably mismatches the body which actually covers Print Jobs and Backgrounds.	2 / 5
Completeness	It states both what ('Intelliprint integration. Manage Organizations.') and when ('Use when the user wants to interact with Intelliprint data.'), though the 'when' clause is generic and could be more specific.	4 / 5
Trigger Term Quality	'Intelliprint' and 'interact with Intelliprint data' provide the core keyword, but common natural variations or synonyms a user might say are missing.	3 / 5
Distinctiveness Conflict Risk	The explicit app name 'Intelliprint' carves out a clear niche with minimal conflict risk, though the generic 'Manage Organizations' phrase slightly weakens distinctiveness.	4 / 5
	Total	13 / 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/intelliprint/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.