Name: rockset
Rating: 67.2 (1 reviews)
Author: membranedev

rockset

Rockset integration. Manage Collections, Queries, Views, Workspaces. Use when the user wants to interact with Rockset data.

Quality

80%

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

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 highly actionable with concrete executable commands and a clear connect-to-run workflow, well organized into sections. It loses points mainly on mild over-explanation and the absence of explicit validation checkpoints in the workflow.

Suggestions

Trim the introductory Rockset definition and the 'auth plumbing' prose to lift conciseness toward a fully lean 5.

Add an explicit verification checkpoint after connecting (e.g. confirm the connectionId is returned and usable with `connection list`) to give the workflow a validate-then-proceed loop.

Flesh out the 'Rockset Overview' entity tree or move it into a short reference so the overview reads as a navigable map rather than a bare bullet list.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-driven, but includes minor over-explanation ('Rockset is a real-time analytics database service in the cloud. Developers use it to build data-driven applications...' and 'so you can focus on the integration logic rather than auth plumbing'), fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready `npx @membranehq/cli@latest` commands with flags, JSON output, and parsed field paths (e.g. 'output.items[0].element?.id') covering login, connect, list, action run, and proxy — matches 'fully executable; specific examples cover the common cases'.	5 / 5
Workflow Clarity	A clear sequence exists (login → connect → discover actions → run/proxy) with conditional guidance ('When you are not sure if connection already exists'), matching 'clear sequence with most checkpoints present; minor validation gaps' — no explicit validate/verify feedback loop, so not 5.	4 / 5
Progressive Disclosure	Content is organized into clear sections (Overview, Working with Rockset, Popular actions, Best practices) with no bundle files present and a single external docs link, fitting 'good structure; most content appropriately placed; minor organization gaps' — the terse entity tree under 'Rockset Overview' is slightly underdeveloped, keeping it below 5.	4 / 5
	Total	17 / 20 Passed

Description

78%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 cleanly states what the skill does and when to use it, anchored to a specific named product with strong distinctiveness. Its main weakness is a generic trigger clause and missing common synonyms (SQL, real-time analytics) that would broaden natural-language matching.

Suggestions

Add natural trigger synonyms to the 'Use when' clause, e.g. 'Use when the user wants to run SQL queries, analyze real-time data, or interact with Rockset collections and views.'

Expand the capability list to cover the full surface area shown in the body (Query Lambdas, Virtual Instances, Integrations) so specificity reaches comprehensive coverage.

Tighten the 'when' phrasing with concrete trigger phrases the user would actually say, moving completeness from 4 toward 5.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage Collections, Queries, Views, Workspaces' — names the Rockset domain plus four concrete managed entities, matching the anchor 'lists several specific actions; minor gaps' rather than 3 (only 1-2 actions) or 5 (comprehensive coverage, which would need Lambdas/Virtual Instances/Integrations listed in the body).	4 / 5
Completeness	Explicitly answers what ('Rockset integration. Manage Collections, Queries, Views, Workspaces.') and when ('Use when the user wants to interact with Rockset data.'), matching 'has both what and when; when could be more explicit or specific' — the trigger clause is generic, so not a 5.	4 / 5
Trigger Term Quality	Includes 'Rockset', 'interact with Rockset data', and the entity names (Collections, Queries, Views, Workspaces) as natural keywords, fitting 'good keyword coverage; a few natural terms missing' — common variations like 'SQL queries' or 'real-time analytics' are absent, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	Names a specific product ('Rockset') with a distinct trigger ('interact with Rockset data'), giving a clear niche with minimal conflict risk against other skills — matches the top anchor.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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

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