CtrlK
BlogDocsLog inGet started
Tessl Logo

erxes

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

61

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

Quality

Content

82%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 is highly actionable with copy-paste CLI commands and a solid connection workflow including validation checkpoints, organized into clean sections. Its main weaknesses are minor verbosity and a dangling step reference that breaks the otherwise clear sequence.

Suggestions

Fix the broken step numbering: label 'Step 1a' and add an actual 'Step 2' section (or replace 'skip to Step 2' with a concrete anchor like 'Searching for actions') so the cross-reference resolves.

Trim narrative asides such as 'so you can focus on the integration logic rather than auth plumbing' to keep the body lean.

Consider moving the proxy options table and the full clientAction state-handling detail into a references file and linking to it, since the body exceeds the simple-skill threshold.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable commands with only minor over-explanation (e.g., 'so you can focus on the integration logic rather than auth plumbing' and the connector auto-build aside) that could be trimmed, fitting the 4 anchor.

4 / 5

Actionability

It provides copy-paste-ready, fully executable commands across the common cases (install, login, connection ensure, action list/run, proxy request) with a concrete options table, matching the 5 anchor.

5 / 5

Workflow Clarity

The connect-to-Erxes flow has a clear sequence with polling feedback loops and state handling (READY, CLIENT_ACTION_REQUIRED, re-poll, error states), but the dangling 'skip to Step 2' reference with no labeled Step 1a/Step 2 is a minor clarity gap keeping it below 5.

4 / 5

Progressive Disclosure

Content is well-organized into clearheaded sections with no broken or deeply nested references, and no bundle files exist to point to; it stays at 4 rather than 5 because the file exceeds 50 lines and all detail is inlined rather than split into referenced files.

4 / 5

Total

17

/

20

Passed

Description

62%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 answers both what and when with an explicit 'Use when' trigger and a named platform, but its action verbs are generic and the trigger phrasing lacks specific synonyms. Tightening the actions and adding concrete trigger terms would lift it toward the top anchors.

Suggestions

Replace generic verbs with concrete Erxes operations (e.g., 'manage contacts, conversations, tickets, and automation workflows') to improve specificity.

Add natural trigger synonyms users actually say, such as 'Erxes contacts', 'Erxes tickets', or 'Erxes marketing automation', to broaden trigger-term coverage.

Make the 'when' clause more specific by listing the Erxes modules the skill covers (Company, Conversation, Integration, Product, Ticket).

DimensionReasoningScore

Specificity

Names the Erxes domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete operations, so it is not comprehensive enough for a 4.

3 / 5

Completeness

Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Erxes data') are present; the 'when' clause could be more specific, matching the 4 anchor rather than 5.

4 / 5

Trigger Term Quality

Includes some relevant natural terms ('Erxes', 'data', 'records', 'workflows', 'interact with Erxes data') but misses common synonyms and variations a user might say, falling short of good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

Naming the specific Erxes platform gives it a clear niche with minimal conflict risk, but the surrounding generic action language ('manage data', 'automate workflows') leaves minor overlap risk with other CRM/marketing skills.

4 / 5

Total

14

/

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.

Validation15 / 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
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.