[el_Paraguayo]

It all comes down to how you want this to be implemented.

Skin Widgets is, I think, a service that generates a heap of infolabels which skinners can then choose how to implement in their skin. This means that, if the functionality has been included in the skin, there's no need to run a script to launch the display. However, this basically passes the work of coding this to the skin developers/maintainers and I suspect this will not be an important enough feature for them to want to focus on.

The sportscenter (the name's not that bad, but I'd prefer it to be centre with "re"... it's a British thing!) is slightly different, it seems to run as a standalone script and comes with skin specific implementations as part of the script.

For the favourite team widget part - I, personally, would rather this was done similarly to the Skin Widgets - i.e. have a service creating and updating infolabels - so I'll start on that basis. On the plus side, either route will require the creation of some xml files so it shouldn't be too big a job to adapt anything I do for use in the sportscentre!