It's probably hard for most users to read a long space-separated list of plugins.

We could categorize plugins. It could be in a tree like this:

• Administration

* admintools - channel tools (nick, op, ban etc)
* auth - users' auth to the bot
* dynacode - eval() for bot admins
* plugintools - (un)load plugins for bot admins

• Anti-spam features

* blockbot - channel flood/spam protection

• Networking

* dns - returns a fully qualified domain name for an ip or host
* isitup - checks domain at http://isitup.org
* tinyurl - tinify an url using http://tinyurl.com
* rss - report new RSS feeds to a channel ('rss-add','rss-list', 'rss-del')
* urltitle - send titles of URLs into channel by request or for every mentioned URL (edit plugin to set)
* yt - http://youtube.com lookup by id
* web search
* ddg - http://duckduckgo.com web search
* google - http://google.com web search
* wikipedia (wp) - http://wikipedia.org lookup

• General

* info - infobot. commands 'learn a as b', 'forget a', 'what is a'.
* What is the infochar? Messages beginning with the infochar trigger the following factoid to be displayed.
* karma - karma. commands 'nick++', 'nick--', 'karma nick'.
* ping - ping/pong
* printer - print events to console
* rpn - reverse polish notation calculation
* sed - sed-like replacement for in-channel conversation
* seen - check which channel and when a nick was last seen on
* smack - has the bot smack someone

• Experimental

* games - not implemented
* wikinews - a custom plugin to output http://www.wikinews.org review queue

Or we could tag, like add 'math' 'calc' to rpm, and 'web' 'network' to urltitle, 'web network search' to ddg, and so on. This could be more flexible.

We would need to think of a good plan - something easy to write, and easy for users to read.