ClaudeSuperPower
SubmitLog in

catalyst-datastore

Skill

Catalyst Data Store — relational cloud database with ZCQL, CRUD operations, table permissions, and result pagination. Requires MCP connection — check for the ZohoMCP_* meta-tools before any operation. Trigger on 'Data Store', 'ZCQL', 'create table', 'executeZCQLQuery', 'table permissions', 'ROWID',

0Databases

Install

git clone https://github.com/catalystbyzoho/claude-plugin.git ~/.claude/skills/catalyst-datastore

What is catalyst-datastore?

Catalyst Data Store — relational cloud database with ZCQL, CRUD operations, table permissions, and result pagination. Requires MCP connection — check for the ZohoMCP_* meta-tools before any operation. Trigger on 'Data Store', 'ZCQL', 'create table', 'executeZCQLQuery', 'table permissions', 'ROWID', 'boolean column', 'boolean always true', 'truthy string', 'boolean stored as string', or 'DataStore data types'. You MUST load this skill whenever writing code that reads or writes Data Store data — ZCQL result wrapping, boolean-as-string behavior, and App User permissions are non-obvious and cause silent bugs if skipped.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~156 tokens of context used while enabled, before you invoke anything

Documentation

README · ~2 min read

⚠️ PREREQUISITES — READ THIS FIRST

MCP gate (before ANY Data Store operation): Confirm the ZohoMCP_* meta-tools (ZohoMCP_getSchema, ZohoMCP_executeTool, ZohoMCP_listTools, ZohoMCP_getFeatures) are present in your tool list — that is the "MCP connected" signal. (The CatalystbyZoho_* names never appear as tools; they are tool_name values passed to ZohoMCP_executeTool.) If the meta-tools are NOT present → STOP: do not write code, scaffold files, or instruct Console steps — load the catalyst-zoho-mcp skill, guide the user through MCP setup, and resume only once they appear.

Once the tools are visible, complete the canonical pre-flight once per session (establish + verify org/project) → ../catalyst-basics/references/preflight.md, then continue to "How It Works". Verify table access with CatalystbyZoho_List_All_Tables before create/update operations.

How It Works

  1. Create or locate the table via MCP — Creating a table? Invoke CatalystbyZoho_Create_Table via ZohoMCP_executeTool (schema first with ZohoMCP_getSchema). Do NOT instruct the user to open the Catalyst Console or create the table manually. Reading/writing data? Invoke CatalystbyZoho_List_All_Tables (same way) to get table IDs. Never ask the user to copy table IDs.
  2. Load references/datastore-basics.md — for CRUD operations, ZCQL syntax, result unwrapping, and permissions setup.
  3. Unwrap ZCQL results — Always remind: rows.map(r => r.TableName). Raw ZCQL results are wrapped; accessing without unwrapping is the #1 Data Store bug.
  4. Permissions — App User permissions are OFF by default. If the query involves a logged-in user reading data, check Console → Table → Scopes and Permissions.
  5. Pagination — ZCQL max 300 rows per query. Use LIMIT offset, count for larger datasets.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills →

create-atomic-tool

Build a `BaseTool[InSchema, OutSchema]` subclass — input/output schemas, `BaseToolConfig`, `run()` (and optional `run_async()`), env-driven secrets, typed failure outputs. Use when the user asks to "add a tool", "create a tool", "wrap an API as a tool", "build a `BaseTool`", "make a calculator/searc

6.1K stars

create-atomic-context-provider

Build a `BaseDynamicContextProvider` that injects a named, titled block into an agent's system prompt at every `run()` — current time, user identity, retrieved RAG docs, session state, cached DB schema. Use when the user asks to "add a context provider", "inject X into the prompt", "give the agent d

6.1K stars

framework

Guide for the Atomic Agents Python framework — schemas, agents, tools, context providers, prompts, orchestration, and provider configuration. Use when code imports from `atomic_agents`, defines an `AtomicAgent`, `BaseTool`, or `BaseIOSchema`, or the user asks about multi-agent orchestration or LLM-p

6.1K stars

Plugins

All plugins →

receipts

A personal Claude Code impact report for justifying your usage to a manager or a self-review: what you shipped, which projects it went to, and each project's share of your usage. Reads your ~/.claude/projects transcripts and runs read-only git locally; only counts and project names are sent to write

32.8K stars

atomic-agents

Comprehensive development workflow for building AI agents with the Atomic Agents framework. Includes specialized agents for schema design, architecture planning, code review, and tool development. Features guided workflows, progressive-disclosure skills, and best practice validation.

6.1K stars

databases-on-aws

Expert database guidance for the AWS database portfolio. Design schemas, execute queries, handle migrations, and choose the right database for your workload.

844 stars