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.
61
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/adobe-pdf-services/SKILL.mdQuality
Discovery
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 relies heavily on the 'Adobe PDF Services' brand name for identification but fails to describe any concrete capabilities. The language is generic and circular—'manage data' and 'interact with data' tell Claude almost nothing about when to select this skill. It needs specific PDF operations and natural trigger terms to be effective.
Suggestions
Replace vague phrases like 'manage data, records, and automate workflows' with specific PDF operations such as 'extract text from PDFs, merge documents, convert file formats, compress PDFs, fill PDF forms, add watermarks'.
Expand the 'Use when...' clause with natural trigger terms users would say, e.g., 'Use when the user wants to extract text from PDFs, merge PDF files, convert documents to PDF, compress .pdf files, or automate PDF processing workflows.'
Remove the circular reference to 'Adobe PDF Services data' in the trigger clause and instead describe concrete scenarios or file types that should activate this skill.
| 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 PDFs, converting formats, filling forms, or any other concrete operations. | 1 / 3 |
Completeness | It has a 'Use when...' clause, which is good, but the 'what' is extremely vague ('manage data, records, and automate workflows') and the 'when' is equally vague ('interact with Adobe PDF Services data'). The trigger guidance is circular rather than providing explicit, useful triggers. | 2 / 3 |
Trigger Term Quality | It includes 'Adobe PDF Services' and 'PDF' which are relevant keywords, but misses natural user terms like 'PDF', '.pdf', 'extract text', 'merge documents', 'convert PDF', 'compress PDF', or other action-oriented terms users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Adobe PDF Services' is a specific product name which helps with distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with many other integration or data management skills. The description doesn't clearly carve out a unique niche beyond the product name. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, actionable CLI commands for integrating with Adobe PDF Services via Membrane, which is its primary strength. However, it wastes tokens explaining what Adobe PDF Services is and listing all operations upfront, and the workflow could benefit from explicit numbered steps with validation checkpoints. The content structure is flat with no progressive disclosure to supplementary files.
Suggestions
Remove the introductory paragraph explaining what Adobe PDF Services is — Claude already knows this. Start directly with the Membrane CLI integration instructions.
Add explicit numbered workflow steps with validation checkpoints, e.g., verify connection was created successfully before proceeding to action discovery.
Move the full operations list to a separate reference file and keep only a brief mention in the main skill file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Adobe PDF Services is and its common use cases — information Claude already knows. The operations list is somewhat useful but bulky. The best practices section has some unnecessary elaboration. Overall mostly efficient but with clear areas to tighten. | 2 / 3 |
Actionability | Provides fully executable CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Commands are copy-paste ready with clear placeholder conventions. | 3 / 3 |
Workflow Clarity | The workflow steps are present and sequenced (install → authenticate → connect → discover → create/run), but there's no explicit validation or error-handling feedback loop for running actions. The action creation section has a polling loop with state checking, which is good, but the overall workflow lacks numbered sequential steps and verification checkpoints. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with headers, but everything is in one monolithic file. The operations list and best practices could be separated. There are no references to supplementary files for advanced topics. The external docs link is provided but no internal progressive disclosure structure exists. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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
- Commit
56d7336
- Reviewed
Table of Contents
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.