I've had this happen when I tried to re-create the schema of a dev version catalyst application on a machine that had an existing version installed to somewhere in @INC. I got round it by removing the conflicting version, running the create script and re-installing, although I realise this may not be an option in your case.

I just re-created my conflict situation and adding the skip_load_external option to foo_create.pl is working here. So I am getting the errors when I run:-

but not when I run:-

 script/foo_create.pl model DB DBIC::Schema Foo::Schema create=static 
+skip_load_external=1 dbi:mysql:foo root password
[download]

I think it might matter that the option appears before the connection string, as the DBIx::Class::Schema::Loader docs say that options after the connection don't have any effect - I haven't trawled through the Catalyst code to check this, but as I say, it's working for me as listed above. (Catalyst 5.90103)

UPDATE - I've just tested it again with the option after the connect string, and it doesn't make any difference - still getting errors with skip_load_external=0, which are fixed with skip_load_external=1