agent-inbox

Centralizes user feedback and bug reports with statuses like acknowledged and dismissed.

20|8|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/1uc4sm4theus/master-zap --skill agent-inbox-1uc4sm4theus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-inbox
Source: https://github.com/1uc4sm4theus/master-zap/tree/main/Master-Zap/.local/skills/agent-inbox
Command: npx skills add https://github.com/1uc4sm4theus/master-zap --skill agent-inbox-1uc4sm4theus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of managing fragmented user feedback, bug reports, and feature requests by centralizing them into a structured, actionable inbox.

Core Features & Use Cases

  • Inbox Management: List, filter, and track the status of incoming user feedback items.
  • Status Tracking: Update item statuses from pending to acknowledged, implemented, or dismissed to maintain a clear development roadmap.
  • Use Case: When a user reports a bug, you can use this skill to list all pending bug reports, review the details, and mark the specific item as acknowledged once you have started working on the fix.

Quick Start

Use the agent-inbox skill to list all pending bug reports and update the status of the first item to acknowledged.

Frequently Asked Questions about agent-inbox

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

FAQPage Schema
What is the best way to centralize fragmented user feedback and bug reports?

Centralizing fragmented user feedback requires a structured inbox interface that aggregates bug reports and feature requests for programmatic tracking. This enables systematic categorization, filtering, and lifecycle management of incoming project items.

How do I track the lifecycle of a bug report from pending to acknowledged?

To track a bug report lifecycle, list pending items from your inbox and update their status to acknowledged, implemented, or dismissed. This maintains a clear development roadmap and reflects current resolution states.

Can I programmatically filter user feedback by specific topics and resolution states?

Yes, you can programmatically filter user feedback by specific topics and resolution states. The centralized inbox interface facilitates filtering incoming project items to isolate relevant bug reports and feature requests.

How do I manage a development roadmap using an inbox workflow for project items?

Managing a development roadmap through an inbox workflow involves listing incoming project items, reviewing details, and updating statuses from pending to acknowledged or dismissed to track development tasks derived from user-submitted content.

Does this bug tracking approach work without external project management dependencies?

Yes, this bug tracking approach functions without external project management dependencies. It operates independently using a centralized inbox interface to manage user feedback lifecycles and categorize incoming project items.

When should I dismiss user-submitted feedback instead of marking it as implemented?

You should dismiss user-submitted feedback when the bug report or feature request is out of scope or invalid. Updating the status to dismissed maintains a clear development roadmap by removing non-actionable items from pending queues.