robocorp-cursor-rules — Claude Code skill: RoboCorp RPA rules
Agent rules for writing RoboCorp RPA automation in Python: plain functions, Pydantic validation, async I/O.
npx skills add Mindrally/skills --skill robocorp-cursor-rules -a claude-codeWhat robocorp-cursor-rules does
The skill tells the agent how to shape RoboCorp code: pure functions instead of classes, declarative task definitions, type hints on every signature. Input and output validation goes through Pydantic models rather than raw dictionaries, and I/O-bound work uses async def.
Error handling sits at the top of each function. Early returns, guard clauses for preconditions, happy path last. Expected failures are caught with specific exceptions such as RPA.HTTP.HTTPException instead of a bare except. For static or frequently read data the rules suggest Redis or an in-memory store.
A single markdown file holds the sections: key principles, Python and RoboCorp standards, error handling, performance, conventions. The conventions lean on RoboCorp's dependency injection and on execution metrics. Nothing runs on its own — the file only steers the agent while it writes tasks.
What it helps with
- define a RoboCorp task declaratively with a clear return type
- swap raw dicts for Pydantic models on input validation
- flatten nested logic with early returns
- move blocking database calls to async
- keep file and variable naming consistent across a project
Example prompts for the agent
- write a RoboCorp task that processes a queue of requests, validate input with Pydantic
- convert this block to async def, the database call stalls the run
- add guard clauses and error logging at the top of the function
How to install robocorp-cursor-rules
1Skills CLI (Vercel)
npx skills add Mindrally/skills --skill robocorp-cursor-rules -a claude-code2Manually: put the files in place
~/.claude/skills/robocorp-cursor-rules/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/robocorp-cursor-rules/
1Skills CLI (Vercel)
npx skills add Mindrally/skills --skill robocorp-cursor-rules -a codex2Manually: put the files in place
.agents/skills/robocorp-cursor-rules/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Mindrally/skills --skill robocorp-cursor-rules -a cursor2Manually: put the files in place
.cursor/skills/robocorp-cursor-rules/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Mindrally/skills robocorp-cursor-rules2Manually: put the files in place
.github/skills/robocorp-cursor-rules/SKILL.md1Skills CLI (Vercel)
npx skills add Mindrally/skills --skill robocorp-cursor-rules -a gemini-cli2Platform CLI
gemini skills install https://github.com/Mindrally/skills --path robocorp-cursor-rulesManually: put the files in place
.devin/skills/robocorp-cursor-rules/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Mindrally/skills --skill robocorp-cursor-rules -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about robocorp-cursor-rules
How do I install robocorp-cursor-rules in Claude?
Run npx skills add Mindrally/skills --skill robocorp-cursor-rules -a claude-code. The skill lands in ~/.claude/skills/robocorp-cursor-rules/SKILL.md.
What does robocorp-cursor-rules do?
It gives the agent rules for RoboCorp RPA in Python: functional style, Pydantic validation, async operations for I/O.
Do I need RoboCorp itself for this skill?
The skill is plain text guidance and runs nothing. Its examples assume a RoboCorp project, so outside one it adds little.
Source text
SKILL.md · Apache-2.0
--- name: robocorp-cursor-rules description: Guidelines for building RoboCorp RPA automation with Python, emphasizing functional programming, Pydantic validation, and async operations. metadata: maintainer: Mindrally source: https://github.com/Mindrally/skills --- # RoboCorp Python Development You are an expert in Python and RoboCorp RPA development. ## Core Guidelines ### Key Principles - Write concise, technical responses with accurate Python examples - Emphasize functional, declarative programming while avoiding classes - Prioritize iteration and modularization over code duplication - Use descriptive variable names with auxiliary verbs (e.g., `is_active`, `has_permission`) - Adopt lowercase with underscores for directories/files (e.g., `tasks/data_processing.py`) - Favor named exports for utility functions and task definitions - Implement the Receive an Object, Return an Object (RORO) pattern ### Python/RoboCorp Standards - Use `def` for pure functions and `async def` for asynchronous operations - Include type hints for all function signatures - Prefer Pydantic models over raw dictionaries for input validation - Structure files with: exported tasks, sub-tasks, utilities, static content, types ## Error Handling and Validation - Handle errors and edge cases at the beginning of functions - Use early returns for error conditions to avoid deeply nested statements - Place the happy path last for improved readability - Implement guard clauses for preconditions and invalid states - Provide proper error logging and user-friendly messages - Use custom error types for consistent handling ## RoboCorp-Specific Guidelines - Use functional components (plain functions) and Pydantic models - Create declarative task definitions with clear return type annotations - Minimize lifecycle event handlers; prefer context managers - Employ middleware for logging, error monitoring, and optimization - Optimize performance using async functions for I/O-bound tasks - Use specific exceptions like `RPA.HTTP.HTTPException` for expected errors - Apply Pydantic's `BaseModel` for consistent input/output validation ## Performance Optimization - Minimize blocking I/O operations; use asynchronous operations for all database calls - Implement caching for static and frequently accessed data using Redis or in-memory stores - Optimize data serialization/deserialization with Pydantic - Use lazy loading techniques for large datasets ## Key Conventions 1. Rely on RoboCorp's dependency injection system 2. Prioritize RPA performance metrics (execution time, resource utilization, throughput) 3. Limit blocking operations; favor asynchronous flows 4. Structure tasks and dependencies clearly for maintainability
© Mindrally · Apache-2.0 · Mindrally/skills