ATM I think the variable route is the only way to check if a skill is learned or not, as long as you keep your variable list organised it shouldn't be a problem though. Either way you're still gonna need a switch to check against the skill if has been learned (yes) OR has not been learned (no), in your suggested case above.. "FireballLearned" On or Off.

I'd suggest to use 1 switch variable at least per skill, this will make things much easier for you to control things such as scenes where a player might not be able to use certain skills in battle for say.. extra strategy/tactical additions to your battles for example. Though I totally get the pain it's going to be if your game is going to have a TON of skills to use in it, organisation of the variables list is key then to make things easier.

That's what I was afraid of. I even checked the Wiki and couldn't find a variable like that so I was hoping that maybe I missed something. It is what it is, though.