Name: pdfco
Rating: 51.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

pdfco

PDF.co integration. Manage Jobs, Templates. Use when the user wants to interact with PDF.co data.

Quality

56%

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

Quality

Content

50%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 CLI commands covering the common workflow, but it is weighed down by a large redundant inlined action list and has workflow gaps: an undefined "Step 2" and no validation checkpoints for executing actions or proxy requests. Progressive disclosure suffers from the inlined bulk and absence of reference files.

Suggestions

Remove or move the ~110-item action list into a separate reference file (e.g., ACTIONS.md), relying on `membrane action list` for discovery as the skill already advises.

Define the dangling "Step 2" reference (or renumber) so the connection-to-execution sequence is unbroken.

Add a validation/error-recovery checkpoint after `membrane action run` and `membrane request` (e.g., inspect the `output`/error field and retry on failure) given these can be destructive or batch operations.

Dimension	Reasoning	Score
Conciseness	A ~110-item enumerated action list (lines 23-134) is inlined as a data dump even though the skill itself recommends discovering actions via `membrane action list`, making it a noticeably padded section rather than mere minor over-explanation.	2 / 5
Actionability	Provides concrete, copy-pasteable commands for the full workflow (install, login, connection ensure, action list/run, request proxy) with a flags table, but commands rely on placeholders and lack a single filled end-to-end worked example, so it is not fully a 5.	4 / 5
Workflow Clarity	The connection flow is sequenced with a state-feedback loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR plus polling), but "Step 2" is referenced and never defined, and action execution / proxy requests (potentially destructive) have no validation or error-recovery checkpoints.	3 / 5
Progressive Disclosure	Section structure is reasonable (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices) but the large inlined action list is content that belongs in a separate reference file or should be removed, and no bundle/reference files exist, matching the 'inlined content that should be separate' anchor.	3 / 5
	Total	12 / 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 answers both what and when with an explicit trigger, but its capabilities are stated generically ("Manage Jobs, Templates") and natural trigger coverage is limited to the brand name. It is clearly distinct yet lacks the concrete action breadth and synonym coverage of top-tier examples.

Suggestions

Replace the generic verb "Manage" with concrete PDF.co operations (e.g., "Convert, merge, split, and extract data from PDFs") to lift specificity.

Expand the trigger clause with natural phrases and file types users actually say (e.g., "Use when the user mentions PDF.co, PDF conversion, merging, or form filling").

Add a synonym or two (e.g., "PDFs", "document conversion") so the skill surfaces for varied phrasings.

Dimension	Reasoning	Score
Specificity	Names the domain and two entity-level actions ("Manage Jobs, Templates") but the verb "Manage" is generic and no concrete document operations are listed, so it sits between the 1-2-action anchor and the several-specific-actions anchor.	3 / 5
Completeness	Explicitly answers both what ("PDF.co integration. Manage Jobs, Templates.") and when ("Use when the user wants to interact with PDF.co data."), though the 'what' is thin and the 'when' offers a single trigger rather than concrete phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Includes the brand keyword "PDF.co" plus entity terms ("Jobs", "Templates", "interact with PDF.co data"), but lacks common natural variations or synonyms users might say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tied to the specific named platform "PDF.co", giving a clear niche with minor overlap risk against generic PDF skills; the single trigger phrase keeps it below the minimal-conflict 5 anchor.	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/pdfco/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.