cross-manager

Maps deprecated cross-session commands to the updated Ravi session management interface syntax.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a bridge for users transitioning from the deprecated cross-session command structure to the modern Ravi session management system.

Core Features & Use Cases

  • Command Mapping: Provides a clear reference for migrating legacy cross-session commands to the new session-based syntax.
  • Session Routing: Facilitates the transition of message relay, task execution, and information sharing to the current Ravi session architecture.
  • Use Case: If you are maintaining older scripts or workflows that rely on the deprecated cross-manager syntax, use this guide to update your commands to the current Ravi session standards.

Quick Start

Use the cross-manager skill to view the migration table and update your existing session commands to the new ravi sessions syntax.

Frequently Asked Questions about cross-manager

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

FAQPage Schema
How do I migrate deprecated cross-session commands to the new Ravi session management syntax?

Migrate deprecated cross-session commands by mapping legacy syntax patterns to the updated Ravi session-based CLI interface. This skill provides a reference table to translate old message relay and task execution workflows into the current session routing standards.

What is the best way to update legacy message relay scripts for Ravi runtime compatibility?

Update legacy message relay scripts by mapping deprecated command structures to the modern Ravi session management infrastructure. This ensures information exchange and task execution workflows remain compatible with the current runtime architecture.

Does the Ravi session management system support old cross-manager task execution workflows?

The Ravi session management system supports old cross-manager task execution workflows through a compatibility bridge. It maps deprecated command patterns to the updated session-based CLI interface, ensuring legacy scripts continue functioning during migration.

How does command mapping work for transitioning legacy session routing to Ravi?

Command mapping for transitioning legacy session routing works by translating deprecated cross-session communication commands into the current Ravi session-based syntax. It provides a clear reference for migrating message relay, task execution, and information sharing workflows.

When do I need to migrate legacy cross-session communication commands?

Migrate legacy cross-session communication commands when maintaining older scripts or workflows that rely on the deprecated cross-manager syntax. This transition is necessary to ensure compatibility with the updated Ravi session management infrastructure.

Can I use this migration guide to update cross-session task execution for the current Ravi CLI?

Use this migration guide to update cross-session task execution for the current Ravi CLI by viewing the migration table. It maps deprecated command patterns to the updated session-based interface, facilitating transition of task execution workflows.