openclaw - ✅(Solved) Fix gh-issues skill: Frontmatter validation failure + excessive size [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#54311Fetched 2026-04-08 01:29:12
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #54360: fix(skills): remove unsupported gh-issues frontmatter

Description (problem / solution / changelog)

Summary

  • remove unsupported user-invocable from gh-issues frontmatter
  • restore quick validation for the bundled skill without changing its runtime body

Refs #54311

Changed files

  • skills/gh-issues/SKILL.md (modified, +0/-1)

Code Example

Unexpected key(s) in SKILL.md frontmatter: user-invocable

---

description: "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]..."

---

description: "Orchestrate GitHub issue resolution via parallel sub-agents. Use when user asks to 'fix these GitHub issues', 'auto-fix bugs in repo', 'process GitHub issues', or 'address PR reviews'. Handles issue fetching, branch creation, PR submission, and review comment resolution."
RAW_BUFFERClick to expand / collapse

gh-issues Skill Quality Issues

The bundled gh-issues skill has several compliance issues:

1. Unexpected Frontmatter Property

The skill includes user-invocable: true in the frontmatter, which is not in the allowed properties list:

  • Allowed: name, description, license, allowed-tools, metadata, compatibility, homepage
  • Found: user-invocable: true

This causes validation failure:

Unexpected key(s) in SKILL.md frontmatter: user-invocable

2. Excessive Size

The SKILL.md file is 30,762 bytes (~30 KB), which is:

  • 2x the recommended maximum (15 KB)
  • Far beyond the 5K word guideline from Anthropic patterns

The skill contains extremely detailed orchestration logic, sub-agent prompt templates, and extensive workflow descriptions that bloat the context window unnecessarily.

3. Description Quality

While the description is functional, it's formatted as a command-line usage string rather than a natural-language description with triggers:

description: "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]..."

Should be more like:

description: "Orchestrate GitHub issue resolution via parallel sub-agents. Use when user asks to 'fix these GitHub issues', 'auto-fix bugs in repo', 'process GitHub issues', or 'address PR reviews'. Handles issue fetching, branch creation, PR submission, and review comment resolution."

Recommended Fixes

Immediate (FORGE-007)

  1. Remove user-invocable — This property is not part of the skill spec. If this is intended functionality, it should be in metadata instead.
  2. Validate compliance — Run validate_skill.py to ensure no other unexpected properties exist.

Future Refactor (FORGE-008)

  1. Reduce size to <15KB — Extract:

    • Detailed sub-agent prompt templates → references/sub-agent-prompts.md
    • Phase-by-phase orchestration logic → references/orchestration-phases.md
    • API call examples → references/github-api-calls.md
    • Keep only: overview, quick usage, key constraints, and references to detailed docs
  2. Improve description — Make it trigger-oriented and conversational, not CLI-style.

Impact

  • Validation failure prevents automated quality checks
  • Massive size increases token consumption for every agent that loads skill metadata
  • Poor description may reduce trigger match quality

Priority

High — This is a bundled skill that serves as an example for others. It should exemplify best practices, not violate them.

extent analysis

Fix Plan

To address the compliance issues in the gh-issues skill, follow these steps:

  1. Remove user-invocable property:

    • Open the SKILL.md file.
    • Remove the line user-invocable: true from the frontmatter.
    • If this property is necessary, add it to the metadata section instead.
  2. Validate compliance:

    • Run validate_skill.py to check for any other unexpected properties.
  3. Reduce size to <15KB:

    • Extract detailed information into separate files:
      • references/sub-agent-prompts.md for sub-agent prompt templates.
      • references/orchestration-phases.md for phase-by-phase orchestration logic.
      • references/github-api-calls.md for API call examples.
    • Keep only essential information in SKILL.md, such as overview, quick usage, key constraints, and references to detailed documentation.
  4. Improve description:

    • Update the description field in SKILL.md to a trigger-oriented and conversational format, similar to:

description: "Orchestrate GitHub issue resolution via parallel sub-agents. Use when user asks to 'fix these GitHub issues', 'auto-fix bugs in repo', 'process GitHub issues', or 'address PR reviews'. Handles issue fetching, branch creation, PR submission, and review comment resolution."


### Example Code Changes
Before:
```yaml
---
name: gh-issues
description: "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]..."
user-invocable: true
---

After:

---
name: gh-issues
description: "Orchestrate GitHub issue resolution via parallel sub-agents. Use when user asks to 'fix these GitHub issues', 'auto-fix bugs in repo', 'process GitHub issues', or 'address PR reviews'. Handles issue fetching, branch creation, PR submission, and review comment resolution."
metadata:
  user-invocable: true
---

Verification

  • Run validate_skill.py to ensure no validation errors occur.
  • Verify the size of SKILL.md is less than 15KB.
  • Test the skill to ensure it functions as expected with the updated description and removed user-invocable property.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix gh-issues skill: Frontmatter validation failure + excessive size [1 pull requests, 1 participants]