SKILLEMALL.ai
RU Sign in

AC github-issue-resolver

Autonomous GitHub Issue Resolver Agent with guardrails. Use when the user wants to discover, analyze, and fix open issues in GitHub repositories. Triggers on requests like "fix GitHub issues", "resolve issues in repo", "work on GitHub bugs", or when the user provides a GitHub repository URL and asks for issue resolution. Supports the full workflow from issue discovery to PR submission with safety guardrails preventing scope creep, unauthorized access, and dangerous operations.

modbender/skill-library-mcp Agent Skills author: modbender MIT 11 files body ≈ 1 497 tokens Open the sourcegithub.com↗ analyzed 36 h ago

Autonomous GitHub Issue Resolver Agent with guardrails.

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureGitHubSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
96
Run on models
none yet
Process rating
C
57/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 57/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 10 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (web, python) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 40 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1497 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 3 example trigger phrases
    • +3Description length 481: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 40 items
    • +4Has examples (13 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)
    • +3All 7 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.