How do I install the Issue Maker skill?

Run npx skillmds@latest add majiayu000/issue-maker in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Issue Maker safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Issue Maker?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Issue Maker free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Issue Maker?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Issue Maker by majiayu000 — Agent Skill

Name: Issue Maker
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Issue-Maker

Turn any user request into GitHub issues following team conventions.

Hard Rules

Repo: pollinations/pollinations
Assignee: Assign to appropriate team member based on domain expertise
No local side-effects (no file creation/modification)

Workflow

1. Research First

Before creating any issues:

# Check @eulervoid's PRs for style inspiration (concise, bullet-point format)
gh search prs --repo pollinations/pollinations --author eulervoid --limit 5

# Search existing issues for patterns
gh search issues --repo pollinations/pollinations "KEYWORD" --limit 5

2. Plan

List all planned issues:

One sentence description per issue
Identify assignee and labels
Note related PRs or issues

3. Create

gh issue create --repo pollinations/pollinations \
  --title "EMOJI Short clear title" \
  --body "- Bullet point 1
- Bullet point 2
- Bullet point 3" \
  --assignee HANDLE \
  --label "LABEL"

4. Output

Provide Discord-compatible summary:

Bold titles with issue numbers
Plain URLs on separate lines (Discord auto-embeds)
Group by category

Team Handles

Name	GitHub	Domain
Thomas	@voodoohop	General, Models, Infra
Joshua	@eulervoid	Pollen, Backend, Auth
Elliot	@elliotetag	Community, Newsletter, UI

Common Labels

Label	Use Case
`TRACKING`	Meta/planning issues that track multiple sub-tasks
`NEWS`	Community announcements and updates
`ext-issue`	External user requests (tier upgrades, etc.)
`app:review`	New project submission (under review)
`app:info-needed`	Submission awaiting user response
`app:approved`	Project approved and merged
`app:denied`	Submission rejected

Issue Templates

Standard Issue (max 3 bullets)

-   Adds X to Y
-   Fix Z by doing W
-   Related: #1234

Tracking Issue (more detailed)

## Overview

Brief description

## Tasks

-   [ ] Task 1
-   [ ] Task 2
-   [ ] Task 3

## Related

-   #issue1
-   #issue2

Tier Upgrade Request

-   Upgrade @USERNAME to TIER tier
-   Qualification: [reason]
-   Related: #original_request_issue

Style Guide

Short, sharp, no fluff
Smart emojis (not overdone)
Bullet points over paragraphs
Reference @eulervoid's style: repo:pollinations/pollinations author:eulervoid

Example Commands

Create simple issue:

gh issue create --repo pollinations/pollinations \
  --title "🔧 Fix caching header for image service" \
  --body "- Update cache-control header
- Add proper ETag support
- Related: #4100" \
  --assignee voodoohop

Create tracking issue:

gh issue create --repo pollinations/pollinations \
  --title "📋 TRACKING: Q4 Model Updates" \
  --body "## Overview
Track all model-related updates for Q4

## Tasks
- [ ] Add Claude Sonnet 4.5
- [ ] Update pricing tiers
- [ ] Deprecate old models" \
  --label "TRACKING" \
  --assignee voodoohop

Comment on issue:

gh issue comment 1234 --repo pollinations/pollinations \
  --body "✅ Done! Merged in #5678"

---name: issue-makerdescription: Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.--- # Issue-Maker Turn any user request into GitHub issues following team conventions. --- ## Hard Rules 1. **Repo:** `pollinations/pollinations` 2. **Assignee:** Assign to appropriate team member based on domain expertise 3. **No local side-effects** (no file creation/modification) --- ## Workflow ### 1. Research First Before creating any issues: ```bash # Check @eulervoid's PRs for style inspiration (concise, bullet-point format) gh search prs --repo pollinations/pollinations --author eulervoid --limit 5 # Search existing issues for patterns gh search issues --repo pollinations/pollinations "KEYWORD" --limit 5 ``` ### 2. Plan List all planned issues: - One sentence description per issue - Identify assignee and labels - Note related PRs or issues ### 3. Create ```bash gh issue create --repo pollinations/pollinations \ --title "EMOJI Short clear title" \ --body "- Bullet point 1 - Bullet point 2 - Bullet point 3" \ --assignee HANDLE \ --label "LABEL" ``` ### 4. Output Provide Discord-compatible summary: - Bold titles with issue numbers - Plain URLs on separate lines (Discord auto-embeds) - Group by category --- ## Team Handles | Name | GitHub | Domain | | ------ | --------------- | ------------------------- | | Thomas | **@voodoohop** | General, Models, Infra | | Joshua | **@eulervoid** | Pollen, Backend, Auth | | Elliot | **@elliotetag** | Community, Newsletter, UI | --- ## Common Labels | Label | Use Case | | ----------------- | -------------------------------------------------- | | `TRACKING` | Meta/planning issues that track multiple sub-tasks | | `NEWS` | Community announcements and updates | | `ext-issue` | External user requests (tier upgrades, etc.) | | `app:review` | New project submission (under review) | | `app:info-needed` | Submission awaiting user response | | `app:approved` | Project approved and merged | | `app:denied` | Submission rejected | --- ## Issue Templates ### Standard Issue (max 3 bullets) ```markdown - Adds X to Y - Fix Z by doing W - Related: #1234 ``` ### Tracking Issue (more detailed) ```markdown ## Overview Brief description ## Tasks - [ ] Task 1 - [ ] Task 2 - [ ] Task 3 ## Related - #issue1 - #issue2 ``` ### Tier Upgrade Request ```markdown - Upgrade @USERNAME to TIER tier - Qualification: [reason] - Related: #original_request_issue ``` --- ## Style Guide - **Short, sharp, no fluff** - Smart emojis (not overdone) - Bullet points over paragraphs - Reference @eulervoid's style: `repo:pollinations/pollinations author:eulervoid` --- ## Example Commands **Create simple issue:** ```bash gh issue create --repo pollinations/pollinations \ --title "🔧 Fix caching header for image service" \ --body "- Update cache-control header - Add proper ETag support - Related: #4100" \ --assignee voodoohop ``` **Create tracking issue:** ```bash gh issue create --repo pollinations/pollinations \ --title "📋 TRACKING: Q4 Model Updates" \ --body "## Overview Track all model-related updates for Q4 ## Tasks - [ ] Add Claude Sonnet 4.5 - [ ] Update pricing tiers - [ ] Deprecate old models" \ --label "TRACKING" \ --assignee voodoohop ``` **Comment on issue:** ```bash gh issue comment 1234 --repo pollinations/pollinations \ --body "✅ Done! Merged in #5678" ```

Frequently asked questions

Issue Maker