How do I install the Github Issue Creator skill?

Run npx skillmds@latest add tomevault-io/github-issue-creator 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 Github Issue Creator safe to use?

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

Which AI agents work with Github Issue Creator?

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 Github Issue Creator free to use?

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

Who published Github Issue Creator?

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

Github Issue Creator by tomevault-io

Name: Github Issue Creator
Author: tomevault-io

Github Issue Creator

Creates well-structured GitHub issues for the MCPSpy project using the gh CLI tool. Use when asked to create issues, report bugs, or document features. Follows conventional naming with feat/chore/fix prefixes and maintains appropriate detail levels.

tomevault-io Updated Sep 17, 2026

File contents

GitHub Issue Creator Skill

Automates the creation of well-structured GitHub issues for the MCPSpy project.

Tools and Usage

Use the gh issue CLI tool to create GitHub issues. If the issue body is rather long, write it to a temporary markdown file and use the gh issue create --body-file <file> option.

Issue Naming Convention

Use standard prefixes: feat(component):, chore:, fix(component):
Component examples: library-manager, ebpf, mcp, http, output
Brackets are optional but recommended for clarity
Keep titles concise and descriptive

Examples

feat(library-manager): add support for container runtime detection
chore: update dependencies to latest versions
fix(ebpf): handle kernel version compatibility issues

Issue Content Guidelines

What to Include

High-level design notes - focus on the "what" and "why"
POC-level details - enough to get started, not exhaustive
Actionable scope - should be implementable by a developer familiar with the codebase

What NOT to Include

Detailed test plans
Exhaustive acceptance criteria
Deep technical specifications
Code examples (unless absolutely necessary for clarity)

When to Use This Skill

Creating new feature requests
Reporting bugs and issues
Documenting technical debt
Planning work items for the MCPSpy project

Source: alex-ilgayev/MCPSpy — distributed by TomeVault.

Frequently asked questions