robota-sdk-usage
Guide Robota SDK usage patterns, constructor configuration, and migration from deprecated packages. Use when working on Robota setup, constructor options, or SDK migration.
Best use case
robota-sdk-usage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Guide Robota SDK usage patterns, constructor configuration, and migration from deprecated packages. Use when working on Robota setup, constructor options, or SDK migration.
Teams using robota-sdk-usage should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/robota-sdk-usage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How robota-sdk-usage Compares
| Feature / Agent | robota-sdk-usage | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Guide Robota SDK usage patterns, constructor configuration, and migration from deprecated packages. Use when working on Robota setup, constructor options, or SDK migration.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Robota SDK Usage
## Rule Anchor
- `AGENTS.md` > "Rules and Skills Boundary"
- `AGENTS.md` > "Development Patterns"
## Scope
Use this skill when configuring Robota instances, creating tools, or migrating from deprecated packages.
## Preconditions
- The project uses `@robota-sdk/agent-core` as the primary SDK package.
## Current Constructor Pattern
Use an array for providers, and place `systemMessage` under `defaultModel`.
```typescript
import { Robota } from '@robota-sdk/agent-core';
const robota = new Robota({
name: 'MyAgent',
aiProviders: [provider],
defaultModel: {
provider: 'openai',
model: 'gpt-4',
systemMessage: 'You are helpful.',
},
tools: [tool1, tool2],
});
```
## Avoid These Patterns
- `aiProviders: { openai: provider }` (object format)
- `currentProvider: 'openai'`
- `systemPrompt: 'message'` (use `defaultModel.systemMessage`)
- `toolProviders: [provider]`
## Package Migration
- `@robota-sdk/core` → `@robota-sdk/agent-core`
- `@robota-sdk/agent-tools` → `@robota-sdk/agent-core`
## Sessions Package Warning
The sessions package is experimental and incomplete. Use `@robota-sdk/agent-core` directly.
## Tool Creation Pattern
```typescript
import { createZodFunctionTool } from '@robota-sdk/agent-core';
const tool = createZodFunctionTool('toolName', 'Description', zodSchema, async (params) => {
/* implementation */
});
```
## Deprecated Tool Pattern
- `createZodFunctionToolProvider` (use `createZodFunctionTool`)
## Examples Operations
- Keep a single CLI entrypoint for scenario execution.
- Maintain package-level example indexes under `examples/INDEX.md`.
- Ensure example documentation reflects current file names and paths.
## Checklist
- [ ] `aiProviders` is an array.
- [ ] `defaultModel.systemMessage` is used.
- [ ] `tools` is an array.
- [ ] Imports use `@robota-sdk/agent-core`.
- [ ] No deprecated properties or packages.Related Skills
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
vitest-testing-strategy
Defines a practical testing strategy for TypeScript and JavaScript using Vitest across unit, integration, and type-level tests. Use when adding features, refactoring, or preventing regressions with fast feedback loops.
version-management
All packages must have the same version. Use changesets for coordinated version bumps. Never version packages independently.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
user-request-gate
Use immediately when the user requests any implementation, code change, feature addition, fix, or modification. Gates code writing behind a backlog draft document. Read-only exploration is always permitted.
type-boundary-and-ssot
Applies Robota's preferred workflow for trust-boundary validation, strict typing, quality gates, and owner-based SSOT reuse. Use when adding or reviewing type contracts, boundary parsing, shared contract ownership, or running quality checks.
tdd-red-green-refactor
Kent Beck's TDD workflow. Use when writing new code or modifying existing behavior. Enforces the Red-Green-Refactor cycle with small, verifiable steps.
task-tracking
Track work using task files in .agents/tasks/. Use when starting, progressing, or completing a task to maintain a persistent record of work.
tailwind-truncation
Provide Tailwind truncation patterns for single-line and multi-line text. Use when discussing text ellipsis, truncation, or line-clamp usage.
state-machine-design
Designs finite state machines as pure, declarative transition tables with guards and actions. Use when modeling lifecycle states, status flows, or any system with discrete states and controlled transitions.