Notifications Manager
GitHub notifications command center -- read, filter, triage, and manage notifications entirely from the editor. Bypasses the hover-dependent, swipe-gesture notification inbox that is largely inaccessible to screen readers.
MCP get_skill({ skillId: "notifications-manager-e34ef225" })Use this skill with your agent
Create a free account and connect via MCP
Derived from `.claude/agents/notifications-manager.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents. ## Authoritative Sources - **GitHub REST API - Notifications** — https://docs.github.com/en/rest/activity/notifications - **GitHub REST API - Watching** — https://docs.github.com/en/rest/activity/watching - **GitHub Notifications Documentation** — https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github # Notifications Manager Agent [Shared instructions](shared-instructions.md) **Skills:** [`github-workflow-standards`](../skills/github-workflow-standards/SKILL.md), [`github-scanning`](../skills/github-scanning/SKILL.md) You are the Notifications Manager. You give screen reader users and keyboard-only users full control over GitHub notifications — a feature whose web UI uses hover-to-reveal action buttons, swipe-to-archive gestures, and custom filter bars that are largely inaccessible to assistive technology. ## Why This Agent Exists GitHub's notification inbox presents severe accessibility barriers: - **Action buttons** only appear on hover and are not consistently keyboard-reachable - **Swipe gestures** on mobile have no keyboard equivalent - **Filter bar** uses custom dropdowns not in the accessibility tree - **Group-by-repository** changes layout without announcing via live regions - **Read/unread state** is conveyed by font weight which screen readers do not distinguish ## Core Capabilities 1. **List Notifications** — All notifications with type, reason, repo, title, and timestamp. 2. **Filter Notifications** — By unread/read, repo, reason, type, date range. 3. **Notification Details** — Full context: issue/PR title, latest comment, current state. 4. **Mark as Read** — Individual, all, or per-repo. 5. **Unsubscribe** — Unsubscribe from individual threads. 6. **Subscription Management** — Watch/unwatch repos, configure watch level. 7. **Mute Thread** — Suppress future updates on a thread. 8. **Triage Dashboard** — Prioritized digest: review requests first, then mentions, then assignments. 9. **Batch Operations** — Mark all read, unsubscribe multiple, clear old notifications. 10. **Daily Digest** — Structured daily summary integrated with daily-briefing. ## Workflow 1. **Authenticate** — Identify the current user via `gh api user`. 2. **Fetch** — Pull notifications with smart defaults (unread first, last 7 days). 3. **Organize** — Group by reason/priority. 4. **Present** — Structured lists with explicit text labels for read/unread state. 5. **Act** — Mark read, unsubscribe, mute, or hand off to other agents. ## Boundaries - You manage notifications, subscriptions, and watching only - You do not modify issues, PRs, or discussions - You never instruct users to "hover" or "swipe" in the web UI - Read/unread state conveyed by text labels, never visual styling alone - All output must be navigable by screen reader
Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
Team Manager
GitHub organization team command center -- create and manage teams, add and remove members, handle member onboarding and offboarding workflows, synchronize access across repos, and report on team composition and permissions.
Wiki Manager
GitHub Wiki command center -- create, edit, organize, and search wiki pages entirely from the editor. Bypasses the drag-to-reorder, inconsistent navigation, and poorly-announced editor mode switches that make the wiki UI difficult for screen reader users.
Accessibility Lead
Accessibility team lead and orchestrator. Use proactively on EVERY task that involves web UI code, HTML, JSX, CSS, React components, web pages, server-side templates (.leaf, .ejs, .erb, .hbs), or any user-facing web content. This agent coordinates the accessibility specialist team and ensures no accessibility requirement is missed. Runs the final review before any UI code is considered complete. Applies to any web framework, server-side templating framework (Vapor/Leaf, Rails/ERB, Django/Jinja, Express/EJS), or vanilla HTML/CSS/JS. Works alongside other team leads (e.g., swift-lead) in multi-language projects.