Use the local Contextual CLI from shell-capable agents to inspect tenants, analyze flows, and apply safe edits. Use only in runtimes with local shell access.
EnglishDesign and validate Contextual.io Object Type schemas. Use when creating new object types, adding properties, defining relations, or reviewing schema correctness. Do NOT use for flow changes — use solai-flow-editor for those.
EnglishEdit live Contextual flows in the Flow Editor — add, change, move, wire, delete, rename, configure, group, copy, or validate nodes / wires / properties / code in a flow open in the user's browser. Also the source-of-truth for node-level behavior, configuration, and authoring patterns — function-node logging (await logger.), loop wiring, Native Object node TypedInput patterns, http-response status precedence, etc. (see node-reference.md). Required before any mcpctxl-flow-editor call other than info/listsessions orientation. Use AFTER planning; do NOT plan architecture here — use plan-flow first.
EnglishGround Solution AI and Contextual product answers in the official platform documentation — for platform/runtime behavior not already covered by plugin-side reference content (cli-reference.md, node-reference.md, the relevant SKILL.md). For CLI command shapes, JSONL formats, flow record structure, native-object-config shape, or node-level authoring patterns, prefer the plugin-side references first; this skill is the second stop, for behavior the plugin-side does not cover.
English
AGENT SKILLS ATLASIncludes Solai Data Modeler, Solai Flow Editor, Solai Knowledge, and other workflows.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Solai CLI
Use the local Contextual CLI from shell-capable agents to inspect tenants, analyze flows, and apply safe edits. Use only in runtimes with local shell access.
Solai Data Modeler
Design and validate Contextual.io Object Type schemas. Use when creating new object types, adding properties, defining relations, or reviewing schema correctness. Do NOT use for flow changes — use solai-flow-editor for those.
Solai Flow Editor
Edit live Contextual flows in the Flow Editor — add, change, move, wire, delete, rename, configure, group, copy, or validate nodes / wires / properties / code in a flow open in the user's browser. Also the source-of-truth for node-level behavior, configuration, and authoring patterns — function-node logging (await logger.), loop wiring, Native Object node TypedInput patterns, http-response status precedence, etc. (see node-reference.md). Required before any mcpctxl-flow-editor call other than info/listsessions orientation. Use AFTER planning; do NOT plan architecture here — use plan-flow first.
Solai Knowledge
Ground Solution AI and Contextual product answers in the official platform documentation — for platform/runtime behavior not already covered by plugin-side reference content (cli-reference.md, node-reference.md, the relevant SKILL.md). For CLI command shapes, JSONL formats, flow record structure, native-object-config shape, or node-level authoring patterns, prefer the plugin-side references first; this skill is the second stop, for behavior the plugin-side does not cover.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Solai CLI skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.