Alternately, you can use this tool to generate one:
http://tools.trepmal.com/wp-readme-generator/

A readme.txt is needed so your plugin will display correctly in our repository, but also so we can make sure you're providing the users with all the information they need before they install your plugin. Our goal with this is to make sure everyone knows what they're installing and what they need to do before they install it. No surprises :)

This is especially important if your plugin is making calls back to your own servers. For the most part, we do not permit offloading of images or code, however in the case where you are providing a service (like Disqus or Akismet or Twitter), we permit it. The catch is you have to actually explain this to the layman in your readme, so they know where data is going.

Please send a link so the completed plugin can be downloaded. Alternately you can reply to this and send a .zip or .rar file. If this is for a new plugin request, please reply within seven days of this email or we will reject your plugin.

Please review http://codex.wordpress.org/Function_Reference/wp_enqueue_script and update your plugin accordingly.

Keep in mind: Offloading the default jquery and other scripts to Google is similarly disallowed. If your code doesn't work with the built-in jQuery, it's most likely a noconflict issue. If you can't guess, we -really- want you to use our jquery, and if you can't, we need to know why so we can fix things for everyone.

When you've corrected your code, reply to this email with the updated code attached, or provide a link to the new code.