Index of every page on this site: llms.txt
All skills
catalystbyzoho avatar

/catalyst-slate

@4b6047f
Run it yourself

Catalyst Slate — Git-based frontend hosting for React, Next.js, Vue, Angular, Svelte, Astro, SolidJS, Preact and other frameworks with preview deploys. Trigger on 'Slate', 'frontend hosting', 'slate-config.toml', 'deploy React app', or 'cross-domain Slate to function'. Do NOT use for backend APIs or server-side logic — use catalyst-appsail or catalyst-functions instead.

Use this Skill: https://skilld.dev/gh/catalystbyzoho/agent-skills/catalyst-slate

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈98 tokens for metadata: the name and description. ≈898 when used: this file. ≈3.3k more on demand in 1 file.

Description uses 4.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈389 characters, or 4.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

⚠️ PRE-FLIGHT CHECK — Slate activation (one-time, per project): Before any Slate command, confirm Slate is activated in the console. Open the Catalyst console → your project → Slate (left sidebar) → click Start Exploring. This is a one-time step. Skipping it means catalyst deploy slate fails with HTTP 400 even though slate:create succeeds locally.

How It Works

  1. Check if Slate is activated — Use MCP: call CatalystbyZoho_List_All_Slate_Apps with the project ID.
    • If it returns apps or an empty list → Slate is activated. Proceed.
    • If it returns INVALID_URL_PATTERN → Slate is not yet activated. This is NOT an MCP bug — it means the service needs a one-time console activation. Tell the user:

      "Please open the Catalyst console, go to your project → Slate (left sidebar) → click Start Exploring. This is a one-time step that takes 5 seconds. Let me know when done and I'll continue." Wait for confirmation, then proceed.

    • Never fall back to Web Client (legacy) because Slate isn't activated yet. Web Client is deprecated — Slate is always the right choice for frontend hosting. The one-time activation is not a reason to change the approach.

    If Slate was not selected during catalyst init, run catalyst slate:create --name <name> --framework <framework> --default immediately after init. This command updates catalyst.json and prompts for the source directory automatically — it is faster than manual setup and should be the default recommendation.

  2. Check if Slate app exists — If no app exists yet, run catalyst slate:create --name <name> --framework <framework> -ni to scaffold one. If Slate was not selected during catalyst init, run this immediately after init.
  3. Load references/slate-basics.md — for framework setup, slate-config.toml format, and baseUrl configuration.
  4. Cross-domain calls — If the query involves calling functions from a Slate app, apply the full URL + generateAuthToken() + CORS whitelist pattern.

    ⚠️ Migrating from basic client hosting? Relative paths like /server/fn/execute that worked in basic client silently break on Slate — Slate is served from *.onslate.com while functions are on *.catalystserverless.com. Every function call must become an absolute URL. Find and replace all relative /server/... paths with the full https://<project>.catalystserverless.com/server/... URL and add generateAuthToken() headers.

  5. Deploy — Before deploying, confirm Slate is activated in the console (Console → Slate). slate:create runs locally and succeeds without activation — the first backend call happens at deploy time, which fails with HTTP 400: Please access the Slate service in your project's console before deploying if not activated. Once confirmed: catalyst deploy slate <name> -ni deploys to the current environment. Preview URLs are available after the build completes.

Triggers

Use this skill for: "Slate", "frontend hosting", catalyst slate, slate-config.toml, "deploy React app", "Slate framework", slate:create, slate deploy, "frontend on Catalyst", "Slate vs Vercel", "cross-domain Slate to function", "Slate baseUrl", "Next.js on Catalyst", or "static frontend on Catalyst".

References

Reference Load when the query is about…
references/slate-basics.md Framework setup, slate-config.toml gotchas, baseUrl config, CORS for Slate→function calls, Git deploy, CLI commands

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    The skill provides standard documentation and instructions for deploying frontend applications using Catalyst Slate. It includes guidance on CLI commands, framework configuration, and handling cross-domain authentication safely using official Catalyst domains.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at 4b6047f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 3 months ago
metadata
{
  "version": "2.0.1"
}

README badge

README badge for catalystbyzoho/agent-skills/catalyst-slate