mock-data-maintainer

What problem does it solve?

Creates coherent, scenario-grounded mock/demo/seed data for Rudder development, testing, screenshots, and product demos so UIs and workflows behave like real agent-team operations rather than random placeholders.

Core Features & Use Cases

• Scenario-first mock generation: Builds a causal “work loop” data spine (goal → issues → agent runs → reviews/approvals → feedback/learning → better future runs) that keeps pages relationally coherent.
• Intent-aware outputs: Produces the right kind of artifact for the request (live seed commands, deterministic fixtures like JSON/CSV/SQL/TypeScript, or scenario briefs) including usage and reset notes.
• Rudder-specific guardrails: Ensures organization boundaries, dense UI evidence (non-empty transcripts/run outputs where needed), and includes meaningful edge states (budget limits, approval gating, conflicts, permission errors, partial failures).
• Reuses canonical datasets: For landing screenshots and demo orgs, reuses curated references (e.g., landing demo org and Rudder Studio) instead of inventing one-off orgs.

Quick Start

Use the mock-data-maintainer skill to generate seed data for a landing-demo-style Rudder org by asking: Create realistic demo seed data for a local Rudder landing workflow so I can open the dashboard and issues routes and see agent progress and approvals.