draft-issue
Skill14 starsChanged 3 months agoMITView on GitHub
Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Draft Issue”. A useful skill states the six fields from Skills and routines. A Slack thread, email, or repro pack must become a GitHub issue before the bug evaporates — written down, not posted until approved. Steps are numbered. Links work. No customer PII. No "please fix" without expected behavior. Issue title, body in the repo template, suggested labels, and a…
6 other projects use a version of this.
Adopted by
Most recently taken up by
- open-telemetry/opentelemetry.iotheir own version, first seen Oct 17, 2026
- Tmeister/skillstheir own version, first seen Oct 13, 2026
- i-am-bee/agentstacktheir own version, first seen Oct 8, 2026
- Xenoneqq/claudified-workflowtheir own version, first seen Sep 24, 2026
- couimet/my-claude-skillstheir own version, first seen Aug 19, 2026
- zahardev/aicontexttheir own version, first seen Apr 22, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- i-am-bee/agentstack★ 1.2ksame name
- open-telemetry/opentelemetry.io★ 996same name
- zahardev/aicontext★ 2same name
- couimet/my-claude-skills★ 1same name
- Tmeister/skills★ 1same name
- Xenoneqq/claudified-workflow★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- convert/claude.mdCLAUDE.md
- docs/llms.txtllms.txt
- audit-subscriptionsSkill
- cited-researchSkill
- cloud-bill-noteSkill
- collate-feature-asksSkill
- coordinate-launchSkill
- daily-digestSkill
- defend-calendarSkill
- design-bot-templateSkill
- detect-docs-driftSkill
- diff-competitorsSkill
- draft-call-followupSkill
- draft-changelogSkill
- draft-newsletterSkill
- draft-security-answersSkill
- draft-sqlSkill
- draft-support-replySkill
- garden-memorySkill
- harden-repoSkill
- incident-timelineSkill
- install-teamSkill
- interrogate-assumptionsSkill
- investigate-perfSkill
- log-promisesSkill
- package-evidenceSkill
- plan-tripSkill
- prep-meetingSkill
- queue-socialSkill
- ramp-new-hireSkill
- rank-account-healthSkill
- recommend-media-reallocSkill
- reconcile-expensesSkill
- remix-contentSkill
- reproduce-bugSkill
- research-accountsSkill
- review-pr-riskSkill
- route-workSkill
- sanitize-shareSkill
- scout-x-threadsSkill
- source-talentSkill
- sweep-ciSkill
- triage-inboxSkill
- vendor-renewalsSkill
- watch-aeoSkill
- watch-brandSkill
- weekly-saas-financeSkill
- write-win-lossSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Prefer the repro pack over the original complaint when both exist.
- Distinctive: line 25
Stop with a preview. Do not click Submit.
- Distinctive: line 39
Do not create the GitHub issue until the owner says to file it.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Draft Issue
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Draft Issue”.
A useful skill states the six fields from Skills and routines.
1. When to use it
A Slack thread, email, or repro pack must become a GitHub issue before the bug evaporates — written down, not posted until approved.
2. Required inputs and access
- Thread, report, or repro pack
- Target repository
- Issue template if the repo has one
3. Sequence of work
- Extract title, actual, expected, steps, environment, and links.
- Prefer the repro pack over the original complaint when both exist.
- Fill the repo's issue template. Label suggestions only.
- Stop with a preview. Do not click Submit.
4. How to validate the result
Steps are numbered. Links work. No customer PII. No "please fix" without expected behavior.
5. What to return
Issue title, body in the repo template, suggested labels, and a "ready to file" checkbox for the owner.
6. What requires approval
Do not create the GitHub issue until the owner says to file it.
Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.