airslate
Airslate integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airslate data.
61
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/airslate/SKILL.mdQuality
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 product domain (Airslate) and includes an explicit 'Use when' clause, which is good for completeness. However, the capabilities listed are vague ('manage data, records, and automate workflows') and could describe many integration tools. Adding more specific actions and Airslate-specific terminology would significantly improve both specificity and distinctiveness.
Suggestions
Add specific concrete actions such as 'create and manage Airslate documents, configure automation bots, query slate records, trigger workflow runs' to improve specificity.
Expand trigger terms to include variations users might say, such as 'airSlate', 'slates', 'automation bots', 'document workflows', or specific Airslate feature names.
Differentiate from generic workflow/automation skills by mentioning Airslate-specific concepts (e.g., 'slates', 'flow templates', 'bots') in the description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Airslate) and some actions ('manage data, records, and automate workflows'), but these are fairly generic and not comprehensive — it doesn't list specific concrete actions like creating documents, triggering flows, or querying specific record types. | 2 / 3 |
Completeness | It answers both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Airslate data), with an explicit 'Use when...' clause providing trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Airslate' as a key trigger term and mentions 'data', 'records', and 'workflows', but misses common variations users might say such as 'airSlate', 'automation', 'bots', or specific Airslate product features. The terms are somewhat generic beyond the product name. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is quite generic and could overlap with other integration or workflow automation skills. However, the explicit mention of 'Airslate' as the product name provides some distinctiveness that reduces conflict risk. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear CLI commands and well-structured connection workflows including state-based branching and error handling. Its main weaknesses are unnecessary introductory explanation about what AirSlate is, an unexpanded overview section that adds no value, and a monolithic structure that could benefit from splitting reference material (like the actions table) into separate files.
Suggestions
Remove the introductory paragraph explaining what AirSlate is and the bare overview bullet list (Slate, Template, Bot, etc.) — these waste tokens without adding actionable guidance.
Extract the popular actions table and proxy request reference into separate files (e.g., ACTIONS.md, PROXY.md) and link to them from the main skill for better progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what AirSlate is ('a document workflow automation platform... no-code solution for automating paperwork') is unnecessary context for Claude. The overview bullet list of concepts (Slate, Template, Bot, Flow, etc.) adds no actionable value. The popular actions table is useful but lengthy. Overall mostly efficient with some bloat. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and JSON output options. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR/SETUP_FAILED), polling instructions, and clear next steps for each state. The headless auth flow includes a feedback loop (user completes login → finish with code). The overall flow from install → auth → connect → discover → run is well-sequenced. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents. The popular actions table and proxy request details could be split into separate reference files. The overview section with unexplained bullet points (Bot, Flow, Integration) hints at content that should either be expanded elsewhere or removed. No bundle files exist to offload detail. | 2 / 3 |
Total | 10 / 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
f484c82
- 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.