callstackincubator/rozenite-agent-sdk
Use Rozenite for Agents through `@rozenite/agent-sdk` in Node.js or TypeScript code. Trigger this skill when Codex needs to write or run scripts, wrappers, automations, benchmarks, or agent runtimes that call Rozenite programmatically instead of driving the `rozenite agent` CLI directly.
npx skills add https://github.com/callstackincubator/rozenite --skill rozenite-agent-sdk
Use this skill when the user wants code-first access to Rozenite for Agents.
Read references/code-patterns.md for copy-pastable examples.
@rozenite/agent-sdk.createAgentClient() -> client.withSession(...) -> inspect or call tools -> exit.session.domains.list() as the source of truth for live built-in and runtime domains.session.tools.list({ domain }) and session.tools.getSchema({ domain, tool }) only when you need live inspection or argument confirmation../sdk export and call tools as session.tools.call(descriptor, args).session.tools.call({ domain, tool, args }) only when no matching ./sdk descriptor is available or the tool is discovered dynamically at runtime.session.tools.list({ domain }), treat the returned shortName as the canonical tool name to pass back into a later call-by-name invocation. Do not invent camelCase aliases or normalize tool names yourself.network, react, memory) and plugin IDs (@rozenite/storage-plugin, @rozenite/tanstack-query-plugin) over the derived, CLI-facing domain token like storage.page.nextCursor explicitly in the next call. The plugin owns its page envelope and cursor.session.domains.list() or session.tools.list(...) before calling the plugin tool.client.openSession() or client.attachSession(sessionId), see the reference patterns.rozenite-agent instead when the task is shell-driven, needs a reusable CLI session, operates directly through rozenite agent ..., or requires target enumeration before choosing a deviceId.Take callstackincubator/rozenite-agent-sdk from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.