Name: pdfless
Rating: 55.2 (1 reviews)
Author: membranedev

pdfless

Pdfless integration. Manage data, records, and automate workflows. Use when the user wants to interact with Pdfless data.

Quality

62%

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/pdfless/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 content is a well-structured, actionable CLI integration guide with executable commands and a sensible workflow including polling feedback. Its main weaknesses are marketing verbosity, a broken step-numbering scheme, and reference-like material kept inline.

Suggestions

Trim marketing filler (the "businesses of all sizes" intro sentence and the "focus on the integration logic rather than auth plumbing" aside) and de-duplicate the pre-built-actions benefit repeated across Best practices.

Fix the workflow numbering: either label a real "Step 2" the "skip to Step 2" reference can point to, or remove the step references and renumber the "1b" block consistently.

Consider moving the proxy flag table and the clientAction field breakdown into a references/ file (e.g. PROXY.md) to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable CLI commands, but it includes marketing padding ("used by businesses of all sizes to streamline document creation workflows", "so you can focus on the integration logic rather than auth plumbing") and repeats the pre-built-actions benefit in the Best practices section, fitting 'mostly efficient but some unnecessary explanation' rather than the lean anchor 4.	3 / 5
Actionability	It provides concrete copy-paste commands (membrane connection ensure, membrane action run ... --json, and a proxy flag table) covering the common cases, with only minor gaps like unfilled placeholders (CONNECTION_ID, actionId), matching 'mostly executable with minor gaps' rather than the fully-specified anchor 5.	4 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear and includes a state machine with a poll/retry feedback loop ("After the user completes the action, poll again..."), but the numbering is broken ("skip to Step 2" references a nonexistent Step 2; "1b" appears out of sequence), which is a minor validation/clarity gap keeping it below 5.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-sectioned with one-level-only structure, but inline reference-like material (the proxy flag table and the clientAction field breakdown) could be split into separate files, matching 'good structure with minor organization gaps' rather than the cleanly-split anchor 5.	4 / 5
	Total	15 / 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 pairs a 'what' and a 'when' trigger in third person, but its capability list is generic and its trigger terms lack natural synonyms. It is distinguishable mainly because it names the Pdfless brand.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete Pdfless actions such as generating documents from templates, filling templates with data, and retrieving generated PDFs.

Broaden the trigger phrase to natural terms users would say, e.g. "Use when the user wants to generate PDF documents, fill document templates, or retrieve Pdfless records."

Dimension	Reasoning	Score
Specificity	It names the domain ("Pdfless integration") but the listed actions — "Manage data, records, and automate workflows" — are generic and minimal rather than concrete PDF/document-specific operations, fitting the 'names domain but actions are generic' anchor rather than the '1-2 concrete actions' anchor above.	2 / 5
Completeness	Both 'what' ("Pdfless integration. Manage data, records, and automate workflows") and 'when' ("Use when the user wants to interact with Pdfless data") are present, but the 'when' could be more explicit/specific with concrete triggers, matching the 'has both but when could be more specific' anchor instead of the fully explicit anchor 5.	4 / 5
Trigger Term Quality	The trigger clause "Use when the user wants to interact with Pdfless data" includes the relevant brand keyword and a natural-ish phrase, but it misses common variations/synonyms (documents, templates, PDFs), so it sits at 'some relevant keywords but missing common variations' rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	Naming a specific brand ("Pdfless") gives it a clear niche with low conflict risk, but the generic action phrasing mirrors sibling Membrane app-integration skills, leaving minor overlap risk rather than the minimal-risk anchor 5.	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/pdfless/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.