agentleFS
Sign inStart free
Fu-JieFu-Jie/openwebui-extensions/.github/skills/gh-issue-scheduler/SKILL.md

gh-issue-scheduler

Skill326 starsChanged 8 months agoMITView on GitHub

Finds all open GitHub issues that haven't been replied to by the owner, summarizes them, and generates a solution plan. Use when the user wants to audit pending tasks or plan maintenance work.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Identify Unanswered Issues: Run the bundled script to fetch issues without owner replies.

    line 14
  2. Distinctive:

    When presenting the summary, use the following Markdown structure:

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Gh Issue Scheduler

Overview

The gh-issue-scheduler skill helps maintainers track community feedback by identifying unaddressed issues and drafting actionable technical plans to resolve them.

Workflow

  1. Identify Unanswered Issues: Run the bundled script to fetch issues without owner replies.
    • Command: bash scripts/find_unanswered.sh
  2. Analyze and Summarize: For each identified issue, summarize the core problem and the user's intent.
  3. Generate Solution Plans: Draft a technical "Action Plan" for each issue, including:
    • Root Cause Analysis (if possible)
    • Proposed Fix/Implementation
    • Verification Strategy
  4. Present to User: Display a structured report of all pending issues and their respective plans.

Tool Integration

Find Unanswered Issues

bash scripts/find_unanswered.sh

Report Format

When presenting the summary, use the following Markdown structure:

📋 Unanswered Issues Audit

Issue #[Number]: [Title]

  • Author: @username
  • Summary: Concise description of the problem.
  • Action Plan:
    1. Step 1 (e.g., Investigate file X)
    2. Step 2 (e.g., Apply fix Y)
    3. Verification (e.g., Run test Z)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free