How do I install the Org Github skill?

Run npx skillmds@latest add pooriaarab/org-github in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Org Github safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Org Github?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Org Github free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Org Github?

pooriaarab (@pooriaarab) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Org Github by pooriaarab — Agent Skill

Name: Org Github
Author: pooriaarab

Org Github

Use when the user wants to organize GitHub — auditing personal repos (active/stale/archive), pruning excessive stars, leaving inactive organizations, fixing repo descriptions/READMEs, applying consistent topics. Triggers: 'organize my GitHub', 'archive old repos', 'prune GitHub stars'.

pooriaarab b75a7b1 2.3 KB Updated Sep 17, 2026

File contents

GitHub Organizer

Organize personal GitHub presence via gh CLI.

Requirements

gh CLI installed and authenticated (gh auth login).
Account-level scope; for organizations, requires org membership.

Step 1 — Ask the User First

1. Scope — your personal repos only, or include orgs you belong to?
2. Repo classification — active (commit in last 90 days) / dormant (90d–1y) / stale (>1y) — what to do with each?
3. Stars cleanup — prune stars older than N months? Group remaining stars into lists?
4. Org membership — leave inactive orgs?
5. Repo metadata — fix missing descriptions, add topics, update READMEs?
6. Visibility audit — flag accidentally-public private-intent repos, or vice versa?

Steps (TBD)

Inventory — gh repo list (your repos), gh api user/starred, gh api user/orgs.
Classify — repos by activity, stars by age, orgs by your last contribution.
Plan — proposed archives, unstars, org-leaves, description fills, topic additions.
Approve — batch by category.
Apply — gh repo archive, gh api -X DELETE user/starred/<repo>, gh api -X DELETE user/memberships/orgs/<org>, etc.
Verify — final repo count, star count, org list.

Surface-specific notes

Archiving a repo is reversible but it stops accepting issues/PRs. Safer than deleting.
Deleting requires delete_repo scope — not in default gh auth login scopes; user must re-auth with gh auth refresh -s delete_repo.
Stars are public unless you've toggled them private — pruning is visible to followers.
Topics are limited to 20 per repo.
For private repos: respect any forks-of-private constraint (you can't archive a fork's parent).

---name: org-githubdescription: Use when the user wants to organize GitHub — auditing personal repos (active/stale/archive), pruning excessive stars, leaving inactive organizations, fixing repo descriptions/READMEs, applying consistent topics. Triggers: 'organize my GitHub', 'archive old repos', 'prune GitHub stars'.---# GitHub OrganizerOrganize personal GitHub presence via `gh` CLI.## Requirements- `gh` CLI installed and authenticated (`gh auth login`).- Account-level scope; for organizations, requires org membership.## Step 1 — Ask the User First```1. Scope — your personal repos only, or include orgs you belong to?2. Repo classification — active (commit in last 90 days) / dormant (90d–1y) / stale (>1y) — what to do with each?3. Stars cleanup — prune stars older than N months? Group remaining stars into lists?4. Org membership — leave inactive orgs?5. Repo metadata — fix missing descriptions, add topics, update READMEs?6. Visibility audit — flag accidentally-public private-intent repos, or vice versa?```## Steps (TBD)1. **Inventory** — `gh repo list` (your repos), `gh api user/starred`, `gh api user/orgs`.2. **Classify** — repos by activity, stars by age, orgs by your last contribution.3. **Plan** — proposed archives, unstars, org-leaves, description fills, topic additions.4. **Approve** — batch by category.5. **Apply** — `gh repo archive`, `gh api -X DELETE user/starred/<repo>`, `gh api -X DELETE user/memberships/orgs/<org>`, etc.6. **Verify** — final repo count, star count, org list.## Surface-specific notes- **Archiving a repo is reversible** but it stops accepting issues/PRs. Safer than deleting.- **Deleting requires `delete_repo` scope** — not in default `gh auth login` scopes; user must re-auth with `gh auth refresh -s delete_repo`.- Stars are public unless you've toggled them private — pruning is visible to followers.- Topics are limited to 20 per repo.- For private repos: respect any forks-of-private constraint (you can't archive a fork's parent).## See also- [`../org-life-organizer/_lib/taxonomy.md`](../org-life-organizer/_lib/taxonomy.md)- [`../org-life-organizer/_lib/patterns.md`](../org-life-organizer/_lib/patterns.md)- [`../mac-organizer/SKILL.md`](../mac-organizer/SKILL.md) — local repo cleanup (worktrees, node_modules) lives there

Frequently asked questions