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".
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryGeneralStars0
About this skill
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".
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Rossum business-rules & validation reference — the two ways to validate extracted data and block automation: native Rossum Rules (the /v1/rules entity — trigger_condition + actions[], FIRE-vs-PASS polarity, lifecycle; the trigger_condition 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 — has_value({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".
About this listing
Category
General
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI