You can improve signal-to-noise by listing in categories ("best", "okay", "seen it before", "academic-only") and then humans can get something out of it too. Or you can call it a loss and treat it like what it is.
The idea of listing categories is fine, but don't rely on those descriptions to give enough detail. What you think might be "good" knowledge of X might be strictly amateur to someone else. Better to tell stories and give descriptions of how you've used the technology in question.
Also, if you know something good enough to say that you're good at it, there better be multiple bullets up above explaining how you've used that technology. I've had resumes where someone says they have expert knowledge in a given technology, but nowhere in their work history do they have anything that says that they've used it. You know Oracle? Then you have to have it in a bullet up above.
Another way that you can get those details in the resume about what you know is by quantifying as much as possible. Instead of saying you wrote a Ruby app to do such-and-such, say that you wrote an N,000-line Ruby app to do such-and-such. The numbers give a sense of scale that's missing without it.
You can improve signal-to-noise by listing in categories ("best", "okay", "seen it before", "academic-only") and then humans can get something out of it too. Or you can call it a loss and treat it like what it is.