New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

GitHub Issues

by Cybereason-Public in Cybereason-Public/owLSM

Manage GitHub issues - create, edit, close, comment, assign, and delegate to Copilot.

GPL-2.0Auto-check passedDevelopment

Install GitHub Issues

skills CLI
$ npx skills add Cybereason-Public/owLSM --skill github-issues -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Cybereason-Public/owLSM github-issues --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Cybereason-Public/owLSM.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/github-issues .claude/skills/github-issues && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
github-issues
GitHub stars
280
Token cost
~1.8k tokens
SKILL.md length
430 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
GPL-2.0

At a glance

Manage GitHub issues - create, edit, close, comment, assign, and delegate to Copilot.

  • Works in 10 steps: List Issues → Create Issue → Read Issue Details → …
  • Tasks that involve Issue triage
  • SKILL.md covers Prerequisites, Default Repository, Available Operations and Workflow Examples, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

GitHub Issues is an agent skill from Cybereason-Public/owLSM. Manage GitHub issues - create, edit, close, comment, assign, and delegate to Copilot. Uses GitHub MCP.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Issue triage. It works with GitHub, Model Context Protocol and Linux. The repository describes itself as: Sigma Rules Engine inside the Linux Kernel using eBPF. Focusing on prevention capabilities. The licence is GPL-2.0.

When your agent uses it

  • Tasks that involve Issue triage

Example prompts

  • “/github-issues”

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. List Issues
  2. Create Issue
  3. Read Issue Details
  4. Update Issue
  5. Close Issue
  6. Add Comment
  7. Search Issues
  8. Assign to Copilot
  9. Get Issue Comments
  10. Manage Labels

What it can do on your machine

Read from SKILL.md and the folder at commit 8e541af. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Issues loads about 1.8k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 430 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Cybereason-Public/owLSM at commit 8e541af, republished under its GPL-2.0 licence (© Cybereason-Public). 430 words, ~1,788 tokens.

Download SKILL.mdSave it as .claude/skills/github-issues/SKILL.md (or your agent's skills folder).
name
github-issues
description
Manage GitHub issues - create, edit, close, comment, assign, and delegate to Copilot. Uses GitHub MCP.

GitHub Issues Management

You are a GitHub issue management assistant using the GitHub MCP server tools.

Prerequisites

  • GitHub MCP server must be configured in Cursor
  • Valid GitHub Personal Access Token with Issues: Read and write permission
  • Access to the target repository

Default Repository

Unless specified otherwise, operate on:

  • Owner: cybereason-labs
  • Repo: owLSM_deprecated

User can specify a different repo: "create issue in owner/repo"

Available Operations

1. List Issues

Triggers: "show issues", "list issues", "what issues are open"

Use: mcp_GitHub_list_issues
Parameters:
  - owner: repository owner
  - repo: repository name
  - state: OPEN | CLOSED (default: OPEN)
  - labels: filter by labels (optional)
  - perPage: results per page (default: 10)

Example output format:

Found 5 open issues:

#42 - Fix memory leak in process cache
     Labels: bug, high-priority
     Assignee: @username
     Created: 2024-01-15

#38 - Add support for network monitoring
     Labels: enhancement
     Assignee: none
     Created: 2024-01-10
...
2. Create Issue

Triggers: "create issue", "new issue", "open issue for"

Use: mcp_GitHub_issue_write
Parameters:
  - method: "create"
  - owner: repository owner
  - repo: repository name
  - title: issue title (required)
  - body: issue description
  - labels: array of label names
  - assignees: array of usernames

When creating issues:

  1. Ask for title if not provided
  2. Generate a clear, descriptive body if not provided
  3. Suggest relevant labels based on content
  4. Confirm before creating
  5. Add context that I provide in the prompt. Things like code blocks, files, link, screenshots, etc'

Example:

User: "create issue for the TCP monitoring bug"

Agent response:
I'll create an issue for the TCP monitoring bug.

Title: TCP monitoring fails to capture outbound connections
Body: 
  ## Description
  TCP monitoring is not capturing outbound connections...
  
  ## Steps to Reproduce
  1. ...
  
Labels: bug
Assignee: (none)

Create this issue? [Provide details to modify or confirm]
3. Read Issue Details

Triggers: "show issue #X", "what's issue #X about", "details of #X"

Use: mcp_GitHub_issue_read
Parameters:
  - method: "get"
  - owner: repository owner
  - repo: repository name  
  - issue_number: the issue number
4. Update Issue

Triggers: "update issue", "edit issue", "change issue"

Use: mcp_GitHub_issue_write
Parameters:
  - method: "update"
  - owner: repository owner
  - repo: repository name
  - issue_number: issue to update
  - title: new title (optional)
  - body: new body (optional)
  - state: "open" | "closed"
  - state_reason: "completed" | "not_planned" | "duplicate"
  - labels: new labels array
  - assignees: new assignees array
5. Close Issue

Triggers: "close issue #X", "mark #X as done", "resolve #X"

Use: mcp_GitHub_issue_write
Parameters:
  - method: "update"
  - issue_number: X
  - state: "closed"
  - state_reason: "completed" (or "not_planned" if won't fix)

Always ask for close reason:

  • completed - Issue was fixed/resolved
  • not_planned - Won't fix / out of scope
  • duplicate - Duplicate of another issue (ask which one)
6. Add Comment

Triggers: "comment on #X", "add comment to issue", "reply to #X"

Use: mcp_GitHub_add_issue_comment
Parameters:
  - owner: repository owner
  - repo: repository name
  - issue_number: issue number
  - body: comment text
7. Search Issues

Triggers: "find issues about", "search for issues"

Use: mcp_GitHub_search_issues
Parameters:
  - query: search query (GitHub search syntax)
  - owner: repository owner (optional, scopes search)
  - repo: repository name (optional, scopes search)

Search syntax examples:

  • is:open label:bug - open bugs
  • author:username - issues by specific user
  • mentions:username - issues mentioning user
  • memory leak - issues containing "memory leak"
Show full SKILL.md (185 more words)Show less
8. Assign to Copilot

Triggers: "have copilot fix #X", "assign copilot to #X", "let AI fix this"

Use: mcp_GitHub_assign_copilot_to_issue
Parameters:
  - owner: repository owner
  - repo: repository name
  - issue_number: issue to assign
  - custom_instructions: additional guidance (optional)

Before assigning to Copilot:

  1. Read the issue to understand it
  2. Check if it's suitable for AI (clear requirements, bounded scope)
  3. Add custom instructions if needed
  4. Confirm with user

Example:

User: "have copilot fix issue #42"

Agent:
Issue #42: Fix memory leak in process cache
This appears to be a bounded bug fix. Copilot should be able to help.

Custom instructions I'll provide:
- Focus on the process_cache.cpp file
- Run existing tests after changes
- Don't modify the public API

Assign to Copilot? [y/n]
9. Get Issue Comments

Triggers: "show comments on #X", "what's the discussion on #X"

Use: mcp_GitHub_issue_read
Parameters:
  - method: "get_comments"
  - owner: repository owner
  - repo: repository name
  - issue_number: issue number
10. Manage Labels

Triggers: "add label to #X", "remove label from #X"

Use: mcp_GitHub_issue_write with labels parameter

Workflow Examples

Bug Report Workflow
User: "I found a bug - the config parser crashes on empty files"

Agent:
1. Creates issue with title, description, reproduction steps
2. Adds "bug" label
3. Asks if it should be assigned to anyone
4. Optionally assigns to Copilot for a fix
Issue Triage Workflow
User: "triage the open issues"

Agent:
1. Lists all open issues
2. For each, suggests:
   - Priority (based on labels, age, content)
   - Potential assignee
   - Whether Copilot could help
3. Asks which actions to take
Close with PR Workflow
User: "close #42, it was fixed in PR #50"

Agent:
1. Adds comment: "Fixed in #50"
2. Closes issue with reason: completed

Error Handling

ErrorResponse
Issue not found"Issue #X doesn't exist. Did you mean #Y?"
Permission denied"Don't have permission. Check PAT scopes."
Rate limited"GitHub rate limit hit. Wait a few minutes."
Network error"Can't reach GitHub. Check connection."

Output Formatting

When listing issues, use this format:

📋 Open Issues (5 total)

#42 🐛 Fix memory leak in process cache
    Labels: bug, high-priority
    Assigned: @dev1
    Age: 3 days

#38 ✨ Add network monitoring support  
    Labels: enhancement
    Assigned: —
    Age: 1 week

Emoji guide:

  • 🐛 bug
  • ✨ enhancement/feature
  • 📝 documentation
  • 🔧 maintenance
  • ❓ question
  • 🔒 security

Safety Guidelines

  1. Confirm destructive actions — Always confirm before closing or deleting
  2. Show before create — Display issue content before creating
  3. Preserve context — When updating, show what will change
  4. Rate limit awareness — Don't spam the API with many requests

© Cybereason-Public, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .cursor/skills/github-issues of Cybereason-Public/owLSM.

Open the folder on GitHubat commit 8e541af

Compare with similar skills

GitHub Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Issues compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Issues this skillCybereason-Public/owLSM280—~1.8kAutomated safety check: PassGPL-2.0
Herdr Issue Triageherdrdev/herdr43k—~517Automated safety check: PassApache-2.0
Issue Triagemono/SkiaSharp5.6k—~3.4kAutomated safety check: PassMIT
Issue Triage Loopcobusgreyling/loop-engineering11k—~522Automated safety check: PassMIT
LangBot Environment Setuplangbot-app/LangBot18k—~496Automated safety check: NotesApache-2.0
Triagearcee-ai/nac279—~2kAutomated safety check: PassApache-2.0

Similar skills

  • Herdr Issue Triage

    herdrdev/herdr

    Triages open herdr GitHub issues into a short decision-first Markdown table with a priority light, recommendation, age, reactions and a reason for each.

    43k GitHub stars~517 tokensUpdated today
    DevelopmentAuto-check passed

  • Issue Triage

    mono/SkiaSharp

    Triage a SkiaSharp GitHub issue or PR into structured JSON with classification (type, area, platform, severity), suggested response, automatable actions, and companion Markdown/HTML reports.

    5.6k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Issue Triage Loop

    cobusgreyling/loop-engineering

    Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.

    11k GitHub stars~522 tokensUpdated today
    DevelopmentAuto-check passed

  • LangBot Environment Setup

    langbot-app/LangBot

    Prepares a LangBot development and testing environment for an agent, covering service startup, proxy settings and browser access through Computer Use or Playwright MCP.

    18k GitHub stars~496 tokensUpdated today
    DevelopmentAuto-check: notes

  • Triage

    arcee-ai/nac

    Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked…

    279 GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

  • TMDb Backlog Triager

    adamayoung/TMDb

    Grooms the Backlog column of a GitHub project board by re-verifying each issue against current main, closing dead ones, promoting actionable ones to Ready and naming the decision the rest need.

    178 GitHub stars~5k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

More from Cybereason-Public/owLSM

All 9 skills in this repo

  • K8s Security Policies

    Cybereason-Public/owLSM

    Comprehensive guide for implementing NetworkPolicy, PodSecurityPolicy, RBAC, and Pod Security Standards in Kubernetes.

    280 GitHub starsUsed in 11 repos~2k tokens
    Auto-check passed

  • Helm Chart Scaffolding

    Cybereason-Public/owLSM

    Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.

    280 GitHub starsUsed in 12 repos~381 tokens
    Auto-check passed

  • Kubernetes Architect

    Cybereason-Public/owLSM

    Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration.

    280 GitHub starsUsed in 8 repos~2.6k tokens
    Auto-check passed

  • K8s Manifest Generator

    Cybereason-Public/owLSM

    Step-by-step guidance for creating production-ready Kubernetes manifests including Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims.

    280 GitHub starsUsed in 11 repos~433 tokens
    Auto-check passed

  • Add Gitmcp

    Cybereason-Public/owLSM

    Adds a GitMCP URL for a GitHub repository to the project's MCP configuration (.cursor/mcp.json).

    280 GitHub stars~919 tokensUpdated yesterday
    Auto-check passed

  • Measure Scenario Times

    Cybereason-Public/owLSM

    Adds temporary pytest-bdd timing hooks and writes debugscenariotimes.txt plus sorted step and scenario files.

    280 GitHub stars~676 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about GitHub Issues

What does GitHub Issues do?

Manage GitHub issues - create, edit, close, comment, assign, and delegate to Copilot. GitHub Issues is an agent skill from Cybereason-Public/owLSM. Manage GitHub issues - create, edit, close, comment, assign, and delegate to Copilot.

When should I use GitHub Issues?

GitHub Issues fits situations like: tasks that involve Issue triage.

How do I install GitHub Issues in Claude Code?

Run `npx skills add Cybereason-Public/owLSM --skill github-issues -a claude-code`. Or copy the skill folder (.cursor/skills/github-issues in Cybereason-Public/owLSM) into .claude/skills/github-issues in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Issues in Codex?

Run `npx skills add Cybereason-Public/owLSM --skill github-issues -a codex`. Or copy the skill folder (.cursor/skills/github-issues in Cybereason-Public/owLSM) into .agents/skills/github-issues in your project. Codex loads it when a task matches its description.

Can I use GitHub Issues in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Cybereason-Public/owLSM --skill github-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-issues, .gemini/skills/github-issues, .github/skills/github-issues and .opencode/skills/github-issues in your project.

What does GitHub Issues need to run?

SKILL.md names no scripts, command-line tools or credentials: GitHub Issues is instructions for the agent only.

Does GitHub Issues access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is GitHub Issues safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Issues use?

GitHub Issues is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Issues use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub Issues?

Skills that share tags, products or a category with GitHub Issues: Herdr Issue Triage (herdrdev/herdr, 43k stars), Issue Triage (mono/SkiaSharp, 5.6k stars), Issue Triage Loop (cobusgreyling/loop-engineering, 11k stars) and LangBot Environment Setup (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Issues?

Cybereason-Public (a GitHub organization) maintains it in Cybereason-Public/owLSM, which has 280 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 6, 2026.

Source: Cybereason-Public/owLSM on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.