What problem does it solve? Staff who spot an error in an org's skills usually have no GitHub seat and no way to open a pull request, so their feedback arrives as vague prose that queues and dies. This Skill turns that feedback into a structured proposal bundle containing the problem, the fix, the evidence, and an applyable patch, then routes it through whatever channel the reporter actually has. ## Core Features & Use Cases - Locate and draft safely: Find the installed file for any skill, agent, or reference by name, then copy it to a scratch working copy so the live install is never edited. - Bundle with a real patch: Generate a proposal bundle with title, problem, fix, evidence, author, type (correction, addition, clarification, removal, bug), and a unified diff against the installed file. - Channel-aware submission: Detect which submission paths are available (Slack channel with Claude Tag, GitHub PR via gh, chat/project-tracker/email connectors) and pick the highest one that works. - Maintainer workflow: List pending proposals, dry-run check whether a patch still applies, and apply it to the working tree without staging or committing. - Use Case: A staff member says the document-find skill lists a retired SharePoint site. The agent locates the file, drafts the corrected copy, bundles it with evidence from a team call, and submits it to the maintainer, who applies it with one command. ## Quick Start Ask the agent to file a proposal saying the document-find skill lists a retired SharePoint site, with the correction and evidence, and submit it to the maintainer.
