Automated summary
Creates well-structured GitHub issues for the MCPSpy project through the gh command-line tool, following a feat/chore/fix naming convention.
Strengths
- Automatically applies the project's feat(component)/fix(component)/chore title convention
- Keeps issue bodies at an actionable POC level instead of exhaustive specification
- Uses --body-file for long descriptions, avoiding shell escaping problems
- Restricts its tool scope to gh issue, limiting unintended actions
Limitations
- Tightly coupled to the MCPSpy project and its component names (ebpf, mcp, library-manager, etc.)
- Does not cover editing, triaging, or closing existing issues
- Guidelines deliberately exclude test plans and acceptance criteria, which may be too thin for critical work
Use it when you need to quickly file a well-titled GitHub issue for a feature, bug, or technical debt item in MCPSpy.
Avoid it for tickets that require detailed acceptance criteria, test plans, or a full technical specification.
Security analysis
SafeThe skill only permits Bash commands restricted to 'gh issue:*' subcommands for creating GitHub issues. It does not instruct destructive actions, exfiltration, obfuscation, or disabling safety. Writing issue bodies to temporary files and using --body-file is a legitimate pattern and remains within the allowed tool scope.
No concerns found
How this analysis is madeExamples
Create a GitHub issue for MCPSpy proposing support for container runtime detection in the library manager.Open an issue reporting that the ebpf module fails to load on older kernel versions.File a chore issue for updating MCPSpy dependencies to the latest versions.name: github-issue-creator description: "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." allowed-tools:
- Bash(gh issue:*)
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 detectionchore: update dependencies to latest versionsfix(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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/github-issue-creator-mm5t89pe/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/github-issue-creator-mm5t89pe' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/github-issue-creator-mm5t89pe/download' --output '.skill-downloads/github-issue-creator-mm5t89pe/SKILL.md.part' && mv '.skill-downloads/github-issue-creator-mm5t89pe/SKILL.md.part' '.skill-downloads/github-issue-creator-mm5t89pe/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/github-issue-creator-mm5t89pe/SKILL.md' && test -s '.skill-downloads/github-issue-creator-mm5t89pe/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/github-issue-creator' && cp -R '.skill-downloads/github-issue-creator-mm5t89pe' '.claude/skills/github-issue-creator'Cursor
test -f '.skill-downloads/github-issue-creator-mm5t89pe/SKILL.md' && test -s '.skill-downloads/github-issue-creator-mm5t89pe/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/github-issue-creator' && cp -R '.skill-downloads/github-issue-creator-mm5t89pe' '.cursor/skills/github-issue-creator'Codex
test -f '.skill-downloads/github-issue-creator-mm5t89pe/SKILL.md' && test -s '.skill-downloads/github-issue-creator-mm5t89pe/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/github-issue-creator' && cp -R '.skill-downloads/github-issue-creator-mm5t89pe' '.agents/skills/github-issue-creator'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/github-issue-creator-mm5t89pe'openskills read 'github-issue-creator-mm5t89pe'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/github-issue-creator-mm5t89pe/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.