Being able to talk about what you've done with the product (product under test) and how you tested are the biggest parts to expressing your ability to testing. It's all about test framing and then telling your testing story.
Michael Bolton on Test Framing and Testing Stories (via the AST website):
Test framing is the set of logical connections that structure and inform the test. To test is to compose, edit, narrate, and justify two stories. One is a story about the product–what it does, how it does it, how it works, and how it might not work–in ways that matter to your clients. The other is a story about your testing–how you came to know and understand the product story.
Framing and creating a story plays a important part (or at least it should) in an interview, working with teams inside and outside your company and even in writing a blog. This can be a major stumbling block for testers when they have trouble explaining what they did, why they did it, and being open to new ideas or admitting things they might never had considered.
If you've got a compelling and accurate testing story for those "cobbled together scripts" you'll do just fine when it comes time to express what you've done.