roleplay-sim

Coordinate multi-agent workflow simulations locally using the Filament CLI.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/JYC11/filament --skill roleplay-sim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: roleplay-sim
Source: https://github.com/JYC11/filament/tree/main/.claude/skills/roleplay-sim
Command: npx skills add https://github.com/JYC11/filament --skill roleplay-sim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roleplay a multi-agent orchestration simulation using the filament CLI. Accepts either a custom scenario definition (JSON/YAML format) or falls back to the built-in "web app rewrite" scenario. Exercises entities, relations, tasks, messaging, escalations, reservations, export/import. Triggers on: "start rp", "pause rp", "end rp", "roleplay", "simulation", "simulate agents", "run simulation".

Core Features & Use Cases

  • Orchestrated roleplay: drive multiple agents through defined cycles to validate workflows and dependencies.
  • Scenario flexibility: supports both built-in and custom scenario definitions with validation of seeds, agents, modules, tasks, and relations.
  • Narrative orchestration: narrates cycles and actions, while executing real CLI commands against a local Filament project.
  • Knowledge graph interactions: leverages entities, relations, plans, docs, and exports to demonstrate graph analytics and reproducibility.

Quick Start

Start a default RP scenario with the filament CLI and watch the narrated cycles unfold in /tmp/fl-sim/.

Frequently Asked Questions about roleplay-sim

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

FAQPage Schema
How do I simulate multi-agent workflows locally using a CLI?▼

You can simulate multi-agent workflows locally by executing the Filament CLI to coordinate agents, validate custom JSON/YAML scenarios, and narrate defined cycles against a local project.

Can I define custom JSON or YAML scenarios for multi-agent orchestration?▼

Yes, multi-agent orchestration accepts custom JSON or YAML scenario definitions to validate seeds, agents, modules, tasks, and relations, or it falls back to a built-in web app rewrite template.

What is the best way to validate dependencies and messaging across multiple agents?▼

The best way to validate dependencies and messaging is to run orchestrated roleplay cycles that execute real CLI commands, testing escalations, reservations, and knowledge graph interactions.

Does multi-agent simulation support knowledge graph interactions and export/import?▼

Yes, multi-agent simulation supports knowledge graph interactions by leveraging entities, relations, plans, and docs to demonstrate graph analytics and reproducibility through export/import.

How do I start a roleplay simulation without a custom scenario definition?▼

You can start a roleplay simulation without a custom scenario by triggering the default built-in web app rewrite template, which executes narrated cycles and outputs to a local simulation directory.

What are the limitations when running local multi-agent simulations?▼

Local multi-agent simulations require executing real CLI commands against a local Filament project, meaning limitations depend on your local environment setup and the validation rules of your scenario seeds.