This skill should be used when drafting GitHub issues for the Positron repository. It provides workflows for searching duplicates, selecting appropriate labels, gathering complete context through questioning, and writing terse, fluff-free issues that precisely describe what is needed or wrong. The skill prepares issues for manual submission by the user.
SkillScore55Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/21/2026
What it changes
Passed 7 of 13 test cases with the skill, and 4 of 13 without it.
Without skill27%
With skill55%
Checks it passed that the model alone missed
Declines to process intake rotation triage.
Includes YAML frontmatter with title and labels.
Refers the user to the positron-intake-rotation skill.
and 7 more in the full report
7 fixed5 passed either way9 still failing1 broke
Pass-rate lift
+27 pp
Tokens
+173%
Agent turns
0%
Response time
-48%
Model gemini-3.6-flashMeasured 8/21/2026v112 of 22 cases passed with skill · 13 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
What script file in the Positron issue creator directory retrieves active repository labels for issue categorization?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies scripts/fetch_labels.sh as the script for retrieving labels.
Missed
Passed
case-11 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md477 linessingle file
Positron Issue Creator
Purpose
This skill guides the drafting of high-quality GitHub issues for the Positron IDE repository. It ensures issues are:
Thoroughly checked for duplicates before drafting
Properly labeled for efficient triage
Written with complete, specific information
Free of unnecessary fluff and filler
Actionable by the development team
Ready for manual submission by the user
When to Use This Skill
Use this skill when:
User explicitly asks to draft, create, file, or report an issue
User describes a bug or feature request that should be tracked
Drafting documentation or improvement requests
User says "can you draft an issue for..." or similar