You could easily take this one step further and give it the ability to then accept which command the user meant (like some shells do). By changing the 'ambiguous match' (you have it 'ambigous', BTW) part to create a hash. Actually, if you make @matched into %matched with the structure of:

%matches = (1 => 'match1',
            2 => 'match2', etc...
           );
[download]

You could then make the 'ambiguous match' section as which was meant.. ie..

'monkey' is ambiguous. It could mean monkeylover [1] or monkeyman [2]:
[download]

The user would then enter 1 or 2, you read it on STDIN, and run the correct sub. Just an idea :)

Cheers,
KM