catalyst-datastore
Catalyst Data Store — relational cloud database with ZCQL, CRUD operations, table permissions, and result pagination. Requires MCP connection — check for CatalystbyZoho 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.
- Installs
- 1K
- Last 24h
- +12
- Trending rank
- #7799
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/catalystbyzoho/agent-skills --skill catalyst-datastore- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads catalyst-datastore automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
PREREQUISITES — READ THIS FIRST
Before ANY Data Store operation, you MUST verify MCP connectivity.
- Search for
CatalystbyZoho_*tools in your available tool list. - If NOT found: STOP. Do NOT write any code, scaffold files, or instruct Console steps. Load
catalyst-zoho-mcpskill and guide the user through MCP setup. Do NOT proceed until the user confirmsCatalystbyZoho_*tools are visible. - If found: Run
CatalystbyZoho_List_All_Organizations→CatalystbyZoho_List_All_Projectsto set project context, then continue to "How It Works".
Execution Checklist (MUST follow in order)
- Step 0: Confirm
CatalystbyZoho_*tools visible → if none found → STOP, set up MCP first - Step 1: Run
CatalystbyZoho_List_All_Organizations - Step 2: Run
CatalystbyZoho_List_All_Projects - Step 3: For table creation →
CatalystbyZoho_Create_Table| For existing tables →CatalystbyZoho_List_All_Tables - Step 4: Proceed with the operation
How It Works
- Create or locate the table via MCP — Creating a table? Use
CatalystbyZoho_Create_Tabledirectly. Do NOT instruct the user to open the Catalyst Console or create the table manually. Reading/writing data? UseCatalystbyZoho_List_All_Tablesto get table IDs. Never ask the user to copy table IDs. - Load
references/datastore-basics.md— for CRUD operations, ZCQL syntax, result unwrapping, and permissions setup. - Unwrap ZCQL results — Always remind:
rows.map(r => r.TableName). Raw ZCQL results are wrapped; accessing without unwrapping is the #1 Data Store bug. - Permissions — App User permissions are OFF by default. If the query involves a logged-in user reading data, check Console → Table → Scopes & Permissions.
- Pagination — ZCQL max 300 rows per query. Use
LIMIT offset, countfor larger datasets.
Hallucination Guards
Never assert project-specific values from an empty or unread directory. If the working directory has no project files, do not invent or assume timezone, table names, project ID, environment names, or any other project-specific detail. Ask the developer to supply them.
- Timezone: do not state a timezone for ZCQL date queries unless you have read it from a real project config file. Ask the developer what timezone their project uses.
- Table names / column names: only use names returned by
CatalystbyZoho_List_All_Tablesor explicitly provided by the user.
Default to native Node.js response syntax. When writing function code alongside Data Store operations, use res.writeHead() + res.end() — not Express methods (res.status(), res.json()), unless the user explicitly chose the Express template.
Security Checklist
- App User write permissions are off by default. The App User role has SELECT enabled by default, but INSERT, UPDATE, and DELETE must be manually enabled per table. Go to Console → Table → Scopes and Permissions → App User role → check Insert/Update/Delete for any table your authenticated users need to write.
- App Administrator has all permissions by default. Never assign the App Administrator role to regular end-users — it grants full read/write/delete access to all tables.
Triggers
Use this skill for: "Data Store", "ZCQL", "catalyst table", "create table", "query data", executeZCQLQuery, "table permissions", "App User permissions", "ROWID", "CREATEDTIME", "Data Store CRUD", "JOIN in ZCQL", "pagination ZCQL", "data store column types", "insert row", "update row", "delete row", or "relational data on Catalyst".
References
| Reference | Load when the query is about… |
|---|---|
references/datastore-basics.md | CRUD, ZCQL queries, result unwrapping, pagination, column types, App User permissions setup, CREATEDTIME timezone gotcha, emoji limitation |
FAQ
What does the catalyst-datastore skill do?
Catalyst Data Store — relational cloud database with ZCQL, CRUD operations, table permissions, and result pagination. Requires MCP connection — check for CatalystbyZoho 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.
How do I install catalyst-datastore?
Run npx skills add https://github.com/catalystbyzoho/agent-skills --skill catalyst-datastore in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/catalyst-datastore/ (personal) or .claude/skills/catalyst-datastore/ (project).
Which AI agents can use catalyst-datastore?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is catalyst-datastore safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains catalyst-datastore?
It is published by catalystbyzoho in catalystbyzoho/agent-skills. It has 1,027 recorded installs.
More from catalystbyzoho/agent-skills
catalyst-by-zoho
catalystbyzoho/agent-skills
Expert coding assistant for Catalyst by Zoho — Zoho's full-stack serverless cloud platform. Use for any question about Catalyst services, CLI, SDKs, architecture, pricing, or Zoho MCP tool-based infrastructure management.
catalyst-basics
catalystbyzoho/agent-skills
Core Catalyst project setup — directory structure, environments, CLI commands, and all Catalyst IDs (Project ID, ZAID, Table ID, Segment ID, Org ID). Trigger on 'start a Catalyst project', 'what is .catalystrc', 'where do I find my Table ID', 'difference between Development and Production', or any Catalyst ID or CLI question.
catalyst-functions
catalystbyzoho/agent-skills
Catalyst serverless functions — all 7 types (Basic I/O, Advanced I/O, Event, Cron, Job, Integration, Browser Logic), handler signatures, catalyst-config.json, Security Rules, API Gateway routing, file uploads, busboy, Express middleware, environment variables, function URL, and function testing. Requires MCP connection — check for CatalystbyZoho tools before any operation. Trigger on 'write a function', 'catalyst function', 'API Gateway', 'Security Rules', 'function not found', 'function returns 401', 'busboy', 'middleware', 'function URL', 'environment variable in function', 'duplicate CORS headers', 'CORS error in browser', 'Access-Control-Allow-Origin multiple values', 'function URL 404', 'execute suffix', 'function timeout', 'function hangs', or any function type question. Do NOT use for persistent servers, long-running processes, or Docker deployments — use catalyst-appsail instead.
catalyst-appsail
catalystbyzoho/agent-skills
Catalyst AppSail — persistent backend PaaS with managed runtimes (Node.js, Java, Python) and custom Docker containers. Trigger on 'AppSail', 'persistent server', 'Docker on Catalyst', 'XZOHOCATALYSTLISTENPORT', or 'long-running process on Catalyst'. Do NOT use for stateless request/response handlers, event-driven functions, or scheduled jobs — use catalyst-functions instead.
catalyst-sdk
catalystbyzoho/agent-skills
Catalyst SDKs — initialization patterns, service access, and method reference for Node.js, Web (browser), Python, Java, Android, iOS, and Flutter. Trigger on 'SDK', 'zcatalyst-sdk-node', 'Node.js SDK', 'Web SDK', 'Python SDK', 'Java SDK', 'Android SDK', 'iOS SDK', 'Flutter SDK', or 'initialize SDK'.
catalyst-zoho-mcp
catalystbyzoho/agent-skills
Catalyst Zoho MCP — manage Catalyst infrastructure (tables, buckets, cache) via CatalystbyZoho MCP tools using natural language. Trigger on 'Zoho MCP', 'MCP tools', 'catalyst MCP', 'CatalystbyZoho', 'create table with AI', 'MCP setup', 'MCP config', 'global MCP server', 'infrastructure as conversation', 'MCP first', 'avoid Catalyst console', or 'use MCP instead of console'.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available