Name: expertai
Rating: 56.8 (1 reviews)
Author: membranedev

expertai

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/expertai/SKILL.md

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 body is action-oriented and well-sequenced with strong connection-state validation, but it carries a marketing-style opening and a few broken cross-references. Trimming padding and fixing the 'Step 2' references would tighten it without losing substance.

Suggestions

Delete or compress the opening 'Expert.ai is a natural language understanding platform...' marketing paragraph and explanatory asides; Claude does not need a product overview.

Fix the broken 'skip to Step 2' references by either defining a Step 2 header or rewriting them as concrete next-action pointers (e.g. 'proceed to Searching for actions').

Consider moving the proxy request flags table and the clientAction field schema into a references/ file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient concrete CLI commands, but the opening marketing paragraph ('helps businesses analyze and understand text data... used by data scientists, developers, and business analysts') and asides like 'so you can focus on the integration logic rather than auth plumbing' explain concepts Claude does not need.	3 / 5
Actionability	Provides many concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a flags table, with only minor gaps such as unsubstituted placeholders (CONNECTION_ID, <actionId>) and no fully worked example with real values.	4 / 5
Workflow Clarity	The connection flow has an explicit state machine (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) with polling and re-poll recovery checkpoints, but cross-references like 'skip to Step 2' point to a section that is never defined, leaving a minor clarity gap.	4 / 5
Progressive Disclosure	The body is well-structured with clear section headers and no nested references, and all content sits one level deep in a single file; minor gaps are the inlined proxy flags table and clientAction schema that could live in a reference file for a ~140-line skill.	4 / 5
	Total	15 / 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 and is clearly tied to a distinct product, but its action list and trigger vocabulary are generic rather than concrete. Adding Expert.ai-specific natural-language trigger terms would lift the lower dimensions.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Expert.ai capabilities such as text classification, sentiment analysis, entity recognition, and knowledge-graph traversal.

Add natural trigger phrases users would actually say, e.g. 'Use when the user wants NLP analysis, text classification, sentiment analysis, or to query the Expert.ai knowledge graph.'

Keep the explicit 'Use when...' clause but make the trigger list more specific to reduce overlap with generic data-integration skills.

Dimension	Reasoning	Score
Specificity	Names the domain ("Expert.ai") and a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete capabilities, matching the anchor for naming a domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	Both 'what' ("Manage data, records, and automate workflows") and 'when' ("Use when the user wants to interact with Expert.ai data") are present, but the 'when' is generic rather than concrete trigger phrases, fitting the 'has both but when could be more specific' anchor.	4 / 5
Trigger Term Quality	"interact with Expert.ai data" supplies the product name, but natural synonyms a user would actually say (NLP, text analysis, natural language understanding, sentiment) are absent, so it sits at 'some relevant keywords, missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the named Expert.ai platform gives a clear niche with low conflict risk, though the generic 'data, records, workflows' phrasing leaves minor overlap with other data-integration skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/expertai/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.