Name: vectorizedio
Rating: 58.4 (1 reviews)
Author: membranedev

vectorizedio

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

Quality

67%

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

Quality

Content

72%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 action-oriented and well-structured with executable commands throughout, scoring high on conciseness, actionability, and progressive disclosure. Its main weakness is the absence of validation/verification steps around action execution and proxy requests, which caps workflow clarity.

Suggestions

Add a verification step after running actions or proxy requests, e.g. check the `output`/`error` fields and surface failures before proceeding, to lift workflow clarity above the cap.

Trim the marketing-style opening sentence and de-duplicate the action-discovery recipe, which currently appears in both "Searching for actions" and "Popular actions".

Clarify how to resolve the actionId/CONNECTION_ID placeholders (e.g. note that CONNECTION_ID comes from the earlier `connection ensure` step).

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with little concept padding, but the opening "high-performance streaming platform" sentence is mild marketing fluff and the action-list recipe is repeated in both "Searching for actions" and "Popular actions".	4 / 5
Actionability	It provides concrete, copy-pasteable bash commands and a flag reference table for the common cases, with only minor gaps such as the actionId/CONNECTION_ID placeholders the user must fill in.	4 / 5
Workflow Clarity	The connection flow has a clear state machine and polling loop, but running actions and proxying requests can be destructive or batch operations with no output validation or verify step, so workflow clarity is capped at 3 per the rubric.	3 / 5
Progressive Disclosure	The skill is a single well-organized SKILL.md under 150 lines with no external bundle files, and the simple-skill guidance allows a 5 when sections are clear and well-structured, which they are.	5 / 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 answers both what and when and is clearly tied to a distinct product, but its action verbs are generic and its trigger terms lack natural synonyms or variations. It sits solidly above average but short of the comprehensive-anchor examples.

Suggestions

Replace generic verbs ("Manage data, automate workflows") with concrete actions a user would request, e.g. "search records, query namespaces, run actions, proxy API requests".

Add natural trigger synonyms and product variants to the "Use when" clause, e.g. "Use when the user wants to query Vectorized.io records, namespaces, or the vector database".

Specify the trigger more concretely than "interact with data" by naming the operations users will ask for (search records, automate workflows via actions).

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain plus a couple of actions, but the verbs (manage, automate) are generic rather than concrete, matching the 1-2-action anchor rather than the comprehensive 5-anchor.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Vectorized.io data"), but the when clause is generic rather than a concrete trigger phrase, which is the 4-anchor rather than the explicit 5-anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Vectorized.io data" surfaces the natural product name and intent phrase, but offers few synonyms or variations a user might actually say, fitting the some-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill specifically to Vectorized.io gives it a clear niche with minimal overlap risk, though the generic verbs leave slight ambiguity about scope versus 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/vectorizedio/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.