Agent skill

Open Source Maintainer

by numman-ali in numman-ali/n-skills

End-to-end GitHub repository maintenance for open-source projects.

Apache-2.0Auto-check passedAgent Workflows

Install Open Source Maintainer

skills CLI
$ npx skills add numman-ali/n-skills --skill open-source-maintainer -a claude-code

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

GitHub CLI
$ gh skill install numman-ali/n-skills open-source-maintainer --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/numman-ali/n-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/workflow/open-source-maintainer/skills/open-source-maintainer .claude/skills/open-source-maintainer && 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/

Facts

Skill name
open-source-maintainer
GitHub stars
1.1k
Token cost
~1.8k tokens
SKILL.md length
686 words
Files
24 (incl. scripts, references)
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

End-to-end GitHub repository maintenance for open-source projects.

  • Works in 7 steps: Setup → Capture (Run Triage) → Analyze (Issues + PRs) → …
  • Asked to triage issues
  • SKILL.md covers Operating Contract…, Interaction Model (Flexible,…, Reference Router (Just‑In‑Time) and Gates (Read‑Before‑Acting), plus 5 more sections
  • Runs TypeScript scripts from its folder; calls npx

What it does

Open Source Maintainer is an agent skill from numman-ali/n-skills. End-to-end GitHub repository maintenance for open-source projects. Use when asked to triage issues, review PRs, analyze contributor activity, generate maintenance reports, or maintain a repository. Triggers include "triage", "maintain", "review PRs", "analyze issues", "repo maintenance", "what needs attention", "open source maintenance", or any request to understand and act on GitHub issues/PRs. Supports human-in-the-loop workflows with persistent memory across sessions.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 26 other files, including scripts and reference files (for example `references/communication-guide.md`, `references/config.md` and `references/decision-framework.md`).

It sits in Agent Workflows, covering Open source maintenance, Agent memory and Issue triage. It works with GitHub. The repository describes itself as: Curated plugin marketplace for AI agents - works with Claude Code, Codex, and openskills. The licence is Apache-2.0.

When your agent uses it

  • Asked to triage issues
  • Analyze contributor activity
  • Generate maintenance reports
  • Maintain a repository

Example prompts

  • “triage”
  • “maintain”
  • “review PRs”
  • “/open-source-maintainer”

Requirements

  • Node.js

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Setup
  2. Capture (Run Triage)
  3. Analyze (Issues + PRs)
  4. Synthesize (What matters next)
  5. Align (Human-in-the-loop)
  6. Execute (Agent does the work)
  7. Record (Project memory)

What it can do on your machine

Read from SKILL.md and the folder at commit fdabc47. 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

    Ships 9 files in scripts/ (TypeScript, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    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

Open Source Maintainer loads about 1.8k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 125 tokens; SKILL.md has 686 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~125
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from numman-ali/n-skills at commit fdabc47, republished under its Apache-2.0 licence (© numman-ali). 686 words, ~1,800 tokens.

Download SKILL.mdSave it as .claude/skills/open-source-maintainer/SKILL.md (or your agent's skills folder). This skill also uses 23 other files; get the full folder from GitHub.
name
open-source-maintainer
description
End-to-end GitHub repository maintenance for open-source projects. Use when asked to triage issues, review PRs, analyze contributor activity, generate maintenance reports, or maintain a repository. Triggers include "triage", "maintain", "review PRs", "analyze issues", "repo maintenance", "what needs attention", "open source maintenance", or any request to understand and act on GitHub issues/PRs. Supports human-in-the-loop workflows with persistent memory across sessions.

Open Source Maintainer

Run a GitHub repository like a steward: fix what blocks users, keep UX + docs sharp, reduce future support burden, and grow trust and adoption.

This skill is designed for “head of maintenance” operation: you do the analysis and propose the next moves with confidence. The human should be able to mostly ask: “What’s next?”


Operating Contract (Non‑Negotiables)

  • You are the maintainer. Optimize for long‑term repo health, not just throughput.
  • PRs are intelligence sources, not merge candidates. Extract intent, then implement the fix yourself.
  • Never merge external PRs. The agent writes all code.
  • Human approval required for any public action (commenting, closing, labeling, releases, etc.).
  • Default to low user burden: do the legwork; ask questions only when it changes the plan materially.
  • Project-first decisions (CEV-style): resolve conflicts, reduce future maintenance load, prefer clarity and stability.

Interaction Model (Flexible, But Grounded)

Always Include (briefly)
  1. Top recommendation(s) (1–3 items)
  2. Why it matters (impact + leverage)
  3. Confidence + risks/unknowns (what could be wrong, what needs verification)
  4. What you need from the human (only if needed: approval or a choice)

Everything else is optional and should be progressively disclosed.

Modes (choose implicitly, switch freely)
  • Maintain: triage, consolidate duplicates, hygiene, labels, backlog shaping
  • Ship: implement fixes/features, add tests, cut releases
  • Investigate: reproduce, narrow scope, request minimal info, design experiments
  • Grow: docs/onboarding, positioning, contributor experience, adoption, trust signals

If unsure which mode to use, default to Maintain → Ship.


Reference Router (Just‑In‑Time)

Do not read everything by default. Load the minimum reference needed for the task you are about to do.

When you are about to…Load this reference (if not already in this run)Output you must produce
Understand the workflow and run artifactsreferences/workflow.md, references/report-structure.mdCorrectly locate and interpret report files
Analyze issues/PRs (intent, severity, actionability)references/intent-extraction.mdClear intent + actionability + relationships
Assess PR approach quality/risk (as input to your implementation)references/quality-checklist.mdRisk notes + test plan + edge cases
Decide close/defer/ask-for-info/prioritizereferences/decision-framework.mdA decision with rationale + next step
Draft any public responsereferences/communication-guide.mdA concise public draft aligned to tone
Change scoring/labels/stale policyreferences/config.mdProposed config edits + impact
Initialize/reshape .github/maintainer/ statereferences/repo-state-template.mdCorrect state files created/updated

Gates (Read‑Before‑Acting)

These are “STOP gates” where skipping the right reference tends to cause mistakes.

  1. Before recommending closure/deferral or enforcement: load references/decision-framework.md.
  2. Before drafting any public comment: load references/communication-guide.md.
  3. Before using a PR as guidance for implementation: load references/quality-checklist.md.
  4. Before deep intent/relationship mapping: load references/intent-extraction.md.
  5. Before changing scoring/automation: load references/config.md.

Default Workflow (End‑to‑End)

Show full SKILL.md (275 more words)Show less
Stage 0 — Setup
  • Confirm repo and scope.
  • Ensure .github/maintainer/ exists (create via templates if missing).
  • Read .github/maintainer/context.md to align with project priorities and tone.
Stage 1 — Capture (Run Triage)

From repo root:

bash
npx tsx /path/to/open-source-maintainer/scripts/triage.ts

Prefer --delta if a previous run exists.

Stage 2 — Analyze (Issues + PRs)
  • Use intent extraction and quality checklist to convert items into actionable notes.
  • Update persistent notes in .github/maintainer/notes/ (scores, confidence, rationale).
Stage 3 — Synthesize (What matters next)
  • Produce a top 5–7 priority list with clear reasoning.
  • Identify duplicates, consolidate discussion targets, and surface opportunity work.
Stage 4 — Align (Human-in-the-loop)
  • Present recommendations with confidence + tradeoffs.
  • Ask only for approvals/choices that unblock execution.
Stage 5 — Execute (Agent does the work)
  • Implement fixes directly (PRs inform, but do not merge).
  • Prepare public-facing drafts and wait for explicit approval before posting.
Stage 6 — Record (Project memory)
  • Update .github/maintainer/decisions.md, .github/maintainer/patterns.md, .github/maintainer/contributors.md.
  • Keep .github/maintainer/state.json current for delta runs.

Script Usage

bash
# Standard run (creates reports/<datetime>/)
npx tsx /path/to/open-source-maintainer/scripts/triage.ts

# Compare with previous run
npx tsx /path/to/open-source-maintainer/scripts/triage.ts --delta

# Keep existing folder if same datetime
npx tsx /path/to/open-source-maintainer/scripts/triage.ts --keep

# Override report folder name
npx tsx /path/to/open-source-maintainer/scripts/triage.ts --datetime 2026-01-17T12-30-00

# Use a custom config path
npx tsx /path/to/open-source-maintainer/scripts/triage.ts --config .github/maintainer/config.json

Per‑Repo State (Persistent Memory)

The skill maintains project memory in .github/maintainer/:

FilePurpose
context.mdProject vision, priorities, tone, boundaries
decisions.mdDecision log with reasoning
contributors.mdNotes on specific contributors
patterns.mdObserved patterns and learnings
standing-rules.mdAutomation policies
notes/Persistent per-item analysis (issues/PRs)
work/Briefs, prompts, opportunity backlog
index/Machine index + relationship graph
runs.mdRun ledger with report paths
state.jsonTechnical state for delta computation

Notes/work/index are persistent across runs; reports are snapshots.


Citation Format

Reference items consistently in reports and responses:

  • ISSUE:42 — Issue #42
  • ISSUE:42:C:3 — Comment #3 on issue #42
  • PR:38 — Pull request #38
  • PR:38:R:1 — Review #1 on PR #38
  • PR:38:RC:4 — Review comment #4 on PR #38

Human Approval Required

Never execute without explicit approval:

  • Posting comments
  • Opening or closing issues or PRs
  • Adding/removing labels
  • Any public-facing action

© numman-ali, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 23 other files (scripts, references) in skills/workflow/open-source-maintainer/skills/open-source-maintainer of numman-ali/n-skills.

  • SKILL.md
  • references/communication-guide.md
  • references/config.md
  • references/decision-framework.md
  • references/intent-extraction.md
  • references/quality-checklist.md
  • references/repo-state-template.md
  • references/report-structure.md
  • references/workflow.md
  • scripts/triage.ts
  • scripts/triage/analysis.ts
  • scripts/triage/config.ts
  • scripts/triage/derive.ts
  • scripts/triage/git-summary.ts
  • scripts/triage/github.ts
  • scripts/triage/graph.ts
  • scripts/triage/index.ts
  • scripts/triage/main.ts
  • … and 6 more

Open the folder on GitHubat commit fdabc47

Compare with similar skills

Open Source Maintainer 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.

Open Source Maintainer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Open Source Maintainer this skillnumman-ali/n-skills1.1k—~1.8kAutomated safety check: PassApache-2.0
Context Mode Opsmksglu/context-mode26k—~6kAutomated safety check: PassCustom licence
Harbor Issue and PR IntakeYeachan-Heo/oh-my-claudecode40k—~5.4kAutomated safety check: PassMIT
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK4.7k—~2.8kAutomated safety check: PassApache-2.0
Ouroboros Maintainer TriageQ00/ouroboros6.2k—~1.7kAutomated safety check: PassMIT

Similar skills

  • Context Mode Ops

    mksglu/context-mode

    Runs maintenance for the context-mode project with parallel subagents: issue triage, PR review, releases, bug fixes, announcements and branch syncing.

    26k GitHub stars~6k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Harbor Issue and PR Intake

    Yeachan-Heo/oh-my-claudecode

    Triages incoming issues and pull requests for a maintainer: verifies claims, reuses past decisions and delivers a docket of open questions, and never merges.

    40k GitHub stars~5.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed
  • WinAppSDK Triage Meeting Prep

    microsoft/WindowsAppSDK

    Official

    Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.

    4.7k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.

    6.2k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Audits open GitHub issues, categorizes them, flags duplicates and linked PRs in three phases, with optional deep analysis and comments posted only after validation.

    83k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check: notes

More from numman-ali/n-skills

  • Gastown

    numman-ali/n-skills

    Multi-agent orchestrator for Claude Code. An agent skill from numman-ali/n-skills.

    1.1k GitHub stars~6k tokensUpdated 25 days ago
    Auto-check passed
  • Orchestration

    numman-ali/n-skills

    Multi-agent orchestration for complex tasks. An agent skill from numman-ali/n-skills.

    1.1k GitHub stars~7.7k tokensUpdated 25 days ago
    Auto-check passed

Works with

Questions about Open Source Maintainer

What does Open Source Maintainer do?

End-to-end GitHub repository maintenance for open-source projects. Open Source Maintainer is an agent skill from numman-ali/n-skills. End-to-end GitHub repository maintenance for open-source projects.

When should I use Open Source Maintainer?

Open Source Maintainer fits situations like: asked to triage issues; analyze contributor activity; generate maintenance reports; maintain a repository.

How do I install Open Source Maintainer in Claude Code?

Run `npx skills add numman-ali/n-skills --skill open-source-maintainer -a claude-code`. Or copy the skill folder (skills/workflow/open-source-maintainer/skills/open-source-maintainer in numman-ali/n-skills) into .claude/skills/open-source-maintainer in your project. Claude Code loads it when a task matches its description.

How do I install Open Source Maintainer in Codex?

Run `npx skills add numman-ali/n-skills --skill open-source-maintainer -a codex`. Or copy the skill folder (skills/workflow/open-source-maintainer/skills/open-source-maintainer in numman-ali/n-skills) into .agents/skills/open-source-maintainer in your project. Codex loads it when a task matches its description.

Can I use Open Source Maintainer 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 numman-ali/n-skills --skill open-source-maintainer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/open-source-maintainer, .gemini/skills/open-source-maintainer, .github/skills/open-source-maintainer and .opencode/skills/open-source-maintainer in your project.

What does Open Source Maintainer need to run?

Going by SKILL.md and its folder, Open Source Maintainer needs TypeScript for the scripts in its folder and the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Open Source Maintainer access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Open Source Maintainer 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Open Source Maintainer use?

Open Source Maintainer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Open Source Maintainer use?

About 1.8k tokens (SKILL.md is roughly 7.2k 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 10k tokens, read only when the agent opens those files.

What are the alternatives to Open Source Maintainer?

Skills that share tags, products or a category with Open Source Maintainer: Context Mode Ops (mksglu/context-mode, 26k stars), Harbor Issue and PR Intake (Yeachan-Heo/oh-my-claudecode, 40k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars) and WinAppSDK Triage Meeting Prep (microsoft/WindowsAppSDK, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Open Source Maintainer?

numman-ali (a GitHub user) maintains it in numman-ali/n-skills, which has 1,051 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 12, 2026.

Source: numman-ali/n-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.