drools_assistant

Generates and validates Drools DRL rules for the Rierino platform.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/rierino-open/rierino-claude-plugin --skill drools-assistant-rierino-open
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: drools_assistant
Source: https://github.com/rierino-open/rierino-claude-plugin/tree/main/development/skills/drools_assistant
Command: npx skills add https://github.com/rierino-open/rierino-claude-plugin --skill drools-assistant-rierino-open

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing correct Drools Rule Language (DRL) code requires deep knowledge of rule firing mechanics, working memory, and truth maintenance, and small mistakes like unguarded nullable fields cause runtime failures. This Skill produces syntactically valid, engine-ready DRL rules aligned with your existing workspace facts and naming conventions. ## Core Features & Use Cases - DRL Rule Generation: Creates atomic, single-purpose rules with proper when/then structure, agenda groups, and guarded constraints. - Workspace Alignment: Reuses existing fact classes, globals, and packages from your project, marking uncertain references with // TO VERIFY comments instead of inventing APIs. - Engine-Ready Output: Returns raw DRL text with no markdown fences or prose, immediately ingestible by the Drools engine. - Use Case: A developer needs a rule that flags high-value orders in the Rierino platform. The Skill outputs a complete DRL block with null-safe constraints, documented working memory changes, and the correct package and imports. ## Quick Start Ask the assistant to write a Drools rule that applies a discount when an order total exceeds a threshold, using the fact types already defined in your workspace.

Frequently Asked Questions about drools_assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Drools DRL rule with when/then logic?▼

Define a rule block with a descriptive name, place fact constraints in the when section, and actions in the then section. Guard all nullable field accesses in constraints and document any working memory changes like modify or insert with inline comments.

How to prevent NullPointerException in Drools rule constraints?▼

Add explicit null checks in the when block before comparing field values, such as field != null combined with the value condition. Unguarded nullable field access during rule evaluation is the most common cause of runtime NPEs in Drools.

When should I use agenda-group and no-loop in Drools rules?▼

Use agenda-group only when rules must fire in coordinated groups, and no-loop only when a rule's own actions could retrigger itself. Applying them speculatively causes unpredictable rule firing behavior and should be avoided.

Can Drools rules reuse existing fact types from my project?▼

Yes, rules should reference the fact classes, globals, and packages already defined in your workspace rather than inventing new types. Uncertain references should be marked with // TO VERIFY comments for later confirmation.

Why should each Drools rule handle only one business intent?▼

Combining multiple business intents into one rule makes debugging, testing, and truth maintenance difficult. Atomic single-purpose rules fire predictably and are easier to validate against changing business requirements.