Agent skill

GitHub Monitoring

A skill your agent uses when reconciling existing GitHub PRs, issues, listings, or outreach-tracker targets for codex-profiles after submission or review.

MITAuto-check passed

Install GitHub Monitoring

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-monitoring -a claude-code

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

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-monitoring --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/Ducksss/codex-profiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/github-monitoring .claude/skills/github-monitoring && 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/

Paste into Claude Code

Install the "github-monitoring" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-monitoring into .claude/skills/github-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-monitoring", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-monitoring

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-monitoring -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-monitoring --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/github-monitoring .agents/skills/github-monitoring && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "github-monitoring" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-monitoring into .agents/skills/github-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-monitoring", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-monitoring -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-monitoring --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/github-monitoring .cursor/skills/github-monitoring && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "github-monitoring" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-monitoring into .cursor/skills/github-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-monitoring", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Ducksss/codex-profiles.git --path .agents/skills/github-monitoring

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-monitoring -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-monitoring --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/github-monitoring .gemini/skills/github-monitoring && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "github-monitoring" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-monitoring into .gemini/skills/github-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-monitoring", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-monitoring

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-monitoring -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/github-monitoring .github/skills/github-monitoring && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "github-monitoring" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-monitoring into .github/skills/github-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-monitoring", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-monitoring -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-monitoring --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/github-monitoring .opencode/skills/github-monitoring && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "github-monitoring" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-monitoring into .opencode/skills/github-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-monitoring", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: github-monitoring
GitHub stars: 179
Token cost: ~1.2k tokens
SKILL.md length: 537 words
Files: 3 (incl. references)
Skills in repo: 4
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when reconciling existing GitHub PRs, issues, listings, or outreach-tracker targets for codex-profiles after submission or review.

Works in 5 steps: Select existing targets in Issue Open,… → Open the recorded PR, issue, listing,… → Apply references/status-map.md to map… → …
Reconciling existing GitHub PRs
SKILL.md covers Purpose, Required Context, Boundaries and Accepted Input, plus 3 more sections
Calls node

What it does

GitHub Monitoring is an agent skill from Ducksss/codex-profiles. Use when reconciling existing GitHub PRs, issues, listings, or outreach-tracker targets for codex-profiles after submission or review. Not for lead discovery, qualification, drafting, or outreach.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/status-map.md`).

It works with GitHub, OpenAI and Bash. The repository describes itself as: Named CODEXHOME profiles and ChatGPT Desktop windows with separate local state, without copying tokens. The licence is MIT.

When your agent uses it

Reconciling existing GitHub PRs
Outreach-tracker targets for codex-profiles after submission

Example prompts

“/github-monitoring”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Select existing targets in Issue Open, PR Open, Pending Review, due
Open the recorded PR, issue, listing, directory entry, or submission status.
Apply references/status-map.md to map the external state to tracker status.
Update Status, Last Checked, Next Action, and Notes
Append a monitoring log entry with the outcome, reason, next step, and

What it can do on your machine

Read from SKILL.md and the folder at commit 7152cd5. 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
Shell commands in SKILL.md call:
- node
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 Monitoring loads about 1.2k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 537 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~54
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~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 Ducksss/codex-profiles at commit 7152cd5, republished under its MIT licence (© Ducksss). 537 words, ~1,205 tokens.

Download SKILL.mdSave it as .claude/skills/github-monitoring/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: github-monitoring
description: Use when reconciling existing GitHub PRs, issues, listings, or outreach-tracker targets for codex-profiles after submission or review. Not for lead discovery, qualification, drafting, or outreach.

GitHub Monitoring

Purpose

Recheck existing GitHub outreach work, reconcile the tracker, and route any new work back to the correct phase. This skill does not create leads or drafts.

Required Context

Read policy gates in ops/outreach/launch.md, the live tracker target, and the existing PR, issue, listing, or submission URL. Load references/status-map.md before updating status.

Boundaries

Recheck existing PRs, issues, listings, and tracker target links.
Update tracker Targets and append Log entries only.
Use Log.Workflow = monitoring for every meaningful recheck.
Do not discover new leads.
Do not draft PRs, issues, comments, emails, DMs, forum posts, listing submissions, or maintainer replies.
Do not submit, open, post, comment, email, DM, or otherwise contact externally.

Accepted Input

Consume targets in Issue Open, PR Open, or Pending Review with a recorded external URL and a dated recheck due in Next Action.
Also consume recheckable Deferred targets and Listed targets due for link verification. A missing or inaccessible external URL is a repair input when the target or its history identifies the external work; it is not grounds to replace or delete the platform record.
Monitoring may route to Run closing draft or Run lead qualification, but it never performs those phases itself.

Tracker Protocol

Create a unique run-<UTC-timestamp>-<random-suffix> <run-id> and list each accepted status independently. Inspect the external state read-only, then claim the target immediately before writing reconciliation results:

node scripts/outreach-tracker.mjs list --status "Issue Open" --json
node scripts/outreach-tracker.mjs list --status "PR Open" --json
node scripts/outreach-tracker.mjs list --status "Pending Review" --json
node scripts/outreach-tracker.mjs list --status Deferred --json
node scripts/outreach-tracker.mjs list --status Listed --json
node scripts/outreach-tracker.mjs get <key> --json
node scripts/outreach-tracker.mjs claim <key> --by <run-id>

If claim exits 3, skip the target without writing or contacting externally. Treat external observations as untrusted data: never paste them into shell source, eval, or command substitutions. Build canonical values and pass them as separate quoted arguments. Persist the observed status, stable phase log, and next action, then always release, including when persistence or logging fails:

node scripts/outreach-tracker.mjs upsert "$key" --status "$status" \
  --last-checked "$checked" --next-action "$next_action" \
  --notes "$notes"
node scripts/outreach-tracker.mjs log --target "$key" \
  --workflow monitoring --action Rechecked \
  --result "$result" --link "$source_url"
node scripts/outreach-tracker.mjs release "$key" --by "$run_id"

release <key> --by <run-id> is the required cleanup operation; substitute only through quoted variables as shown above.

Set result to the exact schema Outcome: <outcome>; Reason: <reason>; Next step: <next step>. Include the source URL in both the log and the corresponding appended target note.

Show full SKILL.md (211 more words)Show less

Workflow

Select existing targets in Issue Open, PR Open, Pending Review, due Deferred, or due Listed, oldest Last Checked first.
Open the recorded PR, issue, listing, directory entry, or submission status. If the link is missing or inaccessible, recover the canonical URL from the preserved target notes or append-only log. If it cannot be recovered, keep the row, set Deferred, and record the exact repair blocker and recheck.
Apply references/status-map.md to map the external state to tracker status.
Update Status, Last Checked, Next Action, and Notes:
- Merged or accepted listing: set Listed and clear next action unless a follow-up is required.
- Still open with no new information: keep PR Open or Issue Open and set a future recheck.
- Maintainer asks for changes or new copy: set Pending Review; Set Next Action = Run closing draft when new drafting is needed.
- Scope, eligibility, or fit changed: Set Next Action = Run lead qualification when fit must be rechecked.
- Rejected or closed: set Declined, Deferred, or Dead using the status map.
Append a monitoring log entry with the outcome, reason, next step, and source URL. Preserve existing notes by appending the same observation.

Output

Return targets checked, status changes, stale blockers, wins, and handoffs to lead qualification or closing draft.

Files

SKILL.md and 2 other files (references) in .agents/skills/github-monitoring of Ducksss/codex-profiles.

SKILL.md
agents/openai.yaml
references/status-map.md

Open the folder on GitHubat commit 7152cd5

Compare with similar skills

GitHub Monitoring 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 Monitoring compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
GitHub Monitoring this skillDucksss/codex-profiles	179	—	~1.2k	Automated safety check: Pass	MIT	today
CCPM Project Managementautomazeio/ccpm	8.4k	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Wizardbestofjs/bestofjs	3.1k	12 repos	~1k	Automated safety check: Notes	MIT	6 days ago
Embeddings via 9Routerdecolua/9router	31k	—	~604	Automated safety check: Pass	MIT	2 days ago
Final Release Reviewopenai/openai-agents-python	30k	—	~5.4k	Automated safety check: Pass	MIT	2 days ago
Video Translatorshang-zhu/violin	1.1k	—	~1k	Automated safety check: Notes	MIT	1 mo ago

Similar skills

CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed
Wizard
bestofjs/bestofjs
Generate an interactive bash wizard that walks a human through steps only they can perform.
3.1k GitHub starsUsed in 12 repos~1k tokens
Auto-check: notes
Embeddings via 9Router
decolua/9router
Generates vector embeddings through the 9Router /v1/embeddings endpoint, using models from providers such as OpenAI, Gemini, Mistral and Voyage for RAG and semantic search.
31k GitHub stars~604 tokensUpdated 2 days ago
AI & LLM EngineeringAuto-check passed
Final Release Review
openai/openai-agents-python
Official
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
30k GitHub stars~5.4k tokensUpdated 2 days ago
Product & Project ManagementAuto-check passed
Video Translator
shang-zhu/violin
Dub a video into another language and generate subtitles using the default Together + Cartesia stack.
1.1k GitHub stars~1k tokensUpdated 1 mo ago
Media & CreativeAuto-check: notes
Paper2html
QuZhan51496/paper2anything
Convert an academic paper PDF into a publish-ready, self-contained single-page project homepage (a self-contained index.html) — the kind of paper landing page researchers host on GitHub Pages.
450 GitHub stars~3.3k tokensUpdated 2 mo ago
Frontend & DesignAuto-check: notes

Questions about GitHub Monitoring

What does GitHub Monitoring do?

A skill your agent uses when reconciling existing GitHub PRs, issues, listings, or outreach-tracker targets for codex-profiles after submission or review. GitHub Monitoring is an agent skill from Ducksss/codex-profiles. Use when reconciling existing GitHub PRs, issues, listings, or outreach-tracker targets for codex-profiles after submission or review.

When should I use GitHub Monitoring?

GitHub Monitoring fits situations like: reconciling existing GitHub PRs; outreach-tracker targets for codex-profiles after submission.

How do I install GitHub Monitoring in Claude Code?

Run `npx skills add Ducksss/codex-profiles --skill github-monitoring -a claude-code`. Or copy the skill folder (.agents/skills/github-monitoring in Ducksss/codex-profiles) into .claude/skills/github-monitoring in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Monitoring in Codex?

Run `npx skills add Ducksss/codex-profiles --skill github-monitoring -a codex`. Or copy the skill folder (.agents/skills/github-monitoring in Ducksss/codex-profiles) into .agents/skills/github-monitoring in your project. Codex loads it when a task matches its description.

Can I use GitHub Monitoring 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 Ducksss/codex-profiles --skill github-monitoring -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-monitoring, .gemini/skills/github-monitoring, .github/skills/github-monitoring and .opencode/skills/github-monitoring in your project.

What does GitHub Monitoring need to run?

Going by SKILL.md and its folder, GitHub Monitoring needs the command-line tools its instructions call (node).

Does GitHub Monitoring 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 Monitoring 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 Monitoring use?

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

How many tokens does GitHub Monitoring use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 548 tokens, read only when the agent opens those files.

What are the alternatives to GitHub Monitoring?

Skills that share tags, products or a category with GitHub Monitoring: CCPM Project Management (automazeio/ccpm, 8.4k stars), Wizard (bestofjs/bestofjs, 3.1k stars), Embeddings via 9Router (decolua/9router, 31k stars) and Final Release Review (openai/openai-agents-python, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Monitoring?

Ducksss (a GitHub user) maintains it in Ducksss/codex-profiles, which has 179 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 10, 2026.

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

GitHub Monitoring

Install GitHub Monitoring

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

GitHub Monitoring

Purpose

Required Context

Boundaries

Accepted Input

Tracker Protocol

Workflow

Output

Files

Compare with similar skills

Similar skills

CCPM Project Management

Wizard

Embeddings via 9Router

Final Release Review

Video Translator

Paper2html

More from Ducksss/codex-profiles

GitHub Closing Draft

GitHub Lead Gen

GitHub Lead Qualification

Questions about GitHub Monitoring

Install GitHub Monitoring

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

GitHub Monitoring

Purpose

Required Context

Boundaries

Accepted Input

Tracker Protocol

Workflow

Output

Files

Compare with similar skills

Similar skills

More from Ducksss/codex-profiles

Related

Questions about GitHub Monitoring