Skill systems and other data-rich structures: inheritance or database?

I've gotten to the point in my development cycle where I need to start looking at how skills will be tracked and organized. Right now, the simplest solution I can think of is to make a core SkillBasic.cs class that contains universal features like names and MP cost, build an empty Use() function into it, then make a new class that extends SkillBase for each new skill, overriding Use() to account for different skills having drastically different utilities. If I create a single delegate or...

Skill systems and other data-rich structures: inheritance or database?