Skip to main content
skill CX Codex

catalyst-authentication — Claude Code skill: how to install

Guides user login, social auth, and OAuth connections in Zoho Catalyst. Prevents broken production deployments caused by mismatched ZAID identifiers.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add catalystbyzoho/agent-skills --skill catalyst-authentication -a claude-code
Open on GitHub

What catalyst-authentication does

This skill guides agent workflows for Zoho Catalyst authentication, covering hosted and embedded login, JWT handling, and third-party identity providers like Okta or Auth0. It handles Web SDK calls such as getCurrentUser, signinWithJwt, and token management via Connections.

Local auth fails when running standard dev servers like Vite or Next.js. Auth cookies and /__catalyst/sdk/init.js are injected solely through catalyst serve.

Another trap is ZAID mismatch. Development and production environments use different ZAID values. Because social logins rely on this identifier, promoting your code without updating the production ZAID breaks logins silently.

What it helps with

  • configure Google, Microsoft, or Okta login in Zoho Catalyst
  • fix silent authentication failures caused by production ZAID changes
  • retrieve external OAuth tokens using Connections and getAccessToken
  • separate function execution permissions from DataStore table scopes

Example prompts for the agent

  • Configure Google social login for my Catalyst application
  • Debug why authentication fails after moving from dev to production
  • Generate a custom JWT token for user signin in Catalyst

How to install catalyst-authentication

1Skills CLI (Vercel)

npx skills add catalystbyzoho/agent-skills --skill catalyst-authentication -a claude-code

2Manually: put the files in place

~/.claude/skills/catalyst-authentication/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/catalyst-authentication/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about catalyst-authentication

How to install catalyst-authentication in Claude Code?

Run npx skills add catalystbyzoho/agent-skills --skill catalyst-authentication -a claude-code. The skill file is placed in ~/.claude/skills/catalyst-authentication/SKILL.md.

What does catalyst-authentication do?

It teaches coding agents how to set up Catalyst user signup, hosted or embedded auth screens, and OAuth integrations without common pitfalls.

Why does local authentication require catalyst serve?

Native servers like Vite or Next dev lack the Catalyst middleware. Only catalyst serve injects required session cookies and /__catalyst/sdk/init.js.

Source text

SKILL.md · Apache-2.0
---
name: catalyst-authentication
description: "Catalyst Authentication — user login/signup, ZAID, Web SDK auth flows, OAuth token management via Connections, third-party authentication (Okta, Auth0, Duo, custom IdP), social logins (Google, Facebook, LinkedIn, Microsoft), generateCustomToken, signinWithJwt. Trigger on 'authentication', 'login', 'signup', 'getCurrentUser', 'ZAID', 'isUserAuthenticated', 'signOut', 'Connections', 'getAccessToken', 'third-party auth', 'social login', 'Google login', 'signinWithJwt', or 'generateCustomToken'. You MUST load this skill whenever implementing user login or protecting data — ZAID differs between Development and Production and is the #1 cause of auth failures after environment promotion. For Security Rules (function invocation control), route to catalyst-functions."
metadata:
  version: "2.1.2"
---

## Local auth requires plain `catalyst serve`

Auth works locally only when served through `catalyst serve`. NEVER use the native dev server (`npm run dev`, `vite`, `next dev`, `ng serve`, etc.) for auth development — the Catalyst auth middleware, cookie injection, and `/__catalyst/sdk/init.js` are only available through `catalyst serve`.

## How It Works

1. **Identify flow type** — Hosted login (redirect to Catalyst login page), embedded login (custom UI), or backend `getCurrentUser` check.
2. **Load `references/auth-basics.md`** — for signup/login flows, ZAID gotcha, hosted vs embedded login, and common auth errors.
3. **ZAID warning** — ZAID differs between Development and Production. This is the #1 auth issue in production. Always verify the environment.
4. **Security Rules** — If the query involves controlling who can invoke a function, route to `catalyst-functions` skill and its `references/functions-basics.md` Security Rules section. Security Rules has two parameters: (a) **`methods`** — which HTTP methods (GET/POST/PUT/DELETE/PATCH) are enabled for the function (removing a method blocks that verb entirely), and (b) **`authentication`** — a single binary flag (`optional` = public, `required` = authenticated users only) applied **function-wide, not per-method**. For role-based data access control, route to DataStore Scopes and Permissions (Console → Table → Scopes and Permissions).
5. **OAuth / Connections** — Load `references/connections.md` for external API OAuth token management (Zoho or third-party).
6. **Third-party auth / social logins** — If the query involves Okta, Auth0, Duo, custom IdP, Google/Facebook/LinkedIn/Microsoft login, `generateCustomToken`, or `signinWithJwt`, load `references/auth-thirdparty.md`.

## Security Checklist

- **ZAID is environment-specific.** The Development ZAID is different from the Production ZAID. Social logins (Google, Facebook, LinkedIn, Microsoft) configured in Development MUST be reconfigured with the Production ZAID and production app domain before going live — using the wrong ZAID causes all social logins to silently fail in production.
- **DataStore permissions are separate from function-level auth.** Requiring authentication in Security Rules only controls who can call the function. App User table permissions (Console → Table → Scopes and Permissions) separately control which DataStore operations authenticated users can perform.

## Triggers

Use this skill for: "authentication", "user management", "login", "signup", `getCurrentUser`, "ZAID", `registerUser`, `isUserAuthenticated`, `signOut`, "cross-domain logout", "hosted login", "embedded login", "Connections", "OAuth token", `getConnector`, `getAccessToken`, "Security Rules", "App User", "credentials include", "auth redirect", "third-party auth", "third-party authentication", "social login", "Google login", "Facebook login", "LinkedIn login", "Microsoft login", `signinWithJwt`, `generateCustomToken`, "Okta", "Auth0", "Duo", "custom IdP".

## References

| Reference | Load when the query is about… |
|-----------|-------------------------------|
| `references/auth-basics.md` | User signup/login, getCurrentUser, Web SDK auth flows, ZAID gotcha, hosted vs embedded login, common auth errors |
| `references/auth-thirdparty.md` | Third-party auth services (Okta, Auth0, Duo), social logins (Google/Facebook/LinkedIn/Microsoft), `generateCustomToken`, `signinWithJwt`, token flow, console setup |
| `catalyst-functions` skill | Security Rules — function invocation control (`methods`, `authentication: optional/required`) |
| `references/connections.md` | OAuth token management for external APIs — getConnector, getAccessToken, Zoho and third-party service connections |

© catalystbyzoho · Apache-2.0 · catalystbyzoho/agent-skills

Similar skills

All skills for Security →

From the same set15

catalyst-sdk A skill that tells the agent how to initialize the Catalyst SDK and reach its services on Node.js, Python, Java, web and mobile. CX Codex +1 1,000installs catalyst-functions Guides development and deployment for all 7 Zoho Catalyst serverless function types. Helps configure API Gateway routing, resolve CORS bugs, and handle file uploads. CX Codex +1 1,000installs catalyst-appsail Guides the agent through deploying a persistent server on Catalyst AppSail, whether a managed Node.js, Java or Python runtime or your own Docker container. CX Codex +1 1,000installs catalyst-by-zoho Guides Claude Code through building full-stack serverless apps on Catalyst by Zoho. Helps wire Functions, Slate, and storage via Zoho MCP tools and the CLI. CX Codex +1 1,000installs catalyst-zoho-mcp This skill wires an AI agent to the Zoho Catalyst MCP server so tables, buckets and cache get created from plain chat instead of the console. CX Codex +1 1,000installs catalyst-slate Walks your agent through deploying a frontend to Catalyst Slate: scaffold the app, configure slate-config.toml, ship the build. Handy when React or Next.js needs to live on Catalyst. CX Codex +1 1,000installs catalyst-cache A skill that teaches the agent to use Catalyst Cache: store temporary values in segments, read them back, and respect the TTL. Handy for session data. CX Codex +1 997installs catalyst-stratus A skill for Catalyst Stratus object storage: file uploads, signed URLs, multipart upload. Useful when your project keeps files in Stratus. CX Codex +1 994installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor