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.

Keep in mind, a readme.MD is not the same as a readme.TXT - the formatting for markup is different.

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

Usually plugins will include wp-config.php or wp-load.php in order to gain access to core WordPress functions, but there are much better ways to do this.

It's best if you tie your processing functions (the ones that need but don't have access to core functions) into an action hook, such as "init" or "admin_init".

Please consult the Plugins API reference for more information: http://codex.wordpress.org/Plugin_API

Also please note that you need to protect your admin panels in WP. People should not be able to hit the URLs directly, so please put in some security to verify the user has access to, say, visit domain.com/wp-content/plugins/fliptu/fliptu-delete.php

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

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.

Also note that you're using <link> and <style> instead of the correct enqueues in your header and footer files. You really should integrate those files with WordPress so they can use all the functions etc. That will also make things safer, as it'll prevent non-users from being able to hit those files directly, if you do it correctly.

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

All plugins are expected to be submitted with the code complete and ready to go, including a valid readme.txt file. Either you did not include a direct link to your code with your submission, or the link you provided was invalid/inaccessible. Could you please reply with a link so the plugin can be downloaded? Alternately you can reply to this and attach your .zip or .rar file.

Note: If you submitted a link to an external site like RapidShare, DropBox, or Google, and you are receiving this email, please do not just send the same link. We probably had issues getting it to load, so sending the same link will likely get you the same reply. If you need a place to version control your code while you work on it, you can use GitHub to safely host your code while you're developing it.

Please reply with 7 days. If a reply is not received the submission will be rejected and you will have to submit the plugin again, with code, should you want your plugin hosted.

Thanks.