flywheel-tool-feedback

Submit structured tool feedback to agent-mail for improving flywheel sessions.

3|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-tool-feedback-burningportra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flywheel-tool-feedback
Source: https://github.com/burningportra/agent-flywheel-plugin/tree/main/skills/flywheel-tool-feedback
Command: npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-tool-feedback-burningportra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tool and command issues encountered during agent-flywheel sessions often go unreported or are lost, making it impossible to spot recurring problems and improve the workflow over time. ## Core Features & Use Cases - Structured Feedback Collection: Gathers actual behavior, expected behavior, and severity (minor / annoying / blocking) through a guided survey. - Persistent Storage via Agent Mail: Records feedback as a message with subject "Tool Feedback: <tool-name>" on the agent-flywheel-feedback thread using the agent-mail MCP. - Recurring Issue Detection: Searches existing feedback and flags when 3 or more similar items exist, suggesting a bead be created to address the pattern. - Use Case: After a command behaves unexpectedly mid-session, invoke the skill with the tool name and what went wrong; the feedback is logged and checked against prior reports. ## Quick Start Ask the agent to submit feedback about a tool, for example: record feedback that the flywheel-status command showed stale checkpoint data and rate it as annoying.

Frequently Asked Questions about flywheel-tool-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit feedback about a tool in agent-flywheel?

Invoke the skill with the format "<tool-name>: <feedback>" or just the feedback text. If no tool name is given, the skill asks which tool you mean, then collects what happened, what you expected, and a severity rating.

What information does tool feedback collection require?

The survey asks three things: what actually happened, what you expected to happen, and a severity level of minor, annoying, or blocking. You can provide these upfront in the arguments or answer them interactively.

Where is submitted tool feedback stored?

Feedback is sent via the agent-mail MCP send_message function with the subject "Tool Feedback: <tool-name>" on the agent-flywheel-feedback thread, marked with low importance.

Does the feedback skill detect recurring tool issues?

Yes. It searches existing messages for the same tool name and, when three or more similar feedback items exist, flags it as a recurring issue and suggests creating a bead to address it.

What happens if I don't specify a tool name in my feedback?

The skill prompts you with "Which tool or command are you giving feedback on?" before proceeding with the rest of the structured survey.