My name is Eliud and I am a Year 13 T Level student, studying Digital Software Development. And I’ll be honest, I love my T Level. I had a choice between A Levels, BTEC and a T Level. Two of them I knew, but T Levels, I had no clue about it. I’ll never forget my secondary school careers advisor who put that option in my mind, and without her, I wouldn’t be here today writing this.

Now, let me take you through the journey of building T-SkiLL and the whole goal behind it.

The idea struck me on a random winter night. It was the Christmas holiday and I wanted to start revising for my next mock exams. So I started looking online, since I’d pretty much rinsed my school resources, and I found some materials. Some PDFs, some past papers. Then I looked at my browser, stacked to around 15 tabs open. I had a lot, but that “a lot” had a problem. Some of the materials made you pay, some were flat out old, and others just didn’t have the format I was looking for.

Then I realised something. During my GCSEs, there were tons of websites and resources you could use, which made revising at home easy. But T Level didn’t get the same treatment. It’s not that the material didn’t exist, it just wasn’t maintained in the same way. So at that moment, I decided I’d work on something.

One place, one platform, one website.

Somewhere for all T Level students to revise. And after a lot of thinking, I called it T-SkiLL.

From that moment, all I cared about was making it happen. When I started asking students in different schools, either doing my T Level or another, hearing their revision experiences made me realise how big this gap truly is.

I started learning React Native for the app, but that learning happened alongside my mock exams, industry placement and other commitments. So instead, I started learning about app stacks and how app development is structured. I had a lot of ideas for T-SkiLL, but actually building them was going to be the hard part, with barely any experience, and traditional learning would take me too long. So I started asking myself what I could use to speed things up without cutting corners. That’s when I properly leaned into AI-powered tools, something that was itself still growing at the time.

Now using AI didn’t make me lazy. AI has played a big part in how I’ve built T-SkiLL, not as a shortcut, but as the fastest way for me, one student, to bring an idea like this to life. I still made every product decision, wrote every massive prompt, tested every screen, and learnt the underlying stacks properly along the way. AI just got me there faster.

The best way to think of it is that I’m the architect, giving the builders what to build.

So I started taking AI courses, learning how to actually get the outputs I wanted, including some through Google Skills or Coursera. And I kept moving from tool to tool. For example, I moved from Cursor to Claude Code after a few months, because it just wasn’t getting me the results I needed. From there, I used the React Native knowledge I already had and learnt the basics of Next.js and Expo, taking courses to learn how to use AI properly alongside it.

The number of prototypes, alpha or near finished builds of T-SkiLL are insane. It was me building and spending nights working on it, then just scrapping it completely, regardless of how much effort I put into it. But hey, I landed on a build that I felt satisfied with and that’s the one you’ll be seeing!

Even through my mock exams, I kept working on T-SkiLL. Friends and teachers told me to slow down and focus on my exams, but I kept going.

Alongside that came cold outreach, which was me messaging people on LinkedIn. Some said yes, some said no. But through that, the team grew, and I’ll forever be grateful for it. Even with not everyone being active at every point, the people who do support, who do contribute, whether through beta testing, content, or anything else, have given up their own time voluntarily, and they’ll always have a place in what T-SkiLL becomes (especially my classmates).

So, what’s next? We’re opening in autumn 2026, starting with our first subject, Digital Software Development. From there, we’ll continue launching more subjects, and we’ll keep going until every T Level subject has a home here. We’ll also keep T-SkiLL updated for as long as the qualification exists, so don’t worry about us dying young. The goal has always been to build the best revision experience for T Level students, engaging, gamified, and built to last.

Built by students, for students.

So yeah, thanks for reading, and I can’t wait to fully launch and get everything out! I have so much planned for T Level, not just this, because of how much it’s done for me. And hopefully, through God, all will go well!