CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

airslate

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/airslate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The content is highly actionable, with executable commands and explicit connection-state validation covering the full workflow. Weaknesses are concentrated in conciseness (marketing-style intro and an empty entity list) and minor structural inconsistencies (dangling 'Step 2' reference, '1b' numbering).

Suggestions

Delete or fix the "Airslate Overview" bullet list — either give each entity (Slate, Template, Bot, Flow, User, Organization, Integration) a one-line description or remove the section, since the current list names entities with no value and has a broken nesting.

Replace the "Step 2" / "1b" numbering with a coherent numbered sequence (1, 2, 3...) and add a brief post-run step for checking the `output` field to confirm the action succeeded.

Trim the intro to one factual sentence (e.g. "AirSlate is a document workflow automation platform; official docs: https://developers.airslate.com/"), removing the marketing filler and the ungrammatical Agent Types sentence.

DimensionReasoningScore

Conciseness

The body is mostly command-focused and efficient, but contains unnecessary padding: the marketing-style intro ("It's used by businesses of all sizes to streamline... Think of it as a no-code solution for automating paperwork"), an "Airslate Overview" bullet list that names seven entities with no descriptions and a malformed nesting (Template indented under Slate), and ungrammatical filler ("Those will be used to adjust tooling to be used best with your harness"). Fits 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not a 4 because these are more than minor trimmable instances, not a 2 because the bulk is lean, executable instruction.

3 / 5

Actionability

Every section provides copy-paste-ready commands: `npm install -g @membranehq/cli@latest`, `membrane login --tenant --clientName=<agentType>` (including headless completion with `membrane login complete <code>`), `membrane connection ensure "https://www.airslate.com/" --json`, `connection get <id> --wait --json`, `action list --intent "QUERY" --limit 10 --json`, `action run <actionId> --input '{"key": "value"}' --json`, and a full flag table for `membrane request`. Matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'; no missing details were found that would drop it to 4.

5 / 5

Workflow Clarity

A clear install → authenticate → connect → poll-until-ready → search → run → proxy-fallback sequence exists, with explicit state-based validation (READY / CLIENT_ACTION_REQUIRED with a clientAction breakdown / CONFIGURATION_ERROR or SETUP_FAILED) and a re-poll feedback loop after the user completes an action. Not a 5 because "skip to **Step 2**" references a step label that does not exist (only an inconsistent "1b" heading appears) and there is no guidance for verifying action output after running. Not a 3 because checkpoints are explicit, not merely implicit.

4 / 5

Progressive Disclosure

The ~160-line body is organized under clear section headers (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no nested or buried references, and the popular-actions catalog is appropriately inline as the core content. No bundle files exist, so there are no reference paths to verify. Matches 'Good structure; most content is appropriately placed; minor organization gaps' — the malformed overview list, inconsistent step numbering, and the arguably-reference-sized action table keep it below 5; there is no monolithic wall or misplaced content that would justify a 3.

4 / 5

Total

16

/

20

Passed

Description

57%Weight 40%Scale 1-5

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 names a clear niche (Airslate via an explicit 'Use when' clause) but describes capabilities in generic terms. Strengthening the action list with concrete capabilities and richer trigger vocabulary would materially improve it.

Suggestions

Replace generic phrases with concrete capabilities, e.g. "List and create organizations, templates, workflows, and webhooks; run workflows to generate documents and send them for e-signature; send direct API requests through a managed proxy."

Add natural trigger terms users would actually say: documents, e-signature, forms, slates, Flowbots, document routing.

Broaden the 'Use when' clause beyond "interact with Airslate data" to cover workflow automation and document/signature tasks, which are the platform's primary use cases.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" are generic action phrases rather than concrete capabilities (no mention of what is actually done, e.g. creating templates, running workflows for e-signature, managing webhooks). This matches the anchor 'Names the domain but actions are minimal or generic'; it is not a 3 because none of the named actions are concrete, and not a 1 because the domain is clearly named alongside several action verbs.

2 / 5

Completeness

Both parts are present: a "what" ("Airslate integration. Manage data, records, and automate workflows") and an explicit trigger clause ("Use when the user wants to interact with Airslate data"). Not a 5 because the what is vague and the when is narrow (misses workflow automation, documents, and e-signature triggers); not a 3 because an explicit 'Use when...' clause is present.

4 / 5

Trigger Term Quality

Includes "Airslate", "data", "records", "workflows", and "automate" — some relevant keywords — but misses the natural terms a user would say such as documents, e-signature, forms, slates, or Flowbots. This fits 'Some relevant keywords but missing common variations or synonyms'; not a 4 because coverage beyond the brand name is thin and generic.

3 / 5

Distinctiveness Conflict Risk

"Airslate" is a specific branded platform, giving the skill a clear niche, but the unqualified phrases "Manage data, records" and "automate workflows" could overlap with generic data-management or automation skills. Matches 'Mostly distinct; minor overlap risk with closely related skills'; not a 5 because the generic action terms weaken the distinct trigger surface.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

membranedev/application-skills

Path

skills/airslate/SKILL.md

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.