RoboCorp RPA Python guidelines: functional tasks, Pydantic validation, async-first automation
Receive-an-object-return-an-object tasks, Pydantic over raw dicts, async I/O for database calls, guard clauses, structured task files, and RPA performance metrics
- What
- Receive-an-object-return-an-object tasks, Pydantic over raw dicts, async I/O for database calls, guard clauses, structured task files, and RPA performance metrics
- Cost
- Free
- Needs
- a RoboCorp/Python RPA setup (or a plan to build one) — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @mindrally's RoboCorp development guidelines: a functional, declarative style for RPA robots — plain functions with `def`/`async def`, full type hints, Pydantic `BaseModel` validation over raw dictionaries, the Receive-an-Object-Return-an-Object (RORO) pattern, descriptive `is_`/`has_` boolean names, guard clauses with the happy path last, structured files (exported tasks → sub-tasks → utilities → types), middleware for logging and error monitoring, async everything I/O-bound, caching for static data, and specific exception handling (`RPA.HTTP.HTTPException`). Includes RPA-specific performance priorities (execution time, resource utilization, throughput) and conventions like RoboCorp's dependency injection. Honest caveats: guidance only — it assumes a RoboCorp/Python RPA setup and will not turn a general agent into an RPA expert without one; RoboCorp-specific bits (dependency injection, RPA libraries) only apply in that ecosystem. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a RoboCorp/Python RPA setup (or a plan to build one) — the skill is guidance the agent follows, not software to install Install "RoboCorp RPA Python guidelines: functional tasks, Pydantic validation, async-first automation" for me. It gives my agent @mindrally's RoboCorp playbook: functional declarative tasks with the RORO pattern, Pydantic validation over raw dicts, full type hints, async I/O, guard clauses with happy path last, structured task files, middleware-based logging and error monitoring, caching for static data, and RPA performance metrics (execution time, resource utilization, throughput). Apache-2.0 licensed. Repository: https://github.com/mindrally/skills/blob/main/robocorp-cursor-rules/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "robocorp-cursor-rules". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my RoboCorp project or the robot to build; RoboCorp-specific conventions only apply there — nothing else, it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.