Design for skip vs next when next requires waiting

I have an app that serves users content which requires them to say whats on the screen. They can move on to the next piece of content only after some period of time depending on the length of the content (usually 5-10 seconds but it can be as long as a minute)

They are also given the option to skip to the next piece of content, the difference being when they click next we save that as being said and when they click skip its basically ignored that they even saw it. We later provide them with statistics on how much they said and other users (who loaded the content) can see how many people used their content.

I showed this to someone and they said its too ambiguous and not obvious what the difference is. I have a help icon that explains the screen at the top, but based on their usage I could tell many people would never bother to click on it. (I suggested maybe we could put a countdown to when Next becomes enabled but they thought that it still wouldn't be intuitive what it was counting down to)

I thought about removing the skip button and only putting in the next button. I would then judge whether it is a 'skip' or 'next' behind the scenes based on how much time was spent on it.

However, the reservation I have with this method is that it is hiding how it works from the user which can mean that they can be confused when they look at their statistics and it seems to be way off (one option to fix this is to have next to the statistic a button saying "My stat is not accurate" or something like that)

Is there a better way of doing this?

This is a basic mockup of the screen (its for mobile)