CtrlK
BlogDocsLog inGet started
Tessl Logo

intercom-articles

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

56

Quality

64%

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

Quality

Content

67%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-sequenced with a solid connection-state feedback loop, but it carries some unnecessary explanation and redundancy that could be trimmed for token efficiency.

Suggestions

Cut the introductory paragraph explaining what Intercom Articles is and the 'so you can focus on the integration logic' padding; lead with the install/connect commands.

Merge the 'Popular actions' section into 'Searching for actions' to remove the duplicated `membrane action list` command.

Add a brief validation note for destructive proxy requests (e.g. confirm the method/endpoint before running POST/PUT/DELETE) to strengthen the execution workflow.

DimensionReasoningScore

Conciseness

The body is mostly commands but opens with a platform explanation Claude largely knows and includes padding ('so you can focus on the integration logic rather than auth plumbing') plus a redundant 'Popular actions' section that repeats the action-list command.

3 / 5

Actionability

It provides concrete, copy-paste CLI commands with flags throughout (login, connection ensure, action list/run, proxy request table), with only minor gaps such as literal 'QUERY' placeholders.

4 / 5

Workflow Clarity

There is a clear install→login→connect→search→run sequence with an explicit feedback loop on connection state (poll, handle CLIENT_ACTION_REQUIRED, re-poll), though action/proxy execution lacks post-run validation.

4 / 5

Progressive Disclosure

The single file is well-organized into clear sections with no external references needed, though the duplicated action-list command between 'Searching for actions' and 'Popular actions' is a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

61%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 distinct and includes an explicit 'Use when' trigger, but its action list is generic ('manage data, records, automate workflows') and lacks the concrete operations and synonyms that would strengthen activation.

Suggestions

Replace generic verbs with concrete Intercom Articles actions, e.g. 'Create, translate, and organize help articles; search and manage collections'.

Add natural trigger synonyms such as 'help center', 'knowledge base', or 'help articles' so users phrasing it differently still activate the skill.

Tighten the 'what' to mirror the skill's actual Article/Translation/Collection/Assistant/Search capabilities listed in the body.

DimensionReasoningScore

Specificity

The description names the domain (Intercom Articles) but its actions — 'Manage data, records, and automate workflows' — are generic categories rather than concrete operations like creating or translating articles.

2 / 5

Completeness

Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with Intercom Articles data' trigger are present, though the 'what' is generic.

4 / 5

Trigger Term Quality

It surfaces the product name 'Intercom Articles' as a trigger but misses natural synonyms a user might say, such as 'help center', 'knowledge base', or 'help articles'.

3 / 5

Distinctiveness Conflict Risk

The named product 'Intercom Articles' gives it a clear niche with a distinct trigger and minimal risk of conflicting with unrelated skills.

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