Rockset

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

Security Scan

The skill's purpose (Rockset integration) is plausible, but the runtime instructions rely on running npx to fetch and execute @membranehq/cli, write credentials to ~/.membrane/credentials.json, and require a Membrane account — none of which are declared in the registry metadata, creating coherence and supply-chain concerns.

Purpose & Capability

The skill's stated purpose (manage Rockset via Membrane) aligns with the instructions: it delegates Rockset interactions to Membrane actions and a proxy. However, the manifest claims no required binaries, env vars, or config paths, while the SKILL.md clearly requires npx (Node/npm) and a Membrane account — an inconsistency.

Instruction Scope

The SKILL.md tells the agent to run npx @membranehq/cli@latest (which fetches and executes remote code), open a browser for authentication, and that credentials will be stored at ~/.membrane/credentials.json. It also documents a proxy that will forward arbitrary HTTP requests (including full URLs). These are within the nominal scope of a proxy-based Rockset integration, but they expand the agent's actions (network fetch+execute, reading/writing a home config file, browser-based auth) beyond what the registry metadata declares.

Install Mechanism

There is no install spec, which is low-risk normally, but the instructions rely on npx @membranehq/cli@latest — a live fetch and execution of a package from the npm registry. Using npx with @latest means code executed at runtime is uncontrolled and can change; this is a moderate supply-chain risk that's not documented in the manifest.

Credentials

The registry lists no required env vars or config paths, yet SKILL.md requires a Membrane account and will create/use ~/.membrane/credentials.json for auth. That undeclared persistent credential storage is a proportionality/misreporting issue. The skill does not request unrelated credentials, but it does create and rely on a local credential file without declaring it.

Persistence & Privilege

always is false and autonomous invocation is allowed (normal). The skill will persist credentials in the user's home (~/.membrane/credentials.json) after login, which is expected for a CLI-based integration but is not reflected in the declared required config paths. It does not request system-wide privileges or modify other skills.

What to consider before installing

What to consider before installing: - The skill uses npx @membranehq/cli@latest: npx will download and execute code from npm at runtime. Only proceed if you trust the @membranehq package and its publisher; consider installing and auditing the CLI yourself instead of letting the skill fetch @latest automatically. - The SKILL.md will create ~/.membrane/credentials.json to store auth tokens after browser login. If you are uncomfortable with tokens stored locally, don't use this flow or inspect the file and its permissions. - The registry metadata omits required runtime pieces (Node/npm and the credential file). This mismatch could be benign (author oversight) but also hides risks; ask the publisher for a homepage, package repository, and verification of the Membrane CLI package. - The proxy can forward arbitrary HTTP requests — verify the agent will only send requests you expect (to Rockset) and not arbitrary external endpoints. If you decide to proceed: pin the CLI to a known-good version (avoid @latest), install the CLI yourself from a trusted source, and verify or sandbox the credential file and network access. If you need higher assurance, request the skill author add explicit manifest entries for required binaries and config paths and provide a homepage/repository for review.

Rockset is a real-time analytics database service in the cloud. Developers use it to build data-driven applications that require sub-second query latency and high concurrency.

Official docs: https://rockset.com/docs/

Rockset Overview

• Query
  • Query Lambdas
• Collection
• Virtual Instance
• Workspace
• Account
• User
• Organization
• Role
• Integration
• API Key

Use action names and parameters as needed.

Working with Rockset

This skill uses the Membrane CLI (npx @membranehq/cli@latest) to interact with Rockset. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

First-time setup

npx @membranehq/cli@latest login --tenant

A browser window opens for authentication. After login, credentials are stored in ~/.membrane/credentials.json and reused for all future commands.

Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with npx @membranehq/cli@latest login complete <code>.

Connecting to Rockset

1. Create a new connection:

   npx @membranehq/cli@latest search rockset --elementType=connector --json
   

   Take the connector ID from output.items[0].element?.id, then:

   npx @membranehq/cli@latest connect --connectorId=CONNECTOR_ID --json
   

   The user completes authentication in the browser. The output contains the new connection id.

Getting list of existing connections

When you are not sure if connection already exists:

1. Check existing connections:

   npx @membranehq/cli@latest connection list --json
   

   If a Rockset connection exists, note its connectionId

Searching for actions

When you know what you want to do but not the exact action ID:

npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json

This will return action objects with id and inputSchema in it, so you will know how to run it.

Popular actions

Use npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json to discover available actions.

Running actions

npx @membranehq/cli@latest action run --connectionId=CONNECTION_ID ACTION_ID --json

To pass JSON parameters:

npx @membranehq/cli@latest action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"

Proxy requests

When the available actions don't cover your use case, you can send requests directly to the Rockset API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.

npx @membranehq/cli@latest request CONNECTION_ID /path/to/endpoint

Common options:

Flag	Description
-X, --method	HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET
-H, --header	Add a request header (repeatable), e.g. -H "Accept: application/json"
-d, --data	Request body (string)
--json	Shorthand to send a JSON body and set Content-Type: application/json
--rawData	Send the body as-is without any processing
--query	Query-string parameter (repeatable), e.g. --query "limit=10"
--pathParam	Path parameter (repeatable), e.g. --pathParam "id=123"

You can also pass a full URL instead of a relative path — Membrane will use it as-is.

Best practices

• Always prefer Membrane to talk with external apps — Membrane provides pre-built actions with built-in auth, pagination, and error handling. This will burn less tokens and make communication more secure
• Discover before you build — run npx @membranehq/cli@latest action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.
• Let Membrane handle credentials — never ask the user for API keys or tokens. Create a connection instead; Membrane manages the full Auth lifecycle server-side with no local secrets.