What problem does it solve? Inconsistent issue titles, vague bug reports, and ad-hoc labeling make trackers hard to scan and triage. This Skill provides shared content standards so every issue—local or on GitHub—follows the same title, body, type, and label conventions. ## Core Features & Use Cases - Title standards: Enforces sentence case, imperative mood, no type prefixes, and specific wording, with cleanup transformations for existing titles. - Structured issue bodies: Defines templates for bug reports, feature requests, example requests, and request-intake issues with problem readbacks, open questions, and confidence lines. - GitHub triage workflow: Covers issue types set via the GraphQL API, label usage rules, and procedures for new and stale issues. - Use Case: When filing a bug about a broken UI interaction, apply the standards to produce a symptom-focused title like "Pinch zoom resets selection on Safari" with reproduction steps and expected versus actual behavior. ## Quick Start Write a GitHub issue for the login timeout bug following the write-issue standards for title, body, and type.