skills.rest
filipexyz
filipexyzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

matrix-manager

Migrate legacy Matrix CLI commands to Ravi channel and session abstractions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides guidance on migrating away from deprecated Matrix-specific CLI commands to the current Ravi channel and session-based architecture.

Core Features & Use Cases

  • Migration Guidance: Clearly identifies retired Matrix-specific commands and surfaces.
  • Architectural Alignment: Directs users toward modern Ravi abstractions like channels, instances, and routes.
  • Use Case: If you are attempting to use legacy Matrix commands, this skill provides the necessary instructions to transition your workflow to the supported Ravi runtime infrastructure.

Quick Start

Use the matrix-manager skill to identify which legacy commands you need to replace with current Ravi channel and session abstractions.

Frequently Asked Questions about matrix-manager

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

FAQPage Schema
How do I migrate deprecated Matrix CLI commands to the Ravi runtime?▼

Migrating deprecated Matrix CLI commands to the Ravi runtime involves replacing legacy account, room, and messaging workflows with the unified Ravi channel and instance abstraction layer. This enforces modern session and platform identity models.

What are the retired Matrix-specific commands in the Ravi architecture?▼

Retired Matrix-specific commands are legacy CLI surfaces for account, room, and messaging workflows. They are replaced by modern Ravi abstractions like channels, instances, and routes to ensure architectural consistency.

How do I transition account workflows to the Ravi channel abstraction?▼

Transitioning account workflows to the Ravi channel abstraction requires mapping legacy Matrix-specific account commands to the current Ravi channel and session-based architecture, aligning workflows with modern platform identity models.

Why are legacy Matrix commands not working in my Ravi session?▼

Legacy Matrix commands are not working because they are deprecated and retired from the Ravi runtime. You must use the unified Ravi channel and instance abstraction layer for account, room, and messaging workflows.

Do I need to update my platform identity models when migrating from Matrix?▼

Yes, updating platform identity models is required when migrating from Matrix. The Ravi runtime enforces architectural consistency by requiring modern session and platform identity models instead of legacy Matrix-specific surfaces.

Related Skills

Explore More Software Engineering Skills→
filipexyzfilipexyz
6

cross-manager

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

Community
Basic
filipexyzfilipexyz
6

channels-manager

Manage multi-platform communication instances and messaging policies via Ravi adapters.

Community
Intermediate
filipexyzfilipexyz
6

instances-manager

Manage lifecycle and operational policies for multi-channel agent instances in the Ravi runtime.

Community
Advanced
anthony-chaudharyanthony-chaudhary
30

tail-wag

Detect and rank architectural inversions in software systems.

Community
Advanced