Add extensive label management capabilities to the github-issues skill

[alx-so]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the main branch for this pull request.

---

Description

Add label management capabilities to the github-issues skill, including instructions for performing full CRUD operations on issue labels.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• Other (please specify):

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[github-actions]

🔒 PR Risk Scan Results

Scanned 2 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	0
ℹ️ Info	0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🔍 Vally Lint Results

✅ All checks passed

Scope	Checked
Skills	1
Agents	0
Total	1

Severity	Count
❌ Errors	0
⚠️ Warnings	0
ℹ️ Advisories	0

Summary

Level	Finding
ℹ️	✅ github-issues (2/2 checks passed)
ℹ️	✓ [spec-compliance] All 1 skill(s) are spec-compliant.
ℹ️	✓ spec-compliance: All spec checks passed.
ℹ️	✓ [valid-refs] All file references across 1 skill(s) are valid.
ℹ️	✓ valid-refs: All file references resolve to existing files within the skill directory.
ℹ️	1 skill(s) linted, 1 passed

Full linter output

### Linting skills/github-issues
✅ github-issues (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

[Copilot]

🟢 Approval recommended

It is a documentation-only addition whose commands are technically accurate, consistent with existing skill conventions, and correctly reflected in the regenerated README.

Pull request overview

This PR extends the existing github-issues skill with repository label management guidance. It adds a new reference document covering full CRUD operations on labels (list, create, rename/recolor, delete, clone) plus applying/removing/replacing labels on issues, and wires that reference into the skill's capability table and trigger description. The regenerated docs/README.skills.md keeps the marketplace README in sync. This is a documentation-only enhancement to an existing skill.

Changes:

• Added references/labels.md documenting label discovery and CRUD via the gh CLI and gh api, including default labels and usage rules.
• Updated SKILL.md description and Extended Capabilities table to surface the new label workflows and triggers.
• Regenerated docs/README.skills.md to reflect the updated description and reference file list.

File summaries

File	Description
skills/github-issues/references/labels.md	New reference with gh-based label management commands, default labels, and usage rules.
skills/github-issues/SKILL.md	Expanded description/triggers and added a Labels row to the capability table.
docs/README.skills.md	Regenerated skill entry with updated description and references/labels.md in the reference list.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 0
• Review effort level: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[allcontributors]

@alx-so

I couldn't determine any contributions to add, did you specify any contributions?
Please make sure to use valid contribution names.

[alx-so]

@all-contributors add @alx-so for skills

[allcontributors]

@alx-so

I couldn't determine any contributions to add, did you specify any contributions?
Please make sure to use valid contribution names.

[alx-so]

@all-contributors add @alx-so for doc

[allcontributors]

@alx-so

I've put up a pull request to add @alx-so! 🎉