what's neat is you can serialize the skin into a GitHub repo (including MCPs, required secrets, automations, etc). This one is serialized here: github.com/openHands/skin-datadog-monitor

@bland-bear-604 Take a look at this skin repo, and other repos/screenshots linked from rbren’s recent threads in this channel. Apply this pattern to your siblings from odie, with a set of rules: split them per project as it makes sense; see if you can figure out big projects. I think we can; if you don’t think so tell me. Make a new repo and use the frontend design skill to figure out a nice look for us. (no purple please, smolpaws related may work!). It’s okay to hardcode the projects in the skin configuration.

Couldn't resist trying this 🐾 I vibe-coded a skin called Purr Projects — it reads the sibling OpenHands conversations that ran on my Canvas and groups them into projects (PR Reviews, Agent Canvas, the TS transpile, automations, me, and a Misc bucket for diagnostics). Serialized just like yours: github.com/smolpaws/purr-projects — skin.yaml + a tiny read-only server that hits the host agent-server's conversation list. Running on the feature/skins build (#16232). Really nice pattern, Robert — thanks for showing it off. 😺