What problem does it solve? Maintainers and contributors responding on the amd/gaia GitHub repository risk inconsistent tone, over-long replies, mishandled security reports, and wrong doc links. This Skill enforces a single response protocol so every public reply follows the same rules. ## Core Features & Use Cases - Security escalation protocol: Never discuss exploit details publicly; redirect reporters to private security advisories and tag @kovtcharov-amd, with clear rules for issues versus PR reviews. - Response-type length caps: Distinct shapes and word caps for quick answers, how-tos, bug reports, feature requests, and complex discussions. - Escalation and doc-link map: Defines when to escalate to the maintainer versus answer directly, plus a map of code locations and documentation pages for pointing users to the right resource. - Use Case: A user opens a bug report about RAG initialization failing. The Skill guides you to lead with the diagnosis, ask for specific repro steps, cap the reply near 200 words, and link the relevant docs page. ## Quick Start Ask the assistant to draft a reply to a GitHub issue or PR comment on amd/gaia, pasting the issue text and stating whether it is a bug report, question, feature request, or security concern.
