Rossum business-rules & validation reference — the two ways to validate extracted data and block automation: native Rossum Rules (the /v1/rules entity — triggercondition + actions[], FIRE-vs-PASS polarity, lifecycle; the triggercondition is written in TxScript, so for that syntax see txscript-reference) and the legacy Business Rules Validation Store extension (checks[] config, error/warning/info result types, automation blocking, queue scoping, one-rule-one-table limit, plus its own curly-brace expression engine — hasvalue({field}), aggregations, casting, similarity/substring/regexp — documented in full in this pack because it is specific to this extension). Use whenever the user works on business rules, validation rules, data validation, native Rules vs. the business-rules extension, blocking automation on invalid data, rule actions, the checks[] config, or gating on field values — even when they just say "add a rule" or "validate this field".
EnglishGenerate a Statement of Work (SOW) for a Rossum.ai implementation project. Use when the user wants to create a SOW, project proposal, or scope document for a Rossum engagement. Triggers on requests like "write a SOW", "create a statement of work", "draft a Rossum proposal", "scope this project".
English
AGENT SKILLS ATLASIncludes Business Rules Reference 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
Business Rules Reference
Rossum business-rules & validation reference — the two ways to validate extracted data and block automation: native Rossum Rules (the /v1/rules entity — triggercondition + actions[], FIRE-vs-PASS polarity, lifecycle; the triggercondition is written in TxScript, so for that syntax see txscript-reference) and the legacy Business Rules Validation Store extension (checks[] config, error/warning/info result types, automation blocking, queue scoping, one-rule-one-table limit, plus its own curly-brace expression engine — hasvalue({field}), aggregations, casting, similarity/substring/regexp — documented in full in this pack because it is specific to this extension). Use whenever the user works on business rules, validation rules, data validation, native Rules vs. the business-rules extension, blocking automation on invalid data, rule actions, the checks[] config, or gating on field values — even when they just say "add a rule" or "validate this field".
Write Sow
Generate a Statement of Work (SOW) for a Rossum.ai implementation project. Use when the user wants to create a SOW, project proposal, or scope document for a Rossum engagement. Triggers on requests like "write a SOW", "create a statement of work", "draft a Rossum proposal", "scope this project".
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 Business Rules Reference 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.