Studio router

You are working on Contentstack Studio. The pack has one specialist skill per task, covering install, provisioning, component registration, section/template authoring, data binding, preview wiring, verification, troubleshooting, and migration.

This SKILL.md is the only file loaded up front. Everything else is routed through skills-index.md.

Resolving a skill file

The specialist guides sit next to this file, in the same folder: a skill named <name> is <name>.md beside this SKILL.md, and the lookup table is skills-index.md in the same folder. Every cross-reference in this file and in skills-index.md is written as <name> or <name>.md. Resolve all of them this way.

Fallback: if <name>.md isn't there, try ../<name>/SKILL.md (a host that installed each guide as its own skill folder).

If neither resolves, say so out loud: "the Studio skill pack looks mis-installed, <name> didn't resolve", and do NOT quietly fall back to general knowledge. A silent fallback looks identical to the pack working, so the user never learns their install is broken.

What to do

Setup intent takes precedence over keyword matching. “Enable Studio”, “make this project Studio ready”, “Studio setup”, and equivalent whole-app requests run convert-project-to-studio through verification. install-studio alone is for an explicit SDK-only request. Preserve the active setup objective across replies such as “yes”, “start”, and “OAuth done”; resume the pending step rather than routing that reply as a new task. Use the orchestrator's scoped completion checklist; authoring requirements below apply only when components or compositions are authored.

Discover MCP execution before resolving raw HTTP credentials. Follow install-contentstack-mcp to inspect callable tools in the current host and verify the target with a read call. A stored OAuth session is not evidence of a connected MCP server. Prefer available MCP operations; use OAuth HTTP for missing operations or an explicitly recorded connection limitation. Never infer tool availability solely from a conversation flag.