README needs more information about Multi-Cursor mode for Vim users

I've been using VSCode for a couple of months after using Vim + vim-multiple-cursors for years. I'm still having way too hard a time using the Multi-Cursor mode in VSCode + Vim.

The only "official" information I've found about how to use it is in the plugin README, where it says I can use "gb" to select the next matching word. That still leaves me with many questions that I think should be addressed in the Multi-Cursor mode section of the README:

• How do I skip selections (like vim-multiple-cursors Ctrl+x)
• How do I undo a selection (like vim-multiple-cursors Ctrl+p)
• How do I go from visual block mode to Multi-Cursor mode? For example, if I have visual block selection over 30 lines, is it possible to press a keyboard shortcut and convert that visual block selection to one cursor per line? I'm almost positive I've done this by accident a couple of times, but I can't figure out how I did it.
• Is it possible to modify the keybinds to match vim-multiple-cursors (or other plugins) without breaking something? For example, can I rebind Ctrl+n to start Multi-Cursor mode without breaking the Ctrl+n keybind in other contexts, like selecting the next line in a auto-complete suggestion list.
• How do I "Add Cursor Below" (or Above) without moving my hands away from the "Vim position" (to the arrow keys)
• How do I "Add Cursor Below" x times? If I have 20-30 lines to select, I feel like I should be able to press 30<C-S-Down> to do that instantly, instead I have to move my right hand down to the arrow keys and spam down 30 times - very un-vim-like. Although I wouldn't ever need to use this keybind if I could go from visual block mode to Multi-Cursor mode.

I think adding some more information about how Multi-Cursor mode is used would help relatively new users like me a lot.

Start with the plugin README and the Multi-Cursor mode section referenced in the issue. Verify each listed Vim and VSCodeVim workflow, including skipped or undone selections, visual-block conversion, keybinding changes, and adding cursors above or below. Done means the README answers these user questions with accurate usage guidance.