Name: escape
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

escape

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

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/escape/SKILL.md

Quality

Content

60%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 actionable and well-structured with executable commands and a clear connection workflow, but it carries some trimmable explanatory prose and inconsistent step numbering. Splitting lengthy reference-style detail into bundle files would further improve disclosure.

Suggestions

Trim the product-introduction paragraph and rhetorical asides ('so you can focus on the integration logic') to assume Claude's competence and improve conciseness.

Fix the step labeling so the referenced 'Step 2' is actually numbered, and add an explicit validation checkpoint after `membrane action run` to confirm the expected `output` was returned.

Move the proxy flag table and the clientAction schema detail into a references file (e.g., references/proxy.md) and link to it from the body to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with command tables and code blocks, but the intro paragraph explaining what Escape is and phrases like 'so you can focus on the integration logic rather than auth plumbing' add unnecessary prose that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands across install, auth, connection, search, run, and proxy (e.g., `membrane action run <actionId> --connectionId=CONNECTION_ID --json`), with only minor gaps such as unfilled placeholders and a literal QUERY intent.	4 / 5
Workflow Clarity	The connection setup is sequenced with state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling feedback loop, but step labeling is inconsistent (a 'Step 2' is referenced yet never labeled) and action-result validation is implicit.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections with no nested or broken references, but at ~145 lines with inline detail like the full proxy-flag table and clientAction schema, some content could be split into reference files.	4 / 5
	Total	15 / 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 is well-structured with an explicit 'Use when' trigger and a clear product anchor, but the capability language is generic. Tightening the action verbs to concrete Escape capabilities would lift specificity.

Suggestions

Replace generic verbs with concrete Escape capabilities (e.g., 'scan web applications for vulnerabilities, manage scan schedules, and triage security findings') to improve specificity.

Add natural synonyms and product-specific trigger terms (e.g., 'Escape scans', 'vulnerability reports', 'escape.tech') so the description matches phrases users actually say.

Keep the explicit 'Use when' clause but tie it to specific Escape tasks rather than the broad 'interact with Escape data'.

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the Escape domain but the actions are generic and abstract rather than concrete API-level capabilities, fitting the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It provides both a 'what' ("Escape integration. Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Escape data"), matching the anchor where both are present though the 'what' could be more concrete.	4 / 5
Trigger Term Quality	It includes the product keyword "Escape" and one natural trigger phrase ("Use when the user wants to interact with Escape data"), but lacks synonyms or variations beyond the single product name.	3 / 5
Distinctiveness Conflict Risk	The description is anchored to the specific Escape product, giving it a distinct niche with only minor overlap risk against other SaaS-integration skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/escape/SKILL.md
Commit: f484c82

Reviewed: ~19 hours ago

Table of Contents

Discovery Implementation Validation

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.