smithery.ai

issue-maker

Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.

First seen Mar 26, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,741 B
  • docs SUMMARY.md 143 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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:

# 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 and support follow-ups
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

Account Support Request

-   Account support for @USERNAME
-   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"