Name: relevance-ai
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

relevance-ai

Relevance AI integration. Manage Organizations, Users. Use when the user wants to interact with Relevance 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/relevance-ai/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 delivers concrete, executable CLI guidance with a clear sequenced workflow and validation states, but carries some conceptual over-explanation and a dangling step reference. It is effective and largely actionable.

Suggestions

Trim the opening paragraph explaining what Relevance AI is — Claude can infer the platform's purpose from its docs link.

Resolve the 'Skip to Step 2' references by labeling the corresponding section (e.g., '## Step 2: Searching for actions').

Consider moving the detailed clientAction state reference into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but explains concepts Claude already knows ('Relevance AI is a platform for building AI-powered search and recommendation experiences...') and pads Membrane auth rationale, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands for install, auth, connection, action list/run, and proxy with a clear flags table, but relies on unsubstituted placeholders (CONNECTION_ID, actionId, QUERY), leaving minor gaps below the fully-executable 5.	4 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clear with state-based validation checkpoints and an explicit feedback loop (CLIENT_ACTION_REQUIRED → complete → poll again), but the dangling 'Skip to Step 2' reference (no labeled Step 2) is a minor gap below the 5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist; content is a single well-organized file with clear section headers and easy navigation, but the slightly long inline detail on clientAction states could justify splitting, so it sits just below the 5 anchor.	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 names a distinct platform, but its action verbs are generic and trigger-term coverage lacks natural synonyms. It is solid but not comprehensive.

Suggestions

Replace the generic verb 'Manage' with specific actions (e.g., 'Create, list, update, and delete Organizations and Users').

Add natural trigger phrases users would actually say, e.g. 'Use when the user wants to list or create Relevance AI organizations, users, or datasets.'

Name concrete trigger keywords/synonyms beyond 'Organizations, Users' to improve distinctiveness and recall.

Dimension	Reasoning	Score
Specificity	Names the domain ('Relevance AI integration') and two concrete entity actions ('Manage Organizations, Users'), but the generic 'Manage' verb and limited entity list leave coverage non-comprehensive, fitting the '1-2 concrete actions' anchor rather than the 4.	3 / 5
Completeness	Both 'what' ('Manage Organizations, Users') and an explicit 'when' ('Use when the user wants to interact with Relevance AI data') are present, but the trigger clause is somewhat generic rather than concrete, placing it above the 3 anchor but below a fully concrete 5.	4 / 5
Trigger Term Quality	Includes relevant terms ('Relevance AI', 'Organizations', 'Users', 'interact with Relevance AI data') but misses common natural variations a user might say, matching the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	The named platform 'Relevance AI' creates a clear niche with minimal conflict risk, though the generic 'Manage Organizations, Users' could lightly overlap with other admin-style skills, so it sits just below the 5 anchor.	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/relevance-ai/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.