Could we have some example queries, generated by the Stack Exchange team themselves, to use as a reference for the Data Explorer?
Edit: Based on the comments, I need to clarify that I am suggesting creation of a very small number of queries -- maybe 5 -- as a reference for users. I am not suggesting that the SE team write hundreds or thousands of queries or that it needs to moderate user's creations.
There is a huge amount of redundancy in the queries that users have created; there are dozens of attempts to report on progress toward certain badges, questions with 4 votes to close, top answer writers, rapid climbers, and so on. The problem is that many of them do not work.
For example, I have tried out all of the queries I could find that attempt to identify questions with 4 votes to close. Most of them at least look sane -- the SQL logic is reasonable -- but not one of them produces meaningful results. In many cases, the results include question ID numbers that are not hyperlinked, even when it seems like the query should have produced text in that column. Even when the questions are hyperlinked, many of the questions have no votes to close or were closed ages ago (as in several years back). I even tried writing my own query from scratch, but ran into the same problems. I've got 14+ years experience with SQL, so this was more than a little frustrating.
Why is this important? Data Explorer has the potential to be a huge help in the community's ability to help moderate effectively, detect abusive users, and provide helpful feedback on potential bugs to the Stack Exchange team. Right now, though, learning to use Data Explorer is one part bootstrapping, one part guess work, and two parts digging through probably-busted queries written by others. A handful of canonical queries that are known to work and documented with a few inline comments would be tremendously helpful and make Data Explorer far more useful to the community.
Note: I am aware that the API also exists and has a lot of powerful features. My question, however, focuses on what can be done to make Data Explorer better. Being able to write a simple query is, at least in my experience, much faster and easier than working with an API, even a great API... but only if the query works!