Skip to content
Skills Library
DevOps & cloud · Automation

org-setup

/org-setup

Use when creating or tidying up a GitHub organization, including its profile README, the public .github repo with default community files, a verified domain, pinned repos, the org's description and avatar, member defaults such as base permissions and two-factor authentication, or auditing how an existing org is set up.

Repository
githard ↗
Licence
MIT
Last repository change
10.11.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
2
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: bootstrap-dotgithub.sh, org-audit.sh

What it does and when to use it

Use when creating or tidying up a GitHub organization, including its profile README, the public .github repo with default community files, a verified domain, pinned repos, the org's description and avatar, member defaults such as base permissions and two-factor authentication, or auditing how an existing org is set up.

Original author description

Use when creating or tidying up a GitHub organization, including its profile README, the public .github repo with default community files, a verified domain, pinned repos, the org's description and avatar, member defaults such as base permissions and two-factor authentication, or auditing how an existing org is set up.

How it works

  1. The checklist
  2. The .github repo
  3. Checking an org
  4. An existing org
Original SKILL.md headings · 46 lines, 521 words
SKILL.md preview
---
name: org-setup
description: Use when creating or tidying up a GitHub organization, including its profile README, the public .github repo with default community files, a verified domain, pinned repos, the org's description and avatar, member defaults such as base permissions and two-factor authentication, or auditing how an existing org is set up.
---

# Org setup

An org's page is the first thing people see before they open a single repo. A blank one says nobody's home. This skill sets up an org the way you'd want it a year from now, or audits one that's already running.

The reasons behind each item are in `${CLAUDE_PLUGIN_ROOT}/knowledge/lessons.md` (Repo setup).

## The checklist

| Item | Who | How |
|---|---|---|
| Display name, description, website, public email | **owner** | Org settings, or `gh api -X PATCH orgs/ORG -f description="..." -f blog=https://...` run by the owner. Write the description with the `writing` skill. |
| Avatar | **owner** | **Settings**, then **Profile**, then **Upload new picture**. No API. |
| Public `.github` repo with `profile/README.md` | you prepare, **owner** runs | Fill `${CLAUDE_SKILL_DIR}/templates/profile/README.md`. Add the default community files from `repo-setup`: CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, issue and PR templates. Any repo without its own copy inherits them. |
| Verified domain | **owner** | **Settings**, then **Verified and approved domains**, then **Add a domain**. Add the TXT record GitHub shows at the DNS host, then click **Verify**. The org's public email must be on that domain. |
| Pinned repos | **owner** | The org's page, then **Customize pins**. No API. |
| Members get read access by default | **owner** | **Settings**, then **Member privileges**, then **Base permissions**: Read. |
| Two-factor authentication required | **owner** | **Settings**, then **Authentication security**, then **Require two-factor authentication**. Check every member has 2FA first, because anyone without it is removed from the org. |
| Sign-off required on web commits | **owner** | **Settings**, then **Repository**, then **Require contributors to sign off on web-based commits**, or `gh api -X PATCH orgs/ORG -F web_commit_signoff_required=true` run by the owner. |

Org settings are account changes, so every one goes to the owner, even when an API exists. Give each as numbered steps with the URL, the button names, or the exact command.

## The .github repo

Prepare the files in a local folder, then give the owner one command:

```sh
bash ${CLAUDE_SKILL_DIR}/bootstrap-dotgithub.sh ORG /absolute/path/to/folder
```

It creates the public repo if it isn't there, makes `main` match the folder, and is safe to run again. Agents are often blocked from creating public repos and changing org settings, and that's right. The owner runs it, and you check the result.

Once it exists, give `ORG/.github` the same treatment as any repo: run `repo-setup` on it, ruleset included.

## Checking an org

```sh
bash ${CLAUDE_SKILL_DIR}/org-audit.sh ORG
```

It prints `ok`, `missing`, `skipped` or `unknown` for each item. Add `--skip "verified domain"` (or any item's name, exactly as printed) for something that's off on purpose, such as a domain the project doesn't have. Settings only owners can see come back `unknown` for anyone else, never `ok`. Report what's missing in the order of the table, with the owner's steps for each.

## An existing org

Run the audit, then the `.github` repo first: it fixes community files for every repo that doesn't have its own. Change the default member permission or turn on 2FA only after checking who it affects. Never remove a member.
Files in this package (4)
  • SKILL.md 4 KB
  • bootstrap-dotgithub.sh 2 KB
  • org-audit.sh 3 KB
  • templates/profile/README.md 1 KB

Versions

The database has no other skills named org-setup.

Database snapshot: 13.11.2026 · package version b8f58878d05b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100repo-setup
    Use when creating a new GitHub repo, getting a repo ready to go public, or checking how an existing repo is set up, including community files, a license, branch protection or rulesets, DCO sign-off, Dependabot, pinned GitHub Actions, CI, issue and PR templates, CODEOWNERS,…
  • 90dx-org-switch
    Switches the active Salesforce org (default target-org) using the Salesforce CLI. Use whenever someone wants to change which org CLI commands run against — whether they say \"switch org\", \"change default org\", \"set my org to\", \"use alias\", \"point to\", or describe…
  • 100github
    Set the project up on GitHub and keep it there, step by step - install git and gh and sign in, git's identity, put the project in a GitHub repo (private or public), a private repo of its own for the project's docs, publish a site on GitHub Pages with an automatic workflow, a…
  • 100github-profile-optimization
    Audits and rebuilds a personal or organization profile on GitHub as a developer-relations surface - the profile README, the six pinned items, bio and social fields, the organization profile repository, and the contribution signals visitors read as evidence. Use whenever someone…
  • 100repo-settings
    Bring a GitHub repository's settings to one shape - the About, merge methods and auto-merge, a ruleset on the default branch, a standard label set, Dependabot and secret scanning, unused tabs turned off, and a full community profile for a public repository. Use when the user…
  • 100ghreport
    Read-only org repo state report. Reuses ghsync's repo discovery (teams union org-repo-list) but, instead of cloning, queries each repo's remote GitHub state - open PRs, CI on the default branch, open security alerts (Dependabot / code-scanning / secret-scanning), and branch…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.