$ loading_
Search GitHub issues and PRs assigned to you or matching queries.
The material indicates this is essentially an open-source prompt/documentation skill that guides use of the GitHub CLI to query issues/PRs. It does not declare built-in secrets, remote endpoints, or file read/write behavior, so overall risk is low; however, it normally relies on local gh authentication and GitHub API access, which warrants standard caution for credentials and network use.
The package declares no required secrets, but the README explicitly relies on the `gh` CLI to call the GitHub API, which in practice usually uses locally configured GitHub auth/token. No extra credential collection or export instructions are shown, so this is standard caution rather than a red flag.
Although no remote host is separately declared, the sample `gh api /search/issues` commands will send queries to the GitHub API and retrieve issue/PR metadata. This egress is directly related to the stated function, and no unrelated or unknown endpoints are indicated.
The system flags it as prompt-only, and the material itself is a set of command examples and usage rules, with no auditable install script, background process, or embedded local code execution logic. The README tells the user to run terminal commands, but that is documentation guidance rather than execution implemented by the skill itself.
There is no stated access to local files, databases, clipboard, or other system resources; the described output is limited to GitHub search result fields. The material does not request data access beyond what is needed for GitHub issue/PR queries.
The source is an open-source Microsoft GitHub repository, which is a strong risk-reducing factor because the code/material can be audited. While the repo has 0 stars, no declared license, and unknown maintenance status, those add some uncertainty but do not amount to a high-risk supply-chain red flag on the available facts.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "inbox-search-issues" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/vscode-team-kit/main/github-inbox/skills/inbox-search-issues/SKILL.md 2. Save it as ~/.claude/skills/inbox-search-issues/SKILL.md 3. Reload skills and tell me it's ready
Search GitHub for all issues and PRs currently assigned to me, sorted by most recently updated.
A list of issues and PRs assigned to you for quick follow-up.
Find GitHub issues created in the last 7 days with no assignee and no labels as a triage queue.
A triage list of issues that need review and categorization.
Search the repository for all open issues and PRs labeled bug that mention the keyword payment.
A filtered result list to quickly locate a specific topic or issue type.
Use gh CLI to search for issues and PRs beyond notifications. This covers your full "issues inbox" — assigned work, triage queue, open PRs, and custom queries.
gh api /search/issues --jq '.items[] | {number, title, repo: .repository_url, state, labels: [.labels[].name], updated_at, html_url}' -f q='assignee:@me is:open is:issue sort:updated-desc'
gh api /search/issues --jq '.items[] | {number, title, repo: .repository_url, state, draft: .draft, updated_at, html_url}' -f q='author:@me is:open is:pr sort:updated-desc'
gh api /search/issues --jq '.items[] | {number, title, repo: .repository_url, state, updated_at, html_url}' -f q='review-requested:@me is:open is:pr sort:updated-desc'
This depends on the repo's label conventions. Common pattern — issues with no bug, feature-request, or enhancement label:
gh api /search/issues --jq '.items[] | {number, title, labels: [.labels[].name], updated_at, html_url}' -f q='assignee:@me is:open is:issue -label:bug -label:feature-request -label:enhancement sort:updated-desc repo:{owner}/{repo}'
Replace {owner}/{repo} with the target repository.
gh api /search/issues --jq '.items[] | {number, title, state, labels: [.labels[].name], updated_at, html_url}' -f q='is:open is:issue repo:{owner}/{repo} sort:updated-desc'
gh api /search/issues --jq '.items[] | {number, title, updated_at, html_url}' -f q='assignee:@me is:open is:issue sort:updated-asc updated:<{30_days_ago_date}'
Replace {30_days_ago_date} with a date like 2026-01-24.
gh api /search/issues --jq '.items[] | {number, title, state, labels: [.labels[].name], html_url}' -f q='is:open milestone:"{milestone}" repo:{owner}/{repo}'
The GitHub search syntax supports:
assignee:@me, author:@me, mentions:@meis:open, is:closed, is:issue, is:prlabel:bug, -label:duplicaterepo:owner/repo, org:microsoftreview-requested:@me, reviewed-by:@mesort:updated-desc, sort:created-descupdated:>2026-01-01 (date filters)gh api /search/issues --jq '.items[] | {number, title, state, labels: [.labels[].name], updated_at, html_url}' -f q='{query}'
jq or other programs — use --jq2>/dev/null or redirectsAdd emoji reactions to GitHub issues or pull requests quickly.
Let AI agents read and write memory with environment-aware storage fallback.
Gather independent multi-model plans and debates for implementation and architecture decisions.
Get high-signal second opinions on plans, designs, and implementations early.
Create and manage AST ban rules to block specific code syntax patterns.
Set up Component Explorer with CLI, MCP, and VS Code tooling.
Fetch GitHub issues, create fixes, open PRs, and handle reviews.
Fetch and review GitHub notifications quickly using the gh CLI.
Connect to GitHub for repo search, issue, PR, and file workflows.
Manage issues, PRs, logs, releases, and repos with GitHub CLI.
Search, read, and create GitHub issues and pull requests with natural language.
Query public GitHub repos, issues, PRs, metadata, and READMEs in natural language.