MultiQC

This skill is designed for maintainers of the MultiQC project to streamline the influx of community-driven module requests. By integrating with GitHub, it automates the evaluation of incoming issues, ensuring that effort is focused on the most impactful tools. It calculates a priority score (0-100) based on weighted metrics including tool popularity, download statistics from PyPI and Bioconda, and community interest measured through reactions and discussion threads. This systematic approach reduces the manual workload of triaging, ensures consistent application of quality standards, and provides immediate, constructive feedback to contributors regarding their proposals.

The skill is highly modular, supporting single-issue analysis on demand via command triggers, as well as comprehensive weekly batch triage operations. It generates data-driven recommendations, assigns appropriate priority labels, and updates project board columns to keep the development roadmap transparent and organized. It relies on internal scripts for fetching real-time metrics and follows established templates to communicate technical requirements and missing information back to the community.

• Automated triage of issues labeled 'module: new' to ensure timely responses to contributors.

• Data-driven scoring rubric covering tool popularity (GitHub stars/forks), download metrics (PyPI/Conda), and community engagement.

• Standardized feedback templates to request necessary artifacts like example log files or tool documentation.

• Multi-mode execution: analyze-single for targeted reviews, triage-all for bulk processing, and dry-run for debugging workflows.

• Integration with GitHub project boards to automate status transitions and issue categorization based on calculated priority bands.

• Use @claude analyze-module in issue comments to trigger an immediate assessment of a specific feature request.

• Relies on GitHub CLI (gh) and secure API calls to ensure accurate metric collection while respecting rate limits.

• Requires valid repository access permissions to modify labels, comments, and project board states.

• Best suited for bioinformatics software maintainers managing open-source contributions and feature requests at scale.

• Expected inputs include a valid GitHub issue, while expected outputs include a detailed comment summarizing the score, reasoning, and next steps for the contributor.