Name: adobe-pdf-services
Rating: 39.2 (1 reviews)
Author: membranedev

adobe-pdf-services

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

Quality

37%

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/adobe-pdf-services/SKILL.md

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a generic Membrane CLI integration template lightly customized for Adobe PDF Services. It spends tokens on explaining what Adobe PDF Services is and listing operations without providing any concrete, service-specific examples of actual PDF operations. The actionable content is limited to generic Membrane CLI commands that would be identical for any integration.

Suggestions

Remove the introductory paragraph explaining what Adobe PDF Services is and the operations overview tree — Claude already knows this, and the operations can be discovered via `membrane action list`.

Add 1-2 concrete, end-to-end examples of common Adobe PDF Services tasks (e.g., creating a PDF from HTML, running OCR) with actual input/output JSON to make the skill truly actionable.

Trim the CLIENT_ACTION_REQUIRED state documentation and proxy request options table into a separate reference file to improve progressive disclosure and reduce the main file's token footprint.

Add explicit validation/verification steps after running actions (e.g., checking output fields, verifying PDF was created) to improve workflow clarity.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Adobe PDF Services is and its common use cases — information Claude already knows. The overview section is a bullet-point tree of operations that adds little actionable value. There's significant verbosity throughout, including explaining what Membrane does ('handles authentication and credentials refresh automatically') and generic best practices.	1 / 3
Actionability	The skill provides concrete CLI commands for authentication, connection setup, action discovery, and proxy requests, which is good. However, the commands are generic Membrane patterns (not Adobe PDF Services-specific), there are no concrete examples of actual Adobe PDF Services operations (e.g., creating a PDF, running OCR), and no example input/output is shown for any action.	2 / 3
Workflow Clarity	The connection setup workflow has a reasonable sequence with state handling (READY, BUILDING, CLIENT_ACTION_REQUIRED), but there are no explicit validation checkpoints after running actions. The workflow for the overall process (connect → discover → run) is implicit rather than clearly numbered end-to-end, and error recovery for action execution is not addressed.	2 / 3
Progressive Disclosure	The content is structured with headers and sections, but it's essentially a monolithic document with no references to supporting files. The operations overview list and the proxy request options table could be in separate reference files. No bundle files are provided, and the content doesn't leverage progressive disclosure to keep the main file lean.	2 / 3
	Total	7 / 12 Passed

Description

40%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague and generic to effectively guide skill selection. While it names the specific product 'Adobe PDF Services', the described capabilities ('manage data, records, and automate workflows') are boilerplate phrases that could apply to dozens of different integrations. The 'Use when' clause essentially restates the skill name without adding meaningful trigger context.

Suggestions

Replace generic phrases like 'manage data, records, and automate workflows' with specific PDF operations such as 'extract text and tables, merge documents, convert file formats, compress PDFs, add watermarks, or perform OCR'.

Expand the 'Use when' clause with concrete trigger scenarios, e.g., 'Use when the user needs to extract content from PDFs, merge multiple PDFs, convert documents to/from PDF format, or compress PDF files'.

Add natural user terms and file extensions like '.pdf', 'PDF extraction', 'PDF conversion', 'combine PDFs' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete PDF-specific actions. It doesn't mention specific capabilities like extracting text, merging documents, converting formats, or filling forms.	1 / 3
Completeness	It has a 'Use when' clause, but the trigger is extremely vague ('interact with Adobe PDF Services data'). The 'what' portion is also weak — 'manage data, records, and automate workflows' could apply to almost any integration. The 'when' doesn't provide meaningful guidance for skill selection.	2 / 3
Trigger Term Quality	It includes 'Adobe PDF Services' and 'PDF' which are relevant keywords, but misses natural user terms like 'extract text', 'merge PDFs', 'convert PDF', '.pdf files', 'compress', or 'OCR'. The phrase 'manage data, records' is generic and not PDF-specific.	2 / 3
Distinctiveness Conflict Risk	'Adobe PDF Services' is a specific product name which helps with distinctiveness, but the generic actions ('manage data, records, automate workflows') could easily overlap with CRM tools, database skills, or other automation integrations.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: membranedev/application-skills
Path: skills/adobe-pdf-services/SKILL.md
Commit: f484c82

Reviewed: 1 day 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.