issue-driven-skill-selector

Collects GitHub issues, validates links, and scores fixes by impact, solvability, cost, and risk.

3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Dalomeve/bot-output --skill issue-driven-skill-selector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-driven-skill-selector
Source: https://github.com/Dalomeve/bot-output/tree/main/skills/issue-driven-skill-selector
Command: npx skills add https://github.com/Dalomeve/bot-output --skill issue-driven-skill-selector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Select high-value fixes from real community problems. Use link-proof validation to rank and decide whether to ship a skill fix, a core code fix, or a hybrid fix.

Core Features & Use Cases

  • Collects candidates from GitHub issues, discussions, and public threads to surface user pains
  • Enforces a Link Proof Gate to ensure all URLs are valid before scoring
  • Scores candidates on impact, solvability, cost, and risk to guide routing decisions (skill-first, core-first, hybrid)

Quick Start

Run an issue-gathering pass on your repositories and review the generated CANDIDATE_TABLE and TOP3_DECISIONS for initial recommendations.

Frequently Asked Questions about issue-driven-skill-selector

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

FAQPage Schema
How do I prioritize GitHub issues for backlog generation using evidence-based scoring?

Prioritize GitHub issues by collecting candidates from public threads and scoring them on impact, solvability, cost, and risk. This generates a structured CANDIDATE_TABLE to guide your backlog decisions using real community evidence.

What is the best way to decide between a skill-layer mitigation, core-engine patch, or hybrid fix?

Decide between skill-layer, core-engine, or hybrid fixes by applying scoring criteria to validated GitHub issues. The tool outputs TOP3_DECISIONS blocks that route your fix strategy based on impact, solvability, and risk metrics.

How does link validation work when surfacing user pains from GitHub issues?

Link validation works through a Link Proof Gate that ensures all URLs within GitHub issues and discussions are valid before scoring. This prevents broken references from influencing your candidate prioritization and routing decisions.

Can I use this issue-driven approach for software projects outside of core-engine patches?

You can use this issue-driven approach for software projects requiring backlog generation, skill-layer mitigations, core-engine patches, or hybrid fixes. It applies evidence-based prioritization across any project with public GitHub issue tracking.

How do I start an issue-gathering pass to review generated candidate tables and top 3 decisions?

Start an issue-gathering pass by running the tool against your repositories to collect candidates. It automatically validates links, scores issues, and outputs structured CANDIDATE_TABLE and TOP3_DECISIONS blocks for your initial recommendations.