CtrlK
BlogDocsLog inGet started
Tessl Logo

intercom

Intercom integration. Manage Users, Companies, Conversations, Admins, Tags, Segments and more. Use when the user wants to interact with Intercom data.

60

Quality

71%

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

Quality

Content

63%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 skill delivers strong, executable command-level guidance with a coherent connection workflow, but a massive inline enumeration of entities and redundant 'Search X' actions bloats the file and should be split into a reference file.

Suggestions

Move the 'Intercom Overview' entity/action enumeration into a separate reference file (e.g. references/entities.md) and keep only a brief summary in SKILL.md.

Collapse the 37 redundant 'Search X' entries into a single note that `membrane action list --intent` searches across all entities.

Fix the dangling 'Step 2' reference by labeling the action-search/run section as 'Step 2' or rewording the 'skip to' instruction.

DimensionReasoningScore

Conciseness

The ~190-line 'Intercom Overview' enumeration (every entity plus redundant 'Search X' entries for 37 entities) is a heavily padded section occupying most of the file, even though the instructional sections themselves are lean.

2 / 5

Actionability

Copy-paste-ready commands cover the full workflow (`npm install -g @membranehq/cli@latest`, `membrane connection ensure`, `membrane action list/run`, `membrane request`) plus a flag table, fully executable across common cases.

5 / 5

Workflow Clarity

A clear sequence (install -> auth -> connect -> poll for READY -> search -> run -> proxy) with state-based checkpoints and a poll-after-user-action feedback loop; minor gaps such as the undefined 'Step 2' reference prevent a 5.

4 / 5

Progressive Disclosure

Section structure is reasonable, but the large inline entity/action enumeration clearly belongs in a separate reference file and there are no bundle files or external references to offload it.

3 / 5

Total

14

/

20

Passed

Description

78%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.

A clear, mostly specific description that names the product and several concrete entities with an explicit 'Use when' trigger. It is held back from the top by the 'and more' hedge and a trigger clause that could enumerate more concrete scenarios.

DimensionReasoningScore

Specificity

It names the domain (Intercom) and lists several concrete entities ('Manage Users, Companies, Conversations, Admins, Tags, Segments'), but the 'and more' hedge and entity-listing rather than action-listing keep it just below comprehensive.

4 / 5

Completeness

Both 'what' (Manage Users, Companies, Conversations, ...) and 'when' ('Use when the user wants to interact with Intercom data') are present, but the 'when' could name more concrete scenarios to reach fully explicit trigger phrasing.

4 / 5

Trigger Term Quality

The prominent natural keyword 'Intercom' appears with an explicit natural trigger ('Use when the user wants to interact with Intercom data'); coverage of the domain's primary term is good, with only minor missing phrasing variations.

4 / 5

Distinctiveness Conflict Risk

'Intercom integration' and 'Intercom data' name a specific commercial product, giving the skill a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

17

/

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.