Ubuntu – Bash script: How to execute commands consecutively without waiting for the previous one

one terminal with two tabs:

gnome-terminal --tab --tab

use the -e switch to execute commands (or scripts):

gnome-terminal --tab -e "command1" --tab -e "command2"

(I don't think there is an easy way of feeding your credentials to skype via the terminal.)
Update: check w4YGcbTeIH's answer, skype allows giving credentials via the command line.

But beware, your credentials would be exposed and this should be avoided.

A script to open skype and chromium-browser would look like the following:

#!/bin/bash

skype --dbpath=<path> &
chromium-browser &

Put this code into myscript.sh and execute chmod +x myscript.sh (in a terminal) to make it executable.

About skype:

• you can run skype without arguments (skype &) and it will load your default user profile ~/.Skype.
• run it with --dbpath=<path> where <path> is your actual path of the Skype profile you want skype to load.

To run the script do one of the following:

• open a terminal and execute ./myscript.sh
• double click on the script and choose Run in the dialog.

set login "sasuke"
set addr "hostname"
set pw "mypasswd"
spawn ssh $login@$addr
expect "$login@$addr's password:"
send "$pw\r"
expect "#"
send {output=$(sudo virsh list --all | awk '/running/{print $2}' | tail -2)}
expect {
    password: {send "$pw\r"; exp_continue}
    "#"
}
send {sudo virsh dominfo "$output"}    ;# don't know if you need quotes there
expect {
    password: {send "$pw\r"; exp_continue}
    "#"
}

In Tcl (and, by extension, expect), curly braces act like the shell's single quotes: inhibit variable expansion.

The multi-pattern form of expect is useful for the case where you may not see a pattern. The exp_continue statement essentially "loops" within the expect so you can send the password and continue to expect the prompt. Since there is no action associated with the prompt pattern, control passes from the expect command to the next one.

I would recommend you save this as a separate script. First line should be

#!/usr/bin/expect -f

If you want to embed in a shell script:

#!/bin/sh
expect <<'END'
   # code as above
END

Note the quotes around the first "END" -- that has the effect of single quoting the entire here-document so you don't have to worry about the shell interpreting the Expect variables