Damn, I was browsing around GitHub and this project really just has a “skill issue” label for issues.
@scarlet Based
@evamik @scarlet It's most likely an issue with their UI design or documentation, whicheever applies ​
@scarlet is it humorous (I'm worried it's not).
@scarlet this would be awesome if the project is well documented (it's probably not well documented)
@kit @scarlet Yes, I wouldn't even be mad if my issue would end up being tagged like this. There's plenty of people who may just be inexperienced and need a hand, which will help future users and maybe even be used in the documentation (will probably never happen) :D
@scarlet ive seen this before too but forgot where lmao
@scarlet passive aggressive. Well not that passive.
@scarlet I think they misspelled “Documentation Issue”.

@ImpossibleUmbrella @scarlet that can only be true if people are willing to look at documentation… which is rare

(I agree a “skill issue” tag is a red flag. But I don’t think “just add docs” is often a great fix)

@scarlet I need to do that on the work bugtracker
@scarlet One more project and maintainer to avoid, check!
@scarlet @0xabad1dea harsh! I would have gone with "documentation enhancement".
@scarlet @quixoticgeek Yes but not the side they think.
@scarlet that's an "every wrong door" policy
@scarlet the newer, hipper PEBKAC
@scarlet It seems reasonable to reply to that assessment with "if you don't know how to improve the interface, maybe ask the community advice instead of just assuming that you're incapable..."
@scarlet `git gud`, I suppose
Skull Issues GIF - Tenor GIF Keyboard - Bring Personality To Your Conversations | Say more with Tenor

Skull Issues GIF - Tenor GIF Keyboard - Bring Personality To Your Conversations | Say more with Tenor

Tenor
@scarlet devs when you report a bug 
@scarlet @bradwilson funny way of writing "we f'ed up the user experience"
@scarlet @rixx we have a "面倒くさい" label