tag-rules

Manage deterministic auto-tagging engines for contact and chat classification.

6|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/filipexyz/ravi --skill tag-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tag-rules
Source: https://github.com/filipexyz/ravi/tree/main/src/plugins/internal/ravi-system/skills/tag-rules
Command: npx skills add https://github.com/filipexyz/ravi --skill tag-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of manually managing contact and chat states by providing a deterministic, rule-based engine that automatically applies or removes tags based on conversation history and contact metadata.

Core Features & Use Cases

  • Deterministic Tagging: Automatically classify contacts and chats based on predefined JSON rules without relying on probabilistic AI inference.
  • Lifecycle Management: Orchestrate complex workflows, such as moving a lead from a new state to a qualified state when specific purchase intent is detected in messages.
  • Audit and Traceability: Maintain a clear history of tag changes with built-in event emission for NATS integration and timeline tracking.

Quick Start

Use the tag-rules skill to evaluate and apply the qualify-buy-intent rule to the contact with the specified ID.

Frequently Asked Questions about tag-rules

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

FAQPage Schema
How do I automate contact classification based on chat messages without using AI?

You can automate contact classification using deterministic auto-tagging engines that evaluate predefined JSON rules against message content and contact attributes to trigger reactive or periodic tag transitions.

What is deterministic auto-tagging for CRM workflow orchestration?

Deterministic auto-tagging is a rule-based method that automatically applies or removes tags on contacts and chats based on canonical state data, bypassing probabilistic inference for precise lifecycle management.

How do I move a lead to a qualified state when purchase intent is detected?

You can orchestrate this lifecycle transition by configuring a JSON rule schema that detects specific purchase intent in chat messages and automatically applies the qualified state tag to the contact.

Does this auto-tagging engine require NATS for event propagation?

Yes, integrating with NATS is required for event propagation, which ensures built-in audit traceability by emitting tag change events for timeline tracking across the runtime environment.

Can I use this rule engine for periodic tag transitions on canonical state data?

Yes, the engine operates on canonical state data to trigger both reactive tag transitions based on message content and periodic tag transitions based on predefined contact attribute rules.

What are the limitations of using deterministic rules for chat classification?

Deterministic rules require strict adherence to defined JSON schemas and cannot interpret nuanced intent like probabilistic AI, meaning tag transitions will only occur when exact rule conditions are met.