load-issues — Claude Code skill: export open issues to markdown
The skill pulls every open issue from the current repository with gh and writes each one to its own markdown file. Handy when you want tasks outside GitHub.
npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a claude-codeWhat load-issues does
The skill walks through the open issues of the current repository and saves each one as a separate file. It first lists them with gh issue list --limit 100, then fetches details per number: title, body, state, dates, author, labels, assignees and URL. Everything lands in ./specs/issues/.
File names follow <number padded to 3 digits>-<kebab-case-title>.md, for example 007-make-code-review-trigger-on-sql-sh-changes.md. Each file holds the issue heading, a metadata block, the description, labels and assignees. When it finishes, the skill reports how many issues were loaded and which files it created.
You need an installed and authenticated gh CLI — without it there is no list and no details. The ./specs/issues directory is created if missing. The listing caps at one hundred issues per run, so in repositories with more open tasks some will be left out; worth checking whether the numbers you care about made it into the export.
What it helps with
- export open repository issues to markdown
- hand tasks to an agent without GitHub access
- collect labels and assignees per issue in one file
- keep a local copy of issues for text search
- prepare a task list for review in an editor
Example prompts for the agent
- load all open issues into ./specs/issues
- fetch the repository issues and save them as markdown
- show how many open issues were loaded and which files were created
How to install load-issues
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a claude-code2Manually: put the files in place
~/.claude/skills/load-issues/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/load-issues/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a codex2Manually: put the files in place
.agents/skills/load-issues/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a cursor2Manually: put the files in place
.cursor/skills/load-issues/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NeoLabHQ/context-engineering-kit load-issues2Manually: put the files in place
.github/skills/load-issues/SKILL.md1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a gemini-cli2Platform CLI
gemini skills install https://github.com/NeoLabHQ/context-engineering-kit --path skills/load-issuesManually: put the files in place
.devin/skills/load-issues/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -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 load-issues
How do I install load-issues in Claude?
Run npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a claude-code. The skill then lives at ~/.claude/skills/load-issues/SKILL.md.
What does load-issues do?
It pulls all open issues from the current repository via the gh CLI and saves each as a markdown file in ./specs/issues/ with metadata, description, labels and assignees.
What does the skill need to run?
An installed and authenticated gh CLI. The list comes from gh issue list --limit 100, so a single run exports at most one hundred issues.