skill-feedback-collector
by @2019-02-18
Human-in-the-loop MCP feedback collector with task queue. Pauses to collect human input via browser UI before continuing. Use when completing tasks, encounte...
clawhub install skill-feedback-collector๐ About This Skill
name: skill-feedback-collector description: Human-in-the-loop MCP feedback collector with task queue. Pauses to collect human input via browser UI before continuing. Use when completing tasks, encountering uncertain parameters, needing user confirmation, working with coding plan subscriptions, or when you should ask instead of guess. Also covers batch task execution via auto-dequeue. metadata: {"clawdbot":{"emoji":"๐ฌ","requires":{"anyBins":["node","npm"]},"install":[{"id":"npm-install","kind":"node","package":"skill-feedback-collector","label":"npm install && npm run build"}],"os":["linux","darwin","win32"]}}
Skill Feedback Collector
Pause the agent and wait for human feedback via a browser-based UI connected through WebSocket. Includes a task queue for batch execution of pre-loaded tasks.
When to Use
Instructions
Follow these guidelines when this skill is active:
1. After completing a task, call ask_human_feedback with a summary and options for next steps. This lets the user decide what to do next rather than ending the session.
2. When unsure about implementation details, call ask_human_feedback with your question instead of making assumptions. Getting explicit input leads to better results.
3. The response from ask_human_feedback is your next instruction. Execute it, then call ask_human_feedback again when done. This creates a productive feedback loop.
4. If the task queue returns a task automatically (queue was non-empty), execute that task and call ask_human_feedback again when complete. The queue feeds tasks until empty.
5. Mode switching:
- User says "free mode" / "่ช็ฑๆจกๅผ" โ call set_feedback_mode(enabled: false) to work without pausing
- User says "feedback mode" / "็กฎ่ฎคๆจกๅผ" โ call set_feedback_mode(enabled: true) to resume the confirmation loop
Best Practices
Tools
ask_human_feedback
Pauses execution and sends the reason to the browser UI. Returns the human's text response. If the task queue is non-empty, the next task is auto-dequeued and returned (with a short delay for UI visibility).
Parameters: reason (string) โ summary of work done and what input you need.
Example reason format:
Completed: [specific work done]
Changes: [files modified, endpoints added, etc.]What would you like me to do next?
1. [Option A]
2. [Option B]
3. Something else
set_feedback_mode
Toggle feedback confirmation on/off. When off, ask_human_feedback returns immediately without pausing.
Parameters: enabled (boolean)
Setup
npm install && npm run build
MCP configuration:
{
"command": "node",
"args": ["build/index.js"],
"cwd": "/path/to/skill-feedback-collector"
}
Browser UI: http://
| Env Variable | Default | Description |
|---|---|---|
| FEEDBACK_PORT | 18061 | HTTP and WebSocket port |
| FEEDBACK_TOKEN | (empty) | Optional access token for the UI |
Workflow
User message โ Agent works โ calls ask_human_feedback("Done. Next?")
โ
[Queue has tasks?] โ YES โ returns next task โ Agent continues
โ NO
[Waits for human input via browser UI]
โ
Human responds โ Agent receives โ works โ calls ask_human_feedback again
โ
... loop continues until user indicates they are done ...
Security
FEEDBACK_TOKEN when deploying on shared or public networks to restrict access0.0.0.0 by default for convenience; restrict network access at the OS or firewall level if neededfeedback-history.json) is stored locally in the skill directory; review and rotate if it contains sensitive informationTips
โก When to Use
โ๏ธ Configuration
npm install && npm run build
MCP configuration:
{
"command": "node",
"args": ["build/index.js"],
"cwd": "/path/to/skill-feedback-collector"
}
Browser UI: http://
| Env Variable | Default | Description |
|---|---|---|
| FEEDBACK_PORT | 18061 | HTTP and WebSocket port |
| FEEDBACK_TOKEN | (empty) | Optional access token for the UI |