Extra steering: Don't claim you found the root cause, use <details>, use /humanizer

Thank you for the skill! It will come handy in my arsenal against AI slop. I have the paragraph below in user-level AGENTS.md, might be useful to incorporate into this skill too.

> External-facing docs (README, GitHub issues, PR descriptions, first emails — not internal docs): brevity, drafted for the audience. A maintainer knows their software — show preliminary findings, don't declare the root cause for them; hide detail in \. Use [/humanizer](https://github.com/blader/humanizer) skill against AI slop.

Start by locating the skill instructions and compare them with the guidance shown from user-level AGENTS.md, including the /humanizer reference. Incorporate the requested external-facing communication guidance into the skill, with the change complete when it covers preliminary findings, for detail, and the linked humanizer skill.

Written by the indexing model from the issue text.