There isn't a catch-all script, this is something you would normally manage yourself. I use a collection of scripts, some of which I wrote, some I didn't - automatic monitoring, morning / afternoon check schedules, and many other different methods. Try writing out a list of priorities - what do you actually want to know about your database server / SQL Server instance / databases? What problems have they had in the past?

Management and administration of the 'health' of the databases is basically a broad description of the job of the DBA anyway, there really isn't one script to rule them all.