issue-maker — Claude Code skill: file Pollinations GitHub issues
issue-maker — a skill for filing and updating GitHub issues in the Pollinations repo. It scans open and closed issues and PRs for duplicates first, then writes the task in the project's current format.
MIT 1 installs ★ 5,322 updated 2026-11-08
npx skills add pollinations/pollinations --skill issue-maker -a claude-codeWhat issue-maker does
The skill handles issues in pollinations/pollinations. It starts by reading open and closed issues and PRs on the same topic, including the last comments and why earlier work was closed, so you don't file a duplicate or reopen something stale. Then it drafts a short title with up to three concrete bullets, links related items, and switches to a checklist when the job has several steps.
Area, type and priority labels are off-limits: the project manager bot assigns those under operations/github/project-manager.md. Assignees come from your request; with no preference the skill follows the ownership table, where Thomas (voodoohop) covers general work, models and infrastructure, Joshua (eulervoid) covers Pollen, backend and auth, and Elliot (elliotetag) covers community, newsletter and UI. App submission states live in the root AGENTS.md.
The repo is hardcoded to pollinations/pollinations, so in another codebase the ownership table and the bot labels mean nothing. For issue-only work it leaves local files alone and returns the issue link plus a short summary, formatted for Discord if you ask.
What it helps with
- file an issue without duplicating closed work
- turn multi-step work into a checklist
- pick the assignee who owns the area
- keep area and priority labels with the bot
- get the issue link back with a summary
Example prompts for the agent
- Open an issue in
pollinations/pollinationsfor the broken mobile chat page, with repro steps in three bullets. - Check whether this task already exists as a closed issue or PR before you file it.
- Format the issue summary for Discord and send me the link.
How to install issue-maker
1Skills CLI (Vercel)
npx skills add pollinations/pollinations --skill issue-maker -a claude-code2Manually: put the files in place
~/.claude/skills/issue-maker/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/issue-maker/
1Skills CLI (Vercel)
npx skills add pollinations/pollinations --skill issue-maker -a codex2Manually: put the files in place
.agents/skills/issue-maker/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pollinations/pollinations --skill issue-maker -a cursor2Manually: put the files in place
.cursor/skills/issue-maker/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pollinations/pollinations .claude/skills/issue-maker2Manually: put the files in place
.github/skills/issue-maker/SKILL.md1Skills CLI (Vercel)
npx skills add pollinations/pollinations --skill issue-maker -a gemini-cli2Platform CLI
gemini skills install https://github.com/pollinations/pollinations --path .claude/skills/issue-makerManually: put the files in place
.devin/skills/issue-maker/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pollinations/pollinations --skill issue-maker -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about issue-maker
How do I install issue-maker in Claude Code?
Run npx skills add pollinations/pollinations --skill issue-maker -a claude-code. The skill lands in ~/.claude/skills/issue-maker/SKILL.md.
What does issue-maker do?
It creates and updates GitHub issues in the Pollinations repo, checking related issues and PRs first, then returning the issue link with a brief summary.
Which labels does issue-maker add?
None for area, type or priority. The project manager bot sets those following operations/github/project-manager.md.
Source text
SKILL.md · MIT
--- name: issue-maker description: Create or update Pollinations GitHub issues when asked to track work, using current repository conventions. --- # Issue Maker - Use `pollinations/pollinations`. Check related open and closed issues/PRs, including the latest discussion and close reason, before creating a duplicate or reviving obsolete work. - Describe the current problem or requested outcome with a short title and up to three concrete bullets. Link related work; use a checklist when an issue covers several steps. The project manager bot sets area, type and priority (`operations/infrastructure/project-manager/project-manager.md`); don't add labels for them. - Follow the user's assignee preferences. Otherwise use the team ownership table below, checking current repository context when uncertain. Root `AGENTS.md` defines app-submission states. - Return the issue link and a concise summary. Use Discord-compatible formatting when requested. - Do not create or modify local files for issue-only work. | Person | GitHub | Area | | --- | --- | --- | | Thomas | `voodoohop` | General, models, infrastructure | | Joshua | `eulervoid` | Pollen, backend, auth | | Elliot | `elliotetag` | Community, newsletter, UI |
© pollinations · MIT · pollinations/pollinations