Name: vectara
Rating: 59.2 (1 reviews)
Author: membranedev

vectara

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

Quality

68%

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/vectara/SKILL.md

Quality

Content

75%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 highly actionable CLI integration guide with executable commands and a clear, checkpoint-driven connection workflow. Its main weakness is conciseness: some conceptual prose and a redundant command repetition could be trimmed, and the step numbering is slightly inconsistent.

Suggestions

Trim conceptual and padded prose such as the 'Vectara is a platform...' opener and 'so you can focus on the integration logic rather than auth plumbing', which explain things Claude can infer.

Remove the redundant action-list command repeated under 'Popular actions' (it duplicates the 'Searching for actions' section), or consolidate the two sections.

Fix the inconsistent workflow numbering — the '#### 1b. Wait for the connection' header and the reference to 'Step 2' (which is never labeled) break the step sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven, but includes unnecessary prose such as the opener 'Vectara is a platform for building powerful search and retrieval applications using neural networks...' and 'so you can focus on the integration logic rather than auth plumbing', plus a redundant repeat of the action-list command in 'Popular actions'; this fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the leaner anchor at 4.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure/get with --wait, action list/run, request proxy) plus a flags table and output-field explanations, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-until-ready → search → run/proxy sequence with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll feedback loop, fitting 'clear sequence with most checkpoints present'; it stays at 4 rather than 5 because the step numbering is inconsistent (a '1b' subsection and references to an unlabeled 'Step 2').	4 / 5
Progressive Disclosure	The content is organized into well-labeled sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested or buried references and no bundle files needed for this CLI skill, fitting 'good structure; most content is appropriately placed; minor organization gaps'; it does not reach 5 because the monolithic body is over 50 lines with some inline material (the flags table, clientAction state detail) that a denser skill might split out.	4 / 5
	Total	16 / 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 clearly identifies the Vectara niche and includes an explicit 'Use when' trigger, but its action verbs are generic rather than reflecting Vectara's actual search/retrieval capabilities and it relies on a single trigger keyword. It is solid but leaves room for more concrete, Vectara-specific language.

Suggestions

Replace the generic verbs ('Manage data, records, and automate workflows') with Vectara-specific actions such as 'create corpora, index documents, and run neural search and retrieval queries'.

Broaden trigger terms beyond just 'Vectara data' to include natural phrases users say, e.g. 'search', 'retrieval', 'corpora', 'index documents', and 'query'.

Tighten the 'what' clause so it lists concrete capabilities that distinguish Vectara from general data-management skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain and 2-3 actions, but the verbs are generic rather than Vectara-specific (no mention of corpora, indexing, or neural search), matching the '1-2 concrete actions, not comprehensive' anchor; it is above score 2 because multiple actions are listed, but below 4 because none are tied to Vectara's actual capabilities.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Vectara data') are present, matching the 'has both what and when; when could be more explicit or specific' anchor; it falls short of 5 because the 'what' is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	The only real trigger keyword is 'Vectara' (in 'interact with Vectara data'); natural synonyms users would say such as 'search', 'retrieval', 'corpora', or 'index' are missing, fitting 'some relevant keywords but missing common variations or synonyms' rather than the fuller coverage at 4.	3 / 5
Distinctiveness Conflict Risk	The named product 'Vectara' plus the trigger 'interact with Vectara data' give it a clear niche with minimal conflict risk, fitting 'mostly distinct; minor overlap risk'; it does not reach 5 because the generic 'manage data, records, workflows' verbs could overlap with other data-management 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/vectara/SKILL.md
Commit: f484c82

Reviewed: 3 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.