No. A skill card structures what an expert already wrote or chose to state — explicit knowledge, publishable by definition. Tacit knowledge is what the person would never write down: because they don't know they know it, or because the information is too uncomfortable to put their name to.
Why is a method published under someone's own name different from an anonymous conversation?
Whoever publishes a method has already decided it's a marketable asset, with their reputation attached to it. Operational tacit knowledge is the opposite: it only surfaces once identification disappears, because the most valuable information is usually the riskiest to put a name to.
Does document extraction replace the interview?
It handles what someone already wrote while describing their own method. It doesn't handle what was never written: why a specific exception was opened yesterday, what happened in the meeting that wasn't recorded, the informal adjustment holding up a deadline. That only exists in conversation.
Structuring what someone published is an extraction problem. Reaching what nobody would write down is a trust problem — and trust isn't solved with a parser.