Cool! Sheriff-o-Matic sounds like a good place for this to live. At the moment, it's a bit confusing to get started on working on Sheriff-o-Matic, which we want to improve, but I believe the README should have enough information. 

The list of routes in Sheriff-o-Matic is at frontend/main.go. Then, we usually add the handlers for routes to som/handler. If you need any help while working on Sheriff-o-Matic, feel free to ask me or Sean. 

(Also, does this mean Skia might have some interest in usin Sheriff-o-Matic? If so, that's something we could follow up on separately. We're always open to supporting new clients.)

So this was a request from Paweł so that he doesn't have to be all-time sheriff for these rollers.  I was hoping it'd be something you folks could knock out easily, but I can take a look after clearing my stack a bit.

As for Skia on Sheriff-o-Matic, I think it's something which could be useful for us, but I assume there are fundamental differences in the way we run tests (eg. we don't use gtest) which would make it difficult to get useful data into SoM.  Most of our sheriffing is done on perf.skia.org and gold.skia.org for performance and correctness, respectively.  Pass/fail test failures are comparatively rare.

Consult the rotations for current sheriffs, SoM isn't the source of truth for this data.