Loading...
Loading...
Found 163 Skills
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
Writing and maintaining GitHub issues for the tldraw repository. Use when creating new issues, editing issue titles/bodies, triaging issues, or cleaning up issue metadata (types, labels).
This skill should be used when parallelizing multi-issue sprints using git worktrees and parallel Claude agents. Use when tackling multiple GitHub issues simultaneously, when the user mentions "blitz", "parallel sprint", "worktree workflow", or when handling 3+ independent issues that could be worked on concurrently. Orchestrates the full workflow from issue triage through parallel agent delegation to sequential merge.
Prepare local GitHub issue branches from the repository default branch using GitHub-style issue branch names. Use when starting issue-linked work, when the user says new branch for an issue, or when an agent must move onto the correct issue branch before implementation.
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
Run a retrospective after generating a CLI. Identifies systemic improvements to the Printing Press — templates, Go binary, skill instructions, catalog — so the next CLI comes out better. Creates a GitHub issue with actionable findings when there are Printing Press fixes to make. Use after any /printing-press run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings".
Interactive QA session where users report bugs or issues through conversation, and the agent creates GitHub issues. Explore the codebase in the background to obtain context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.
Manage GitHub issues locally as Markdown files. Use for triaging, searching, editing, and creating issues without leaving your editor or terminal.
Submit GitHub issues, feature requests, bug reports, product suggestions, and feedback to the ZenMux repository (ZenMux/zenmux-doc). Use this skill whenever the user wants to: report a bug, request a feature, suggest a product improvement, give feedback, request support for a new model or provider, report a documentation issue, or share their experience. Trigger on phrases like: "submit issue", "file a bug", "feature request", "report a problem", "I have an idea", "提交issue", "提反馈", "功能建议", "报告bug", "产品建议", "提个需求", "新增模型", "新增供应商", "文档问题", "我想提个建议", "提交建议". If the user is describing a ZenMux problem or product idea and would benefit from submitting it formally, proactively offer to help them create an issue.
Use when a GitHub issue needs triage — typically one carrying status/needs-triage label, a freshly opened issue without type/priority labels, or when the user says "triage
Triages GitHub issues by routing to oncall teams, applying labels, and closing questions. Use when processing new PyTorch issues or when asked to triage an issue.