airslate
Airslate integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airslate data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill airslate72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 integration target (Airslate) and includes an explicit 'Use when' clause, which is good. However, the capabilities listed are vague ('manage data, records') and could apply to dozens of different tools. The description would benefit from more specific Airslate-related actions and additional trigger terms.
Suggestions
Add specific Airslate capabilities like 'create and send documents for e-signature', 'build document workflows', or 'manage Slate templates' to improve specificity.
Include additional trigger terms users might naturally say, such as 'e-signature', 'document automation', 'workflow builder', or 'Slate forms'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Airslate) and mentions some actions ('Manage data, records, and automate workflows'), but these are fairly generic and not comprehensive - doesn't specify what kinds of data, records, or workflows. | 2 / 3 |
Completeness | Answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Airslate data') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Airslate' as the primary trigger term, but lacks common variations or related terms users might say (e.g., 'air slate', document automation, e-signatures, workflow automation platform). | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is generic and could overlap with many other integration or automation skills. The 'Airslate' brand name provides some distinction, but the actions described are not unique. | 2 / 3 |
Total | 9 / 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 Airslate integration via Membrane, with a useful actions reference table. However, it wastes tokens on unnecessary platform explanations Claude already knows, and lacks validation/error-handling guidance for the multi-step connection workflow. The structure is adequate but could benefit from trimming the overview and adding verification steps.
Suggestions
Remove the opening paragraph explaining what AirSlate is and the empty 'Overview' bullet list - Claude already knows this context
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failures like authentication timeout or invalid connector ID
Move the large 'Popular actions' table to a separate ACTIONS.md reference file to improve scannability
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what AirSlate is wastes tokens on information Claude already knows. The 'Overview' section with bullet points adds no actionable value. However, the CLI commands and action tables are appropriately concise. | 2 / 3 |
Actionability | Provides fully executable CLI commands for every operation: installation, login, connection, searching actions, and running actions. The commands are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the popular actions table is quite long and could be referenced externally. The overview section adds little value and could be removed or condensed. No external file references for advanced topics. | 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 | |
- 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.