Ok after repeated attempts to contact customer service have yielded no results I'm going to address the issue here.
A week ago I respec'd my characters skill points, I knew exactly what skills I wanted and what I didn't want, so I was putting points into skills at a fairly fast pace, during this process when I put a point into the skill "Blinding Light" I experienced a bad lag spike that had caused me to D/C, when I reconnected the game registered that I had put a point into the skill. However when I tried to put the skill on my bar I would get the message "You do not know that ability" or "Ability not learned" one of those messages, basically the game thinks I don't have a point in that skill even though the plus icon on the skill itself is no longer there.
So after a few hours past I decided to respec my character AGAIN...and as you know this is quite costly especially when your in the Vet3-4 levels, Something around 15k for me to do this now. In any case respecing did not help the situation, as after respecing the skill was still showing as purchased even though I reset. So after a few days a GM actually contacted me in game and gave me a free respec, though I thought this was going to be different or they were going to reset my skills from their side. And again this did NOT work. I'm going on over a week now with that skill bugged, not heard back from customer support and getting extremely annoyed, this bug has the potential to completely break a skill from the player and I feel its not even being addressed with the concern it deserves. Sure the rarity it occurs is apparent but regardless the chance is still there, it could be someones favorite skill that gets bugged out next.
So again to have to get me to actually make a post about this just to get someone to take another look at it only proves the lack of communication, either you guys don't know how to fix this serious issue or my bug/complaint just got shelved for awhile, either way now the community knows. So yeah my fellow ESO players be careful when respecing cause you never know when this might happen.
Here is my case number: Incident: 140502-012781