Github

Community

notque

github

GitHub: notification triage, profile rule extraction.

Overview

Publisher	notque
Repository	`vexjoy-agent`
Skill name	`github`
Stars	443
Forks	50
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by notque on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/notque/vexjoy-agent/tree/main/skills/integrations/github
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.

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/notque/vexjoy-agent.git /tmp/vexjoy-agent
mkdir -p .claude/skills
cp -r /tmp/vexjoy-agent/skills/integrations/github .claude/skills/github

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Github 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 Github 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 Github 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.

GitHub Skill

GitHub notification triage and issue/PR queue classification.

Mode Selection

Request	Mode
Notifications, inbox, cleanup	Notification Triage
Issue or PR queue, review items	Queue Triage

Notification Triage

Fetch, classify, and report GitHub notifications via the triage script.

Commands

bash
# Report-only (default)
python3 scripts/github-notification-triage.py

# Mark informational notifications as read
python3 scripts/github-notification-triage.py --mark-read

# Save report to ~/.claude/reports/notifications/
python3 scripts/github-notification-triage.py --save

# Cron/scheduled: auto-clear noise and save
python3 scripts/github-notification-triage.py --mark-read --save

Steps

Run report-only: python3 scripts/github-notification-triage.py.
Display the output. The report classifies notifications as:
- Action required -- PRs awaiting review, mentions, assigned issues.
- Informational -- CI results, bot comments, automated updates.
If the user says "clean them up", "mark read", "clear the noise", or "yes" to clearing informational items, re-run with --mark-read. Confirm how many were marked read.

Scheduled (no interactive user): run with --mark-read --save.

Exit codes: 0 = success, 1 = error (auth, API, script not found).

Queue Triage

When triaging a queue of issues or PRs (not just notifications), produce one card per item.

Card Format

Open each card with the item's full GitHub URL on its own line, then these fields in order:

Field	Content
What	One sentence: what the issue/PR asks or changes.
Why	Motivation or problem it addresses.
Author trust	Maintainer, known contributor, first-timer, or bot. Cite prior merged PRs.
Fit	Match to project scope and conventions.
Risk	Blast radius: files touched, API/behavior changes, security or data paths.
Proof state	CI status, tests added, repro steps, screenshots. "Unverified" when none.
Blocker	Single thing stopping progress, or "None".
Next action	One concrete step with named actor. Label Autonomous or Needs-owner.

Example:


https://github.com/owner/repo/pull/123
What: Adds retry with backoff to the webhook sender.
Why: Webhooks drop on transient 5xx from receivers.
Author trust: Known contributor, 4 merged PRs.
Fit: Matches existing client retry pattern in net/client.go.
Risk: Low — one module, behavior gated behind config flag.
Proof state: CI green; unit tests cover backoff schedule.
Blocker: None.
Next action: Autonomous — review and merge.

Autonomous vs Needs-owner

Autonomous -- the agent can complete the action alone: reply with a question, label, close an obvious duplicate, merge a green PR within granted authority, rebase.
Needs-owner -- requires owner judgment: scope decisions, breaking changes, security-sensitive merges, releases, money, or access.

When in doubt, label Needs-owner and state the decision the owner must make.

Clean-Checkout Gate

Before any local work on an item (checkout, tests, repro):

Run git status --short.
Proceed only when output is empty.
If dirty, mark the card Needs-owner with blocker "dirty working tree in <repo>" and continue triaging from API data only.

Frequently asked questions

What does the Github AI skill do?

GitHub: notification triage, profile rule extraction.

Why use Github on TypingMind?

Because you install it once and use it with any model. Github 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 Github in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/notque/vexjoy-agent/tree/main/skills/integrations/github. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Github?

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 Github?

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

Is the Github AI skill free?

Yes. It is published on GitHub by notque 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

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Debugging

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Openclaw Live Updater

openclaw

OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

GitHub Skill

Mode Selection

Notification Triage

Commands

Steps

Queue Triage

Card Format

Autonomous vs Needs-owner

Clean-Checkout Gate

Frequently asked questions

Related AI Skills

Set up your own AI workspace now