label-issue Skill
Classify and label GitHub issues based on repository-specific labeling instructions. Use when (1) auto-labeling new issues, (2) classifying issue types (bug, feature, etc.), (3) adding priority or area labels, (4) applying consistent labeling rules. Triggers on requests like "label issue", "classify issue", "what label Published by microsoft in vscode-java-pack.
Decision snapshot
Is this a fit?
Developers using vscode-java-pack, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · NOASSERTION license
No specific cautions were detected. Review the source and requested permissions before installing.
What is label-issue Skill?
Classify and label GitHub issues based on repository-specific labeling instructions. Use when (1) auto-labeling new issues, (2) classifying issue types (bug, feature, etc.), (3) adding priority or area labels, (4) applying consistent labeling rules. Triggers on requests like "label issue", "classify issue", "what label Published by microsoft in vscode-java-pack. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using vscode-java-pack
Declared skill metadata
- Source file: .github/skills/label-issue/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use label-issue Skill
- Use it for developers using vscode-java-pack.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-java-pack
- Skill file: .github/skills/label-issue/SKILL.md
What it does
Classify and label GitHub issues based on repository-specific labeling instructions. Use when (1) auto-labeling new issues, (2) classifying issue types (bug, feature, etc.), (3) adding priority or area labels, (4) applying consistent labeling rules. Triggers on requests like "label issue", "classify issue", "what label
Skill instructions
Label Issue Skill Automatically classify and label GitHub issues based on repository-specific labeling instructions. Overview This skill analyzes GitHub issue content (title, body, comments) and applies appropriate labels based on labeling rules defined in the target repository's .github/llms.md file. Workflow 1. Input: Receive issue URL or issue number with repository (owner/repo) 2. Fetch labeling instructions: Read .github/llms.md from the checked-out repository before deciding labels 3. Fetch issue: Get issue details (title, body, existing labels) 4. Analyze issue: Match issue content against labeling rules 5. Determine labels: Select appropriate labels based on: - Keyword matching - Issue type detection (bug, feature, question, etc.) - Priority assessment - Area/component identification 6. Apply labels: Use Python script to add labels via GitHub API 7. Report: Confirm labels applied with reasoning Reading Labeling Instructions Fetch .github/llms.md from the checked-out target repo
Verified compatibility and discovery
Frequently asked questions
What is label-issue?
label-issue is a open-source AI agent skill with Copy skill directory. Classify and label GitHub issues based on repository-specific labeling instructions. Use when (1) auto-labeling new issues, (2) classifying issue types (bug, feature, etc.), (3) adding priority or area.
Who is label-issue best for?
label-issue is best for reusing agent instructions, scripts, and references.
How do I install label-issue?
Install or run label-issue using Copy skill directory. Check label-issue for the latest setup command.
Is label-issue actively maintained?
label-issue may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
