gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--mod...
Quality score
This tab explains the quality score through structured review blocks instead of collapsing everything into one number.
Most of the install and source context is visible, but a reviewer should still inspect the repository directly.
The description states what the skill does and includes a usage example, but the trigger context is somewhat generic and could benefit from more specific 'Use when' scenarios.
Instructions are clear, actionable, and well-structured, providing detailed steps for each phase of the process, including error handling and environment checks.
Scored by deterministic linter
The skill demonstrates domain-specific knowledge with detailed API usage and error handling, but lacks deeper insights into edge cases or real-world examples.
Structural Checks
Valid YAML frontmatter found
Frontmatter has name field
Frontmatter has description field
Content length: 34096 chars
Name format is valid
Description: 340 chars
Review checklist
Primary SKILL.md entrypoint is linked.
Install guidance is visible before download.
Repository context is attached to the listing.
Design Pattern
Design Pattern
tool-wrapper
Execution Contract
/learn @openclaw/gh-issues
Source Visibility
The catalog points directly to skills/gh-issues/SKILL.md so reviewers can inspect the live skill entrypoint instead of a generic readme.
Reviewed on Mar 28, 2026 · How scoring works