CtrlK
BlogDocsLog inGet started
Tessl Logo

intellexer-api

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

57

Quality

66%

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/intellexer-api/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 a strong, command-driven integration guide: highly actionable with runnable CLI commands, a clear connection state machine with feedback loops, and tidy sectioning. The main gaps are minor over-explanation in the intro, slightly inconsistent step numbering, and bulk action reference that could be split into a separate file.

DimensionReasoningScore

Conciseness

The body is mostly lean commands and tables with only minor over-explanation (the intro paragraph describing what Intellexer does and the auth-plumbing aside could be trimmed), matching the "efficient; minor instances of over-explanation" anchor.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure/get, action list/run, request proxy) plus a concrete actions table with real keys, matching the "fully executable; specific examples cover common cases" anchor.

5 / 5

Workflow Clarity

The connection lifecycle is a clear state machine with per-state next actions and a re-poll feedback loop, but the loose Step 2 / "1b" numbering and lack of an explicit checklist leave minor sequencing gaps, matching the "clear sequence with most checkpoints; minor gaps" anchor.

4 / 5

Progressive Disclosure

No bundle files exist and the body is a single well-organized file with clear section headers, but the long popular-actions table and connection-state detail are inlined where a separate reference file could help, matching the "good structure; minor organization gaps" anchor.

4 / 5

Total

17

/

20

Passed

Description

50%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 has both a what and an explicit Use-when trigger and names a distinct API, but its capability language ("manage data, records, automate workflows") is generic and lacks the concrete NLP actions and natural trigger terms that would make it specific. It reads as a templated integration description rather than a tailored one.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete capabilities the API provides, e.g. "Analyze sentiment, summarize documents, extract named entities, and compare texts."

Expand the trigger with natural user phrases: "Use when the user wants to analyze sentiment, summarize or extract text, recognize named entities, compare documents, or classify text via the Intellexer API."

Drop generic verbs like "manage data" and "records" that overlap with many other skills to sharpen distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain ("Intellexer API integration") but its actions are generic ("Manage data, records, and automate workflows") rather than the concrete NLP capabilities the API actually offers, matching the "names the domain but actions are minimal or generic" anchor.

2 / 5

Completeness

It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Intellexer API data"), but the what is vague and the when could be more specific, matching the "has both what and when; when could be more explicit" anchor.

4 / 5

Trigger Term Quality

Triggers rely almost entirely on the single brand term "Intellexer API" and lack the natural phrases users say (sentiment analysis, summarize, extract entities), matching the "one or two generic keywords; missing natural phrases" anchor.

2 / 5

Distinctiveness Conflict Risk

Tying the skill to the named Intellexer API gives it a distinct niche with minor overlap risk, though the generic action language keeps it from a 5, matching the "mostly distinct; minor overlap risk with closely related skills" anchor.

4 / 5

Total

12

/

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.