Name: pdfmonkey
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

pdfmonkey

PDFMonkey integration. Manage Documents, Audits. Use when the user wants to interact with PDFMonkey data.

Quality

66%

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/pdfmonkey/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 body delivers concrete, executable Membrane CLI guidance with a reasonably clear connection workflow and polling feedback loops, well-organized into sections. It loses points to explanatory padding, a vague Overview, and loose/duplicated step numbering rather than to any structural problem.

Suggestions

Trim explanatory padding (the PDFMonkey intro paragraph, 'auth plumbing' phrasing, and 'burn less tokens' editorializing) and remove the vague Overview line 'Use action names and parameters as needed'.

Tighten the workflow numbering (label 'Step 1a', 'Step 2', etc. consistently) and merge the duplicate action-discovery guidance in 'Popular actions' with 'Searching for actions'.

Add a brief validation checkpoint after running an action (e.g. confirm the `output` field and HTTP status) so the run-and-proxy flows have an explicit verification step.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation such as the PDFMonkey intro paragraph ('a service that allows developers to generate PDFs...'), 'focus on the integration logic rather than auth plumbing', and a thin Overview whose only guidance is 'Use action names and parameters as needed'. Fits 'mostly efficient but includes some unnecessary explanation'; not a 4 because the padded prose and filler overview are noticeable rather than minor.	3 / 5
Actionability	Provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a proxy-flag table. Fits 'mostly executable guidance; concrete code or commands with minor gaps'; not a 5 because placeholders (CONNECTION_ID, <actionId>, QUERY) require substitution and the Overview gives only vague direction.	4 / 5
Workflow Clarity	Sequences install -> login -> connect -> poll for READY -> handle client-action states -> search -> run, with feedback loops ('poll again... to check if the state moved to READY', 'Keep polling until state is no longer BUILDING') and error-state handling. Fits 'clear sequence with most checkpoints present; minor validation gaps'; not a 5 because step numbering is loose ('1b' with no labeled '1a', references to an unlabeled 'Step 2') and the 'Popular actions' section duplicates 'Searching for actions'.	4 / 5
Progressive Disclosure	A single self-contained file with clear section headers and no nested references (only an external docs URL), which is appropriate for a CLI-integration skill with no bundle files. Fits 'good structure; most content is appropriately placed; minor organization gaps'; not a 5 because the Overview is thin and the duplicated action-discovery content is a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

66%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 covers both what and when with a distinct, low-conflict trigger tied to a named service, but its action language is generic ('Manage') and trigger-term coverage lacks common synonyms. Tightening the verbs and adding natural phrases like 'generate PDFs' or 'templates' would raise specificity and trigger quality.

Suggestions

Replace the generic verb 'Manage' with concrete PDFMonkey operations (e.g. 'Generate Documents from templates, list and download Documents, run and inspect Audits').

Expand the 'Use when' clause with natural trigger phrases users would actually say, such as 'generate a PDF', 'PDFMonkey templates', or 'document audits'.

Add file-format or entity synonyms (e.g. 'PDFs', 'templates', 'Document Groups') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (PDFMonkey) and two entities ('Manage Documents, Audits'), but the verb 'Manage' is generic rather than a concrete action, fitting the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. Not a 2 because two named entities exceed the single-generic-action example; not a 4 because no specific operations (e.g. generate, list, download) are listed.	3 / 5
Completeness	Answers both 'what' ('Manage Documents, Audits') and 'when' ('Use when the user wants to interact with PDFMonkey data'). Not a 3 because the 'when' clause is explicit rather than weakly implied; not a 5 because the 'when' offers a single trigger phrase and the 'what' is generic rather than concrete.	4 / 5
Trigger Term Quality	Includes 'PDFMonkey', 'Documents', and 'Audits' as relevant keywords, but misses common user variations such as 'generate PDFs', 'templates', or 'PDF documents'. Fits 'some relevant keywords but missing common variations or synonyms'; not a 4 because the natural phrase coverage is thin rather than just a few terms short.	3 / 5
Distinctiveness Conflict Risk	Names a specific third-party service (PDFMonkey) with a dedicated trigger ('interact with PDFMonkey data'), giving it a clear niche with minimal conflict risk. Fits the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	15 / 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/pdfmonkey/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.