adobe-acrobat-sign
Adobe Acrobat Sign integration. Manage Users, Agreements, Widgets. Use when the user wants to interact with Adobe Acrobat Sign data.
75
70%
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-acrobat-sign/SKILL.mdQuality
Discovery
75%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 adequately identifies the product domain and provides an explicit 'Use when' clause, which is good for completeness. However, the capabilities listed are high-level entity types rather than specific actions, and the trigger terms miss common natural language phrases users might use when needing e-signature functionality. The strong product specificity helps with distinctiveness but the description could be more actionable.
Suggestions
Replace generic 'Manage' with specific actions like 'Create, send, and track signature agreements; manage signing widgets; add and configure users in Adobe Acrobat Sign.'
Add natural trigger terms users would say, such as 'e-signature', 'digital signature', 'send for signing', 'signature request', or 'signing workflow'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Adobe Acrobat Sign) and some actions ('Manage Users, Agreements, Widgets'), but the actions are high-level categories rather than specific concrete operations like 'create agreements', 'send for signature', 'check signing status'. | 2 / 3 |
Completeness | Answers both 'what' (manage Users, Agreements, Widgets in Adobe Acrobat Sign) and 'when' ('Use when the user wants to interact with Adobe Acrobat Sign data'), with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Adobe Acrobat Sign', 'Users', 'Agreements', 'Widgets' which are relevant but misses natural user terms like 'e-signature', 'digital signature', 'sign document', 'send for signing', or 'DocuSign alternative'. | 2 / 3 |
Distinctiveness Conflict Risk | Adobe Acrobat Sign is a very specific product, making this clearly distinguishable from other skills. The mention of the specific product name creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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.
This skill provides solid, actionable CLI commands for integrating with Adobe Acrobat Sign via Membrane, with good coverage of the full workflow from setup to execution. Its main weaknesses are unnecessary introductory content about what Adobe Acrobat Sign is, an empty-description actions table that wastes tokens, and missing validation/error-handling guidance for key workflow steps.
Suggestions
Remove the introductory paragraph explaining what Adobe Acrobat Sign is — Claude already knows this. Start directly with the overview or working instructions.
Either populate the Description column in the popular actions table or remove the column entirely to avoid wasting tokens on empty cells.
Add explicit error handling/validation steps after connection setup and action execution (e.g., 'Verify connection with `membrane connection list --json` and confirm status is active before proceeding').
Consider splitting the popular actions table and detailed CLI reference into a separate REFERENCE.md file, keeping SKILL.md as a concise quick-start guide.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Adobe Acrobat Sign is (cloud-based service, legally binding signatures, etc.) is unnecessary context Claude already knows. The popular actions table has empty description columns, wasting space. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, and running actions with parameters. The commands include specific flags like --json, --wait, and --timeout with clear explanations. | 3 / 3 |
Workflow Clarity | The workflow follows a logical sequence (install → authenticate → connect → search → run), and the action creation flow includes polling with state checking (BUILDING → READY/error). However, there are no explicit validation checkpoints or error recovery feedback loops for the main workflow steps like connection setup or action execution. | 2 / 3 |
Progressive Disclosure | The content is structured with clear sections and headers, but it's somewhat monolithic — the popular actions table and detailed CLI usage could be split into separate reference files. The overview section listing Agreement/Widget/Library Document hierarchy adds little value inline without linking to deeper documentation. | 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.