yunxiao-bug-stats

Analyze cloud project online fault work items and report counts by assignee.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/weiran-tech/agent-skills --skill yunxiao-bug-stats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yunxiao-bug-stats
Source: https://github.com/weiran-tech/agent-skills/tree/main/skills/yunxiao-bug-stats
Command: npx skills add https://github.com/weiran-tech/agent-skills --skill yunxiao-bug-stats

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill retrieves and summarizes cloud project online fault work items to provide quick visibility into the current state and month-specific activity.

Core Features & Use Cases

  • Unresolved count: counts all online fault items not yet closed.
  • Monthly creation: counts items created in the target year-month.
  • Monthly closures: counts items closed in the target year-month.
  • Grouped reporting: outputs per-assignee groupings with emoji visualizations for priority, severity, and status.
  • Use case: monthly sprint or operations review to gauge quality and workload across multiple projects.

Quick Start

Invoke this skill with a JSON export to generate the current month's online fault statistics for the selected organization and space.

Frequently Asked Questions about yunxiao-bug-stats

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

FAQPage Schema
How do I generate a monthly online fault statistics report for cloud projects?

To generate an online fault statistics report, you invoke the skill with MCP-like JSON input specifying your organization and space, which then outputs a Markdown report of unresolved, created, and closed items.

Can I group unresolved online bug work items by assignee in a Markdown report?

Yes, online bug work items can be grouped by assignee in the Markdown report, which uses emoji-based visualizations to display priority, severity, and status for each assigned user.

What is the best way to track monthly online fault closures and creations across project spaces?

The best way to track monthly online fault closures and creations is to input a target year-month and organization space, which retrieves counts of items created and closed in that specific month.

Does this bug tracking analytics tool require external dependencies to process JSON exports?

No external dependencies are required to process JSON exports for bug tracking analytics, as the skill operates independently using internal scripts to read MCP-like JSON input and identify online fault types.

How do online fault metrics identify which work items are unresolved?

Online fault metrics identify unresolved items by reading the JSON input to exclude work items that match defined closed statuses, counting all remaining online fault work items as unresolved.

What visualizations are included in the per-assignee fault workload grouping?

The per-assignee fault workload grouping includes emoji-based visualizations in the Markdown report output, representing the priority, severity, and status of each online fault work item.