report-skill-issue

Identify failing skills and generate standardized upstream issue reports.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/nq-rdl/agent-extensions --skill report-skill-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-skill-issue
Source: https://github.com/nq-rdl/agent-extensions/tree/main/skills/report-skill-issue
Command: npx skills add https://github.com/nq-rdl/agent-extensions --skill report-skill-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps users report issues with skills to their upstream repositories when a skill fails, behaves unexpectedly, or produces incorrect output.

Core Features & Use Cases

  • Guides you through identifying the failing skill and locating its upstream repository.
  • Checks for existing issues to avoid duplicates, gathers context, and formats a standardized report.
  • Provides a ready-to-file issue body and steps to file it manually if automated submission isn't possible.

Quick Start

Run this skill when a skill fails to guide you through reporting the issue to its upstream repository.

Frequently Asked Questions about report-skill-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I report a failing skill to its upstream GitHub repository?

To report a failing skill to its upstream GitHub repository, this skill identifies the failing component, checks for existing duplicate issues, gathers context, and generates a standardized ready-to-file draft.

What is the best way to automate issue reporting for skills that fail silently?

Automating issue reporting for skills that fail silently involves identifying the unexpected behavior, locating the upstream repository, and formatting a standardized report draft to file manually if automated submission is unavailable.

Can I automatically submit GitHub issues for skills that produce errors?

You cannot always automatically submit GitHub issues for skills that produce errors; this skill generates a ready-to-file issue body and provides manual steps for the upstream repository's issue tracker when automated submission fails.

How do I check for duplicate upstream issues before reporting a skill failure?

To check for duplicate upstream issues before reporting a skill failure, this skill verifies the upstream repository's issue tracker to avoid duplicates and ensures the issue body follows a standardized template.

What should I do when a skill behaves unexpectedly and I need to file an upstream issue?

When a skill behaves unexpectedly and you need to file an upstream issue, this skill guides you through locating the upstream repository, gathering context, and formatting a standardized report.