All of which I never see used in a professional capacity for the vast majority of software developers.
What I do see used quite often is the ability to communicate to customers or other engineers in a clear, succinct and enjoyable manner using the English language.
Not just underestimate, even outright condemn. Like the people who defend Linus's form of "communication" on the kernel mailing list as "to the point" or "efficient". Anyone who thinks that's an acceptable style of communication from/to any human being is wrong and a perfect example of why the tech companies in general should probably make their engineers attend a speech and/or social relationships class. Somewhere along the line, "engineering culture" decided any communication protocols outside of TCP, UDP and syscalls are a waste of time.
He's an asshole on occasion, but that's not the same as communicating poorly.
"Ends don't justify the means" kinda thing... but I know I'm not going to convince you in this thread; and you're definitely not going to convince me otherwise. There are too many rude people in tech that don't know how to communicate properly with people. Rudeness has somehow become acceptable in the tech-industry so they can't see the problem they have.... and it _is_ a problem.
Conversely to Linus, someone can be perfectly polite and pleasant but fail to communicate effectively because they don't convey any meaningful information. Such a person would have poor communication skills, but not be an asshole. Linus has good communication skills, but is an asshole.
Anecdotal irony: not 24 hours ago a colleague and I had to reverse engineer a hairy mess of deeply nested if/then/else clauses that should not exist that turned out to be composed mostly of tautologies. I definitely wish to throw books at some people, preferably of the steel-bound, razor sharp edged kind.
Conclusion: you're not drawing Karnaugh tables daily in front of you, but having manipulated the fundamental rules of logic has trained your neural net and makes you much more effective at solving logic problems in a wink and not write crap code, and also simply able to debug stuff efficiently, if at all. I am regularly aghast at people drawing completely invalid conclusions from broken "common sense" logic propositions (A=>B therefore B=>A, or various other syllogisms).
If you're a consultancy that writes CRUD apps I can see emphasizing communication skills over technical skills but you're not Google.
Is it? I've met quite a lot of coders who think they're good communicators but really, really aren't.