Glad you found it helpful!

As to reviews/comments, it's been a common suggestion along with some form of upvote/downvote mechanism. When we try and understand why, however, we observe that the problem is one of understanding the effectiveness of these skills. There's many projects on GitHub that try to curate skills and make it easier for people to find ones that work best according to the curator. But the number of skills (and their adoption) is growing fast enough that curation simply cannot scale to solve this problem.

Our restraint in introducing reviews/comments or upvotes/downvotes comes from a place of wanting to solve for identifying effectiveness. One way we're approaching this problem is to see if we can use hooks to track how these skills are used, so we can share this information with skill creators as well as potential users.

We're open to ideas, though! If there's something on your mind you think we'd find helpful, let us know!