File generic plugin feedback as GitHub issues labeled plugin-feedback.
npx skills add https://github.com/JSai23/claude-tooling --skill improve-jsai23
Please help me install this Agent Skill. Skill: improve Source: https://github.com/JSai23/claude-tooling/tree/main/plugins/util/skills/improve Command: npx skills add https://github.com/JSai23/claude-tooling --skill improve-jsai23
This Skill captures generic plugin feedback after any session where the tooling fell short—such as wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps—and files it as a GitHub issue labeled plugin-feedback for cross-project improvements. It is explicitly designed for generic plugin improvements that would help ANY project, not repo-specific config.
Provide a session summary describing what went wrong and what should improve, and the skill will file a plugin-feedback GitHub issue.
High-intent search queries and answers about installing and using this skill.
To capture generic plugin feedback as a GitHub issue, provide a session summary describing the tooling friction or coverage gaps. The feedback is structured into an actionable issue and filed in the JSai23/claude-tooling repo labeled plugin-feedback for centralized triage.
You should file generic plugin feedback that applies to ANY project, such as wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps. Avoid submitting repo-specific configuration issues to maintain centralized cross-project improvement tracking.
Create a GitHub issue from a session by providing a summary of what went wrong and what should improve. The tool distills these friction points into clear, reproducible issues and auto-files them in claude-tooling with the plugin-feedback label.
No, you cannot use this to report repo-specific plugin configuration issues. It is explicitly designed for generic plugin improvements that would help any project, filtering out repo-specific configs to ensure only broad tooling feedback is tracked.
You should submit plugin feedback to the claude-tooling repository after sessions where you observe generic tooling friction or coverage gaps across plugins. This ensures non-repo-specific improvements are captured and filed with the plugin-feedback label for tracking.
tomzxAudit an existing solutions survey across five evaluation categories.
erclxClassify open GitHub feedback issues into direct fixes, plan-worthy features, or clarification requests.
agol586Convert markdown task lists into dependency-ordered GitHub issues.
SvendsysCreate GitHub issues from aligned features using predefined templates.
