CtrlK
BlogDocsLog inGet started
Tessl Logo

endorsal

Endorsal integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Endorsal data.

59

Quality

68%

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/endorsal/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 body delivers executable Membrane CLI guidance across setup, connection, discovery, and proxying with clear organization, but lacks validation/verification checkpoints for potentially destructive or batch operations.

Suggestions

Add explicit validation steps (e.g., verify a connection succeeded or an action returned expected fields) before proceeding to run actions.

Document how to inspect and handle error responses from action run and proxy requests.

Consider splitting the proxy flags table into a reference file once the skill grows.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and minimal conceptual padding, though a few sentences restate what Membrane does that could be trimmed.

4 / 5

Actionability

Provides concrete, executable CLI commands with flags and JSON examples covering connection, action discovery, and proxying, with minor gaps in parameter specifics.

4 / 5

Workflow Clarity

Sequences setup, connection, discovery, and execution steps, but lacks explicit validation checkpoints for batch/destructive operations and the proxy path, capping clarity at 3.

3 / 5

Progressive Disclosure

Well-organized sections with no bundle files; content stays in one file with clear headers and appropriate structure, with minor gaps.

4 / 5

Total

15

/

20

Passed

Description

67%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 clearly identifies the Endorsal integration domain and lists concrete entity types with an explicit use-when trigger, but trigger-term naturalness and specificity of actions could be stronger.

Suggestions

Add natural user-facing trigger phrases such as ‘when the user mentions testimonials, leads, or deals in Endorsal’.

Specify the key concrete actions per entity (create, update, list, delete) rather than the generic ‘Manage’.

Include file-format or noun synonyms users commonly say to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists many concrete entity types (Persons, Organizations, Deals, Leads, Projects, Activities) and a manage verb, giving broad coverage with minor gaps in describing each action.

4 / 5

Completeness

States what the skill does (manage Endorsal entities) and includes an explicit Use-when clause, though the trigger could be more specific.

4 / 5

Trigger Term Quality

Mentions Endorsal data interaction but lacks natural synonyms or common user phrasings a user would actually say; relies mostly on the domain name.

3 / 5

Distinctiveness Conflict Risk

The Endorsal niche is clearly named and tied to a specific integration, leaving only minor overlap risk with generic CRM skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
membranedev/application-skills
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.