Help the user file a bug report or feature request for Nimbalyst. Activates when the user opens the in-app feedback flow or runs /feedback:bug-report or /feedback:feature-request. Coordinates evidence gathering, anonymization, and posting to GitHub Issues.
SkillScore59Maintained
Automatic
◆Product Management pack
Last verified 8/13/2026
What it changes
Passed 9 of 16 test cases with the skill, and 9 of 16 without it.
Without skill55%
With skill59%
Checks it passed that the model alone missed
targets repository nimbalyst/nimbalyst with issue template bug_report.yml
notifies the user of the switch and transitions from bug_report.yml to feature_request.yml
displays the issue body in chat and opens a URL without a body while instructing the user to paste the content
3 fixed10 passed either way7 still failing2 broke
Pass-rate lift
+5 pp
Tokens
+4%
Agent turns
0%
Response time
-49%
Model gemini-3.6-flashMeasured 8/13/2026v113 of 22 cases passed with skill · 16 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
I am filing a defect report for Nimbalyst. Which repository target and issue template file should be specified during URL construction?
What was checked, without and with the skill
Checked
Without skill
With skill
targets repository nimbalyst/nimbalyst with issue template bug_report.yml
Missed
Passed
case-13 · gemini-3.6-flash · 8/13/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md35 linessingle file
Nimbalyst Feedback Skill
This skill is the entry point for the Nimbalyst in-app feedback flow. It activates when:
The user runs the /feedback:bug-report slash command
The user runs the /feedback:feature-request slash command
The user opens a session with sessionType: 'bug-report' or sessionType: 'feature-request'
Behavior
Read the matching command file:
For bug reports: commands/bug-report.md in this plugin
For feature requests: commands/feature-request.md in this plugin
Both commands share these constraints:
The user is the gate. Never call mcp__nimbalyst-situational__feedback_open_github_issue without explicit user approval of the final title and body.
Anonymize aggressively. Run anything that includes file paths, log content, environment strings, or workspace identifiers through mcp__nimbalyst-situational__feedback_anonymize_text first, then read the output and redact anything else that looks sensitive.
Honor the intake flags. Bug-report sessions include Log gathering: allowed or Log gathering: not allowed; feature-request sessions may include UX mockup: requested or UX mockup: not requested. Only bug reports may read logs, and only when log gathering is allowed.
Handle long reports. When the drafted body exceeds the URL safe length, the URL builder returns reason: 'too-long'. Fall back to: show the body in chat, open a no-body URL, tell the user to paste.
Target repo and templates. Bug reports use bug_report.yml; feature requests use feature_request.yml. Both target nimbalyst/nimbalyst. Don't hardcode the URL — let the URL builder handle template selection and field-id routing. The GitHub issue type (Bug / Feature) and status:needs-triage label come from the template frontmatter, not from the URL builder.