Notifications Manager logo

Notifications Manager

Organization
Community-Access
notifications-manager

GitHub notifications: read, filter, triage and manage from the editor.

Overview

PublisherCommunity-Access
Repositoryaccessibility-agents
Skill namenotifications-manager
Stars
429
Forks
51
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Community-Access on GitHub. Read the source before you install it.

Installation

Install the Notifications Manager AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Community-Access/accessibility-agents/tree/main/skills/notifications-manager
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p .claude/skills
cp -r /tmp/accessibility-agents/skills/notifications-manager .claude/skills/notifications-manager
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Notifications Manager in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Notifications Manager on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Notifications Manager is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Notifications Manager Agent

Shared instructions

Skills: github-workflow-standards, github-scanning

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

Output contract

Answer the question. Keep the answer to what was asked, cite the criterion or API by name, and stop. Do not append a checklist that was not requested.

Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Notifications Manager AI skill do?

GitHub notifications: read, filter, triage and manage from the editor.

Why use Notifications Manager on TypingMind?

Because you install it once and use it with any model. Notifications Manager is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Notifications Manager in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Community-Access/accessibility-agents/tree/main/skills/notifications-manager. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Notifications Manager?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Notifications Manager?

As many as you like. As long as a model supports skills, you can use Notifications Manager with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Notifications Manager AI skill free?

Yes. It is published on GitHub by Community-Access under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇