[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KAVX2HAQ86Y0AFW638457":3,"skill-same:01M77KAVX2HAQ86Y0AFW638457":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M77KAVX2HAQ86Y0AFW638457","gh-create-app",null,"Create (from scratch) an org- or enterprise-scoped GitHub App for workflow authentication — walk the UI-gated registration with starter PR-automation permissions, install it on the target repo(s), set App ID + private key as secrets, verify a minted installation token, and save a checked-in metadata doc. Idempotent: detects an already-configured App and offers to verify instead of re-creating.","TheVoskamps\u002Fclaude-plugins-marketplace","TheVoskamps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235012489?v=4","01M77K5ZCP12QCJPQ85WVJSHTS","Irene and Edwin Voskamp","01M77K5ZDS7DB0PA1W8FM7G2QD",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FTheVoskamps\u002Fclaude-plugins-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fgithub-setup\u002Fskills\u002Fgh-create-app\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gh-create-app\ndescription: \"Create (from scratch) an org- or enterprise-scoped GitHub App for workflow authentication — walk the UI-gated registration with starter PR-automation permissions, install it on the target repo(s), set App ID + private key as secrets, verify a minted installation token, and save a checked-in metadata doc. Idempotent: detects an already-configured App and offers to verify instead of re-creating.\"\n---\n\nYou are running the `\u002Fgh-create-app` skill. Your job is to provision a\n**new** GitHub App for workflow authentication, scoped at the **org or\nenterprise** level, and wire it up for the current repo:\n\n1. Walk the user through the **UI-gated** App registration (GitHub\n   does not expose an API to create an App from nothing) with the\n   right permissions for the intended automation scope.\n2. Walk the user through **installing** the App on the target repo(s).\n3. **Collect** the App ID and the generated private key.\n4. **Set** them as repo (or org) secrets via `gh secret set`.\n5. **Document** the standard workflow snippet for minting an\n   installation token and exposing it to downstream steps.\n6. **Verify** that a minted installation token can call a\n   representative API as the App.\n7. **Save** App metadata (name, ID, install URL, granted permissions)\n   to a checked-in doc.\n\nThis skill is the **create-from-scratch path** of\n`skills\u002Flib\u002Fgh-app.md`. The find\u002Fverify path (detecting and validating\nan *existing* App) already lives in that library; this skill is what\nthe library's \"no suitable candidates\" branch points users at. When an\nApp already exists, this skill **detects it and offers to verify\nrather than re-create** (see \"Idempotency\").\n\nThere is **no such thing as a per-repo GitHub App.** Apps are owned by\nan organization or an enterprise and *installed onto* repos. The\n`--scope` flag (or the prompt in its absence) chooses org vs.\nenterprise ownership.\n\nThe skill **does not commit** the metadata doc it writes (global rule\n§0: never commit without approval). Remote changes it *does* apply\ndirectly — setting secrets via `gh secret set` — are reported, and\nre-running converges (a secret that is already set is overwritten with\nthe same value, reported as such).\n\n---\n\n## Inputs\n\nAll optional; the skill prompts for anything it needs and cannot\ninfer.\n\n- `--scope=org|enterprise` (no default): ownership scope of the App.\n  In its absence the skill **prompts** (org vs. enterprise) before\n  the registration walkthrough.\n- `--app-name=\u003Cslug>`: the intended App name\u002Fslug. Used for the\n  idempotency check (does an App by this slug already exist and\n  resolve via `skills\u002Flib\u002Fgh-app.md`?) and recorded in the metadata\n  doc. If omitted, the skill asks for it before registration.\n- `--owner=\u003Corg-or-enterprise-slug>`: the org or enterprise login that\n  will own the App. Defaults to the current repo's owner\n  (`gh repo view --json owner -q .owner.login`) for `--scope=org`;\n  prompted for `--scope=enterprise`.\n- `--target-repo=\u003Cowner\u002Frepo>`: the repo to install the App on and set\n  secrets on. Defaults to the current repo\n  (`gh repo view --json nameWithOwner -q .nameWithOwner`).\n- `--secret-scope=repository|organization` (default `repository`):\n  where the App ID and private-key secrets are stored. `organization`\n  sets them as org secrets (shared across repos); `repository` sets\n  them on `--target-repo` only.\n- `--app-id-secret=\u003CNAME>` (default `WORKFLOW_APP_ID`): name of the\n  secret that holds the App ID.\n- `--app-key-secret=\u003CNAME>` (default `WORKFLOW_APP_PRIVATE_KEY`): name\n  of the secret that holds the private key.\n- `--metadata-path=\u003Cpath>` (default `docs\u002Fgithub-app.md`, repo-root\n  relative): where the checked-in metadata doc is written.\n- `--permissions=\u003Cstarter|custom>` (default `starter`): the permission\n  set requested at registration. `starter` is the PR-automation set\n  below; `custom` prompts the user for the scopes.\n\nIf the user passed nothing, use the defaults above and prompt for the\nnon-defaulted required inputs (`--scope`, `--app-name`, and `--owner`\nfor enterprise scope).\n\n### Starter permission set (PR automation)\n\nThe default `--permissions=starter` requests exactly:\n\n| Permission | Access | Why |\n| --- | --- | --- |\n| Pull requests | Read and write | open \u002F approve \u002F merge \u002F label PRs |\n| Contents | Read and write | push branches, create commits |\n| Issues | Read and write | close the issues a merged PR's `Closes #N` lines link |\n| Checks | Read-only | read a commit's check-run results before merging |\n| Commit statuses | Read-only | read a commit's combined status before merging |\n| Metadata | Read-only | mandatory; GitHub auto-selects it |\n\n`Issues: write` is not optional decoration. Merging a PR whose body\ncarries a closing keyword has an **issue-side** side effect, and that\nside effect runs under the *merging* token's authority — so an App\nwith `contents: write` + `pull_requests: write` and no `issues` scope\nmerges the PR successfully and silently leaves every linked issue\nopen. That is the exact half of the closing-keyword convention (PR\nbody only, the branch's own issue set only) that the automation exists\nto deliver.\n\n`Checks: read` and `Commit statuses: read` are what let the App see\nwhether CI passed. `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fcommits\u002F{ref}\u002Fcheck-runs`\nneeds the first and `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fcommits\u002F{ref}\u002Fstatus`\nneeds the second, and the `statusCheckRollup` GraphQL field the\nPR-automation workflows gate on reads both. Those workflows read the\nrollup and make neither REST call, so an App without the two scopes\nfails in the GraphQL shape the first time a merge pass has an open PR\nto evaluate: HTTP 200 carrying a `FORBIDDEN` body error —\n`Resource not accessible by integration` — which exits `gh api\ngraphql` non-zero. HTTP 403 is the REST shape, and it is what a caller\nof either endpoint above gets instead. Both scopes are read-only on an\nApp that already holds write on Pull requests, Contents, and Issues,\nso they widen nothing an operator has not already granted.\n\n**No webhook.** This App mints installation tokens in CI; it does not\nreceive event deliveries. Leave \"Active\" under Webhook **unchecked**\nduring registration.\n\nThe corresponding `required_permissions` map (the shape\n`skills\u002Flib\u002Fgh-app.md` and consuming skills use) is:\n\n```text\n{ pull_requests: write, contents: write, issues: write, checks: read,\n  statuses: read, metadata: read }\n```\n\nFor `--permissions=custom`, ask the user which scopes and levels they\nneed, then carry that map through the walkthrough and the metadata doc\nin place of the starter set.\n\n---\n\n## Step 0: Payload\n\nThe template payloads this skill renders ship with the plugin at\n`${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002Fgh-create-app\u002F`. The placeholder\u002Frender\nconvention is documented in `${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002FREADME.md`.\n\n## Step 1: Pre-flight — repo root, auth, identifiers, inputs\n\nConfirm you are inside a git working tree and capture the root:\n\n```bash\ngit rev-parse --show-toplevel\n```\n\nIf it fails, abort with:\n\n> `\u002Fgh-create-app` must be run from inside a git repository. The\n> current directory is not a git working tree.\n\nConfirm `gh` is authenticated:\n\n```bash\ngh auth status\n```\n\nIf not authenticated, abort and tell the user to run `gh auth login`.\nSetting **org** secrets requires `admin:org`; **enterprise**-scoped\nApp management requires enterprise-owner rights. Note these in the\nabort message when the relevant scope is selected.\n\nResolve identifiers and inputs:\n\n```bash\ngh repo view --json nameWithOwner -q .nameWithOwner   # default --target-repo\ngh repo view --json owner -q .owner.login             # default --owner (org scope)\ngh repo view --json defaultBranchRef -q .defaultBranchRef.name\n```\n\nResolve `--scope` (prompt if absent), `--app-name` (prompt if absent),\nand `--owner` (default for org; prompt for enterprise). Echo the\nresolved configuration back to the user before proceeding:\n\n```text\ngh-create-app — planned configuration\n  Scope:            \u003Corg|enterprise>\n  Owner:            \u003Cowner>\n  App name:         \u003Capp-name>\n  Target repo:      \u003Cowner\u002Frepo>\n  Secret scope:     \u003Crepository|organization>\n  App ID secret:    \u003CAPP_ID_SECRET>\n  Private-key secret: \u003CAPP_KEY_SECRET>\n  Permissions:      \u003Cstarter|custom> → \u003Crequired_permissions map>\n  Metadata doc:     \u003Cmetadata-path>\n```\n\n## Step 2: Idempotency — does a suitable App already exist?\n\nBefore walking the UI, run the **find\u002Fverify** path of\n`skills\u002Flib\u002Fgh-app.md` (Steps 1–4) with\n`required_permissions` = the resolved permission map and\n`target_repo` = `--target-repo`. If an `--app-name` was supplied, use\nthe \"User-supplied App name (skip discovery)\" path from that library.\n\n- **A suitable App is found and installed on the target repo** — do\n  **not** re-create. Report what was found and offer to **verify**\n  instead:\n\n  > GitHub App `\u003Capp_slug>` (ID `\u003Capp_id>`) already exists, has\n  > sufficient permissions, and is installed on `\u003Cowner\u002Frepo>`.\n  > Re-creating would produce a duplicate App. Proceed to verify the\n  > secrets and refresh the metadata doc instead? (Steps 4–7.)\n\n  On confirmation, skip Steps 3 (registration) and go to Step 4 using\n  the existing App's `app_id` \u002F `app_slug`. The skill still needs the\n  private key for the verify step if the secret is not already set —\n  ask the user to generate one in the App settings if so.\n\n- **An App exists by the requested name but is missing permissions or\n  not installed on the repo** — report the gap (the library's \"missing\n  permissions\" \u002F \"not configured for repo\" message) and tell the user\n  to fix it in the App settings, then re-run. Do **not** create a\n  second App with the same intent. For a **missing permission**\n  specifically, relay both steps from `skills\u002Flib\u002Fgh-app.md` →\n  \"Granting a missing permission to an existing App\": the UI-only\n  edit, **and** the approval each installing account must give before\n  the new scope goes live. An App that predates a change to the\n  starter set — one provisioned before `checks: read` and\n  `statuses: read` joined it, say — lands in exactly this branch.\n\n- **No suitable App** — proceed to Step 3 (registration).\n\nThis is the create branch's half of the idempotency contract; the\nfind\u002Fverify half is owned by `skills\u002Flib\u002Fgh-app.md`.\n\n## Step 3: Walk the UI-gated registration\n\nGitHub gates App **creation** behind the web UI; there is no API to\ncreate an App from nothing (see \"Out of scope\"). The skill therefore\n**guides** the user and waits. Print the steps and **halt** for the\nuser to complete them.\n\n### 3a. Open the right \"New GitHub App\" page\n\n- **Org scope:**\n  `https:\u002F\u002Fgithub.com\u002Forganizations\u002F\u003Cowner>\u002Fsettings\u002Fapps\u002Fnew`\n- **Enterprise scope:**\n  `https:\u002F\u002Fgithub.com\u002Fenterprises\u002F\u003Cowner>\u002Fsettings\u002Fapps\u002Fnew`\n\n### 3b. Fill the registration form\n\nTell the user to set:\n\n- **GitHub App name:** `\u003Capp-name>` (must be globally unique; if taken,\n  pick a variant and tell the skill the final slug).\n- **Homepage URL:** the repo URL is fine\n  (`https:\u002F\u002Fgithub.com\u002F\u003Cowner\u002Frepo>`).\n- **Webhook → Active:** **uncheck.** No webhook is needed for\n  token-minting.\n- **Permissions → Repository permissions:** set exactly the resolved\n  map. For the starter set:\n  - Pull requests: **Read and write**\n  - Contents: **Read and write**\n  - Issues: **Read and write**\n  - Checks: **Read-only**\n  - Commit statuses: **Read-only**\n  - Metadata: **Read-only** (auto-selected; leave it)\n- **Where can this GitHub App be installed?** \"Only on this account\"\n  is the right choice for an internal automation App.\n\nThen **Create GitHub App**.\n\n### 3c. Capture the App ID and generate a private key\n\nAfter creation, on the App's settings page:\n\n- Note the **App ID** (a number near the top).\n- Scroll to **Private keys** → **Generate a private key.** The browser\n  downloads a `.pem` file. **Halt** and ask the user for:\n  - the **App ID** (number), and\n  - the **filesystem path** to the downloaded `.pem` file.\n\nDo **not** ask the user to paste the private-key *contents* into the\nconversation. Only the *path* is collected; the key material is piped\nstraight into `gh secret set` via stdin in Step 4 and never printed.\n\n### 3d. Install the App on the target repo(s)\n\nDirect the user to the App's **Install App** tab, install it on\n`\u003Cowner>`, and under \"Repository access\" select **Only select\nrepositories** → `\u003Ctarget-repo>` (or \"All repositories\" if that is the\nintent). **Halt** until the user confirms the install is done.\n\nThen verify the installation programmatically via the user-token path\nfrom `skills\u002Flib\u002Fgh-app.md` Step 4:\n\n```bash\ngh api \"\u002Fuser\u002Finstallations\" --paginate --jq \\\n  '.installations[] | select(.app_slug == \"\u003Capp-slug>\") | .id'\n```\n\n```bash\ngh api \"\u002Fuser\u002Finstallations\u002F\u003Cinstallation_id>\u002Frepositories\" \\\n  --paginate --jq \\\n  '.repositories[] | select(.full_name == \"\u003Cowner\u002Frepo>\") | .full_name'\n```\n\nIf the repo is not listed, report the \"installed on org but not\nconfigured for this repo\" gap from the library and halt for the user\nto fix the App's repository access, then re-check.\n\n## Step 4: Set the App ID and private key as secrets\n\nSet both secrets with `gh secret set`. Pick the org-vs-repo target\nfrom `--secret-scope`.\n\nApp ID (a value, safe to pass on the command line):\n\n```bash\n# repository scope (default)\ngh secret set \u003CAPP_ID_SECRET> --repo \u003Cowner\u002Frepo> --body \"\u003Capp-id>\"\n# organization scope\ngh secret set \u003CAPP_ID_SECRET> --org \u003Cowner> --visibility selected \\\n  --repos \u003Crepo> --body \"\u003Capp-id>\"\n```\n\nPrivate key (read from the `.pem` path via stdin — never expanded into\nargv or the conversation):\n\n```bash\n# repository scope (default)\ngh secret set \u003CAPP_KEY_SECRET> --repo \u003Cowner\u002Frepo> \u003C \"\u003Cpem-path>\"\n# organization scope\ngh secret set \u003CAPP_KEY_SECRET> --org \u003Cowner> --visibility selected \\\n  --repos \u003Crepo> \u003C \"\u003Cpem-path>\"\n```\n\nThe redirect target is quoted so paths with spaces work. `gh secret\nset` overwrites an existing secret of the same name, so re-running is\nconvergent. Report each secret as `set` (and, when it already existed,\n`overwritten`).\n\n## Step 5: Document the token-minting workflow snippet\n\nRead the reference snippet from the payload:\n\n```text\n${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002Fgh-create-app\u002Fapp-auth-snippet.yml\n```\n\nStrip its leading comment block, substitute `__APP_NAME__`,\n`__APP_ID_SECRET__`, and `__APP_PRIVATE_KEY_SECRET__`, and **show** the\nrendered snippet to the user. This skill does **not** write a workflow\nfile — consuming skills (e.g. `\u002Fgh-repo-setup-pr-automation`) own their\nworkflows. The snippet is the canonical pattern those workflows embed:\nmint a short-lived installation token with\n`actions\u002Fcreate-github-app-token`, expose it as `GH_TOKEN` (or pass\n`steps.app-token.outputs.token` to a token input), and do the\nprivileged work as the App.\n\nNever show the snippet with unresolved `__...__` placeholders; if any\nremain, abort per the `${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002FREADME.md`\nunresolved-placeholder rule.\n\n## Step 6: Verify a minted token acts as the App\n\nConfirm the secrets actually mint a working installation token. The\npaths below are in preference order:\n\n**Preferred — local mint with the collected private key.** If the\n`.pem` path is still available this run, mint an installation token\nlocally and call a representative API as the App. Use the App JWT →\ninstallation-token exchange:\n\n```bash\n# Mint a JWT (App auth), exchange for an installation token, call an API.\n# gh supports App auth via `gh api` with a generated JWT; if the local\n# tooling to sign a JWT is not available, fall back to the CI path below.\n```\n\nBecause signing an App JWT locally requires a JWT tool that may not be\npresent, treat the local mint as best-effort. If it succeeds, report\nthe representative call's result (e.g. the repo `full_name`).\n\n**Fallback — CI verification.** If a local mint is not feasible, tell\nthe user to run a one-off workflow (or the snippet from Step 5 in any\nworkflow) and confirm the `Mint App installation token` step succeeds\nand the representative `gh api` call returns. Report the expected\nsuccess signal:\n\n> The `Mint App installation token` step prints a masked token and the\n> `gh api` call returns `\u003Cowner\u002Frepo>`. A failure here means the\n> secrets are wrong or the App is not installed on the repo.\n\nDo not block the skill on the CI run; surface it as the verification\nstep the user performs.\n\n## Step 7: Save the App metadata doc\n\nRender the metadata doc from the payload and write it to\n`--metadata-path` (default `docs\u002Fgithub-app.md`, repo-root relative).\n\n1. Read `${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002Fgh-create-app\u002Fapp-metadata.md`.\n2. Strip its leading HTML comment block (the placeholder documentation).\n3. Substitute every placeholder:\n\n   | Placeholder | Value |\n   | --- | --- |\n   | `__APP_NAME__` | resolved App slug |\n   | `__APP_ID__` | the App ID |\n   | `__APP_OWNER__` | `\u003Cowner>` |\n   | `__APP_SCOPE__` | `organization` or `enterprise` |\n   | `__APP_INSTALL_URL__` | the App settings URL from Step 3a (minus `\u002Fnew`) |\n   | `__APP_PERMISSIONS__` | comma-separated granted permissions (see note) |\n   | `__APP_ID_SECRET__` | `\u003CAPP_ID_SECRET>` |\n   | `__APP_PRIVATE_KEY_SECRET__` | `\u003CAPP_KEY_SECRET>` |\n   | `__SECRET_SCOPE__` | `repository` or `organization` |\n   | `__CREATED_DATE__` | today's date (ISO `YYYY-MM-DD`) |\n\n   The `__APP_PERMISSIONS__` value is an inline, comma-separated\n   string (e.g. `Pull requests: write, Contents: write, Issues: write,\n   Checks: read, Commit statuses: read, Metadata: read`), not a\n   markdown list — the template renders it inside a sentence.\n\n4. **Converge** like the other setup skills: if the target file is\n   absent, write it; if present and **semantically equal** to the\n   render, do nothing and report \"metadata doc already converged\"; if\n   present and different, show the diff and **halt** before\n   overwriting (the doc may carry hand-added notes the render would\n   drop). Whole-file replace, never append.\n\nNever write the doc with unresolved `__...__` placeholders.\n\nThe doc is written **uncommitted**; the user reviews and commits.\n\n## Step 8: Report and next steps\n\n```text\ngh-create-app — \u003Capp-name> (ID \u003Capp-id>), \u003Cscope> scope, owner \u003Cowner>\n\nCreated \u002F configured on GitHub:\n  App:           \u003Capp-name> (ID \u003Capp-id>)        \u003Ccreated|reused existing>\n  Installed on:  \u003Cowner\u002Frepo>                     \u003Cverified>\n  Secrets (\u003Crepository|organization>):\n    \u003CAPP_ID_SECRET>            \u003Cset|overwritten>\n    \u003CAPP_KEY_SECRET>           \u003Cset|overwritten>\n\nUncommitted in this repo (review and commit when ready):\n  \u003Cmetadata-path>                                 \u003Cwritten|unchanged>\n\nGranted permissions: \u003Clist>\n\nNext steps:\n  1. Review the metadata doc:  git diff --stat \u003Cmetadata-path>\n  2. Commit and push when ready (this skill does not commit).\n  3. Use the App in a workflow with the snippet from Step 5\n     (or run \u002Fgh-repo-setup-pr-automation, which wires it in).\n  4. Verify in CI: trigger a workflow using the snippet and confirm\n     the token mints and the representative API call succeeds.\n  5. Re-run \u002Fgh-create-app any time — it detects the existing App and\n     converges (verify + refresh metadata) instead of re-creating.\n```\n\nWhen the App was **reused** rather than created, append the\ncheck-state upgrade note to the report:\n\n```text\n  6. Checks: read and Commit statuses: read joined the starter set\n     after some Apps were registered. If this App predates that, add\n     both in the App's settings AND accept the change on every\n     installation — granting alone leaves it pending and the minted\n     token unchanged.\n```\n\nBoth scopes are read-only, so an operator who reads that note is being\nasked for the two reads and nothing else.\n\n---\n\n## Idempotency (summary)\n\nRe-running this skill on an already-configured App must **detect and\nconverge**, never duplicate:\n\n- **App detection via the library.** Step 2 runs the find\u002Fverify path\n  of `skills\u002Flib\u002Fgh-app.md`. A suitable, installed App short-circuits\n  registration; the skill offers to verify and refresh the metadata\n  doc instead of creating a second App.\n- **Secrets overwrite, not duplicate.** `gh secret set` replaces a\n  secret of the same name, so re-running with the same key is a\n  convergent overwrite.\n- **Metadata doc semantic-compare before write.** An unchanged doc is\n  reported \"unchanged\"; a changed doc halts for review before a\n  whole-file replace, so hand-added notes are never silently dropped.\n- **No second App, ever, by accident.** When an App by the requested\n  name exists but is misconfigured, the skill reports the gap and\n  tells the user to fix the existing App — it does not register a\n  duplicate.\n\n---\n\n## Hard constraints\n\n- **Never attempt to create the App via API.** GitHub gates App\n  creation behind the UI (manifest flow excepted, which is out of\n  scope here). The skill walks the user through the UI and halts; it\n  does not automate creation.\n- **Never print private-key material to the conversation.** Collect\n  only the `.pem` path and pipe it into `gh secret set` via stdin. The\n  `gh secret set \u003CNAME> ... \u003C \"\u003Cpem-path>\"` form is required.\n- **Never commit or push.** The skill writes the metadata doc\n  uncommitted and applies remote changes (secrets, the user's UI\n  actions). The user reviews and commits the doc manually (global rule\n  §0).\n- **Never create a duplicate App.** Run the `skills\u002Flib\u002Fgh-app.md`\n  find\u002Fverify path first (Step 2); a suitable existing App\n  short-circuits registration.\n- **Never skip a halt.** The registration walkthrough (Step 3) has\n  explicit halts for the UI work and the App-ID \u002F key-path collection.\n  A \"looks fine, proceeding\" without explicit user confirmation is not\n  approval.\n- **Never write a file (metadata doc) or show a snippet with\n  unresolved `__...__` placeholders.** Abort per the\n  `${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002FREADME.md` unresolved-placeholder rule.\n- **Never edit anything outside the current repo.** The only on-disk\n  write is the metadata doc under `\u003Crepo-root>\u002F\u003Cmetadata-path>`.\n  Templates are **read** from\n  `${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002Fgh-create-app\u002F` (never written).\n  Scratch work, if any, goes under\n  `\u003Crepo-root>\u002F.claude\u002Ftmp\u002Fgh-create-app\u002F`, never `\u002Ftmp\u002F`, never the\n  user's home directory, never a path outside the repo.\n\n---\n\n## Out of scope\n\n- **Auto-creating the App via API.** GitHub does not expose an API to\n  create a GitHub App from nothing; the App-manifest flow that exists\n  is a separate, heavier mechanism. This skill walks the UI and\n  automates the automatable parts (secrets, verification, metadata).\n- **Rotation automation.** Rotating the App's private key on a\n  schedule is a follow-up concern. The metadata doc documents the\n  manual rotation steps; automating them is out of scope.\n- **The per-user Claude identity App.** A GitHub App that mints a\n  per-user Claude commit identity is a separate sub-issue \u002F design\n  doc, not this skill.\n- **Branch-protection bypass wiring.** Listing the App as a\n  bypass actor in a ruleset is `\u002Fgh-repo-setup-protection`'s \u002F a\n  protection skill's concern; this skill only provisions the App\n  identity and secrets.\n","You are running the `\u002Fgh-create-app` skill. Your job is to provision a\n**new** GitHub App for workflow authentication, scoped at the **org or\nenterprise** level, and wire it up for the current repo:\n\n1. Walk the user through the **UI-gated** App registration (GitHub\n   does not expose an API to create an App from nothing) with the\n   right permissions for the intended automation scope.\n2. Walk the user through **installing** the App on the target repo(s).\n3. **Collect** the App ID and the generated private key.\n4. **Set** them as repo (or org) secrets via `gh secret set`.\n5. **Document** the standard workflow snippet for minting an\n   installation token and exposing it to downstream steps.\n6. **Verify** that a minted installation token can call a\n   representative API as the App.\n7. **Save** App metadata (name, ID, install URL, granted permissions)\n   to a checked-in doc.\n\nThis skill is the **create-from-scratch path** of\n`skills\u002Flib\u002Fgh-app.md`. The find\u002Fverify path (detecting and validating\nan *existing* App) already lives in that library; this skill is what\nthe library's \"no suitable candidates\" branch points users at. When an\nApp already exists, this skill **detects it and offers to verify\nrather than re-create** (see \"Idempotency\").\n\nThere is **no such thing as a per-repo GitHub App.** Apps are owned by\nan organization or an enterprise and *installed onto* repos. The\n`--scope` flag (or the prompt in its absence) chooses org vs.\nenterprise ownership.\n\nThe skill **does not commit** the metadata doc it writes (global rule\n§0: never commit without approval). Remote changes it *does* apply\ndirectly — setting secrets via `gh secret set` — are reported, and\nre-running converges (a secret that is already set is overwritten with\nthe same value, reported as such).\n\n---\n\n## Inputs\n\nAll optional; the skill prompts for anything it needs and cannot\ninfer.\n\n- `--scope=org|enterprise` (no default): ownership scope of the App.\n  In its absence the skill **prompts** (org vs. enterprise) before\n  the registration walkthrough.\n- `--app-name=\u003Cslug>`: the intended App name\u002Fslug. Used for the\n  idempotency check (does an App by this slug already exist and\n  resolve via `skills\u002Flib\u002Fgh-app.md`?) and recorded in the metadata\n  doc. If omitted, the skill asks for it before registration.\n- `--owner=\u003Corg-or-enterprise-slug>`: the org or enterprise login that\n  will own the App. Defaults to the current repo's owner\n  (`gh repo view --json owner -q .owner.login`) for `--scope=org`;\n  prompted for `--scope=enterprise`.\n- `--target-repo=\u003Cowner\u002Frepo>`: the repo to install the App on and set\n  secrets on. Defaults to the current repo\n  (`gh repo view --json nameWithOwner -q .nameWithOwner`).\n- `--secret-scope=repository|organization` (default `repository`):\n  where the App ID and private-key secrets are stored. `organization`\n  sets them as org secrets (shared across repos); `repository` sets\n  them on `--target-repo` only.\n- `--app-id-secret=\u003CNAME>` (default `WORKFLOW_APP_ID`): name of the\n  secret that holds the App ID.\n- `--app-key-secret=\u003CNAME>` (default `WORKFLOW_APP_PRIVATE_KEY`): name\n  of the secret that holds the private key.\n- `--metadata-path=\u003Cpath>` (default `docs\u002Fgithub-app.md`, repo-root\n  relative): where the checked-in metadata doc is written.\n- `--permissions=\u003Cstarter|custom>` (default `starter`): the permission\n  set requested at registration. `starter` is the PR-automation set\n  below; `custom` prompts the user for the scopes.\n\nIf the user passed nothing, use the defaults above and prompt for the\nnon-defaulted required inputs (`--scope`, `--app-name`, and `--owner`\nfor enterprise scope).\n\n### Starter permission set (PR automation)\n\nThe default `--permissions=starter` requests exactly:\n\n| Permission | Access | Why |\n| --- | --- | --- |\n| Pull requests | Read and write | open \u002F approve \u002F merge \u002F label PRs |\n| Contents | Read and write | push branches, create commits |\n| Issues | Read and write | close the issues a merged PR's `Closes #N` lines link |\n| Checks | Read-only | read a commit's check-run results before merging |\n| Commit statuses | Read-only | read a commit's combined status before merging |\n| Metadata | Read-only | mandatory; GitHub auto-selects it |\n\n`Issues: write` is not optional decoration. Merging a PR whose body\ncarries a closing keyword has an **issue-side** side effect, and that\nside effect runs under the *merging* token's authority — so an App\nwith `contents: write` + `pull_requests: write` and no `issues` scope\nmerges the PR successfully and silently leaves every linked issue\nopen. That is the exact half of the closing-keyword convention (PR\nbody only, the branch's own issue set only) that the automation exists\nto deliver.\n\n`Checks: read` and `Commit statuses: read` are what let the App see\nwhether CI passed. `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fcommits\u002F{ref}\u002Fcheck-runs`\nneeds the first and `GET \u002Frepos\u002F{owner}\u002F{repo}\u002Fcommits\u002F{ref}\u002Fstatus`\nneeds the second, and the `statusCheckRollup` GraphQL field the\nPR-automation workflows gate on reads both. Those workflows read the\nrollup and make neither REST call, so an App without the two scopes\nfails in the GraphQL shape the first time a merge pass has an open PR\nto evaluate: HTTP 200 carrying a `FORBIDDEN` body error —\n`Resource not accessible by integration` — which exits `gh api\ngraphql` non-zero. HTTP 403 is the REST shape, and it is what a caller\nof either endpoint above gets instead. Both scopes are read-only on an\nApp that already holds write on Pull requests, Contents, and Issues,\nso they widen nothing an operator has not already granted.\n\n**No webhook.** This App mints installation tokens in CI; it does not\nreceive event deliveries. Leave \"Active\" under Webhook **unchecked**\nduring registration.\n\nThe corresponding `required_permissions` map (the shape\n`skills\u002Flib\u002Fgh-app.md` and consuming skills use) is:\n\n```text\n{ pull_requests: write, contents: write, issues: write, checks: read,\n  statuses: read, metadata: read }\n```\n\nFor `--permissions=custom`, ask the user which scopes and levels they\nneed, then carry that map through the walkthrough and the metadata doc\nin place of the starter set.\n\n---\n\n## Step 0: Payload\n\nThe template payloads this skill renders ship with the plugin at\n`${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002Fgh-create-app\u002F`. The placeholder\u002Frender\nconvention is documented in `${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002FREADME.md`.\n\n## Step 1: Pre-flight — repo root, auth, identifiers, inputs\n\nConfirm you are inside a git working tree and capture the root:\n\n```bash\ngit rev-parse --show-toplevel\n```\n\nIf it fails, abort with:\n\n> `\u002Fgh-create-app` must be run from inside a git repository. The\n> current directory is not a git working tree.\n\nConfirm `gh` is authenticated:\n\n```bash\ngh auth status\n```\n\nIf not authenticated, abort and tell the user to run `gh auth login`.\nSetting **org** secrets requires `admin:org`; **enterprise**-scoped\nApp management requires enterprise-owner rights. Note these in the\nabort message when the relevant scope is selected.\n\nResolve identifiers and inputs:\n\n```bash\ngh repo view --json nameWithOwner -q .nameWithOwner   # default --target-repo\ngh repo view --json owner -q .owner.login             # default --owner (org scope)\ngh repo view --json defaultBranchRef -q .defaultBranchRef.name\n```\n\nResolve `--scope` (prompt if absent), `--app-name` (prompt if absent),\nand `--owner` (default for org; prompt for enterprise). Echo the\nresolved configuration back to the user before proceeding:\n\n```text\ngh-create-app — planned configuration\n  Scope:            \u003Corg|enterprise>\n  Owner:            \u003Cowner>\n  App name:         \u003Capp-name>\n  Target repo:      \u003Cowner\u002Frepo>\n  Secret scope:     \u003Crepository|organization>\n  App ID secret:    \u003CAPP_ID_SECRET>\n  Private-key secret: \u003CAPP_KEY_SECRET>\n  Permissions:      \u003Cstarter|custom> → \u003Crequired_permissions map>\n  Metadata doc:     \u003Cmetadata-path>\n```\n\n## Step 2: Idempotency — does a suitable App already exist?\n\nBefore walking the UI, run the **find\u002Fverify** path of\n`skills\u002Flib\u002Fgh-app.md` (Steps 1–4) with\n`required_permissions` = the resolved permission map and\n`target_repo` = `--target-repo`. If an `--app-name` was supplied, use\nthe \"User-supplied App name (skip discovery)\" path from that library.\n\n- **A suitable App is found and installed on the target repo** — do\n  **not** re-create. Report what was found and offer to **verify**\n  instead:\n\n  > GitHub App `\u003Capp_slug>` (ID `\u003Capp_id>`) already exists, has\n  > sufficient permissions, and is installed on `\u003Cowner\u002Frepo>`.\n  > Re-creating would produce a duplicate App. Proceed to verify the\n  > secrets and refresh the metadata doc instead? (Steps 4–7.)\n\n  On confirmation, skip Steps 3 (registration) and go to Step 4 using\n  the existing App's `app_id` \u002F `app_slug`. The skill still needs the\n  private key for the verify step if the secret is not already set —\n  ask the user to generate one in the App settings if so.\n\n- **An App exists by the requested name but is missing permissions or\n  not installed on the repo** — report the gap (the library's \"missing\n  permissions\" \u002F \"not configured for repo\" message) and tell the user\n  to fix it in the App settings, then re-run. Do **not** create a\n  second App with the same intent. For a **missing permission**\n  specifically, relay both steps from `skills\u002Flib\u002Fgh-app.md` →\n  \"Granting a missing permission to an existing App\": the UI-only\n  edit, **and** the approval each installing account must give before\n  the new scope goes live. An App that predates a change to the\n  starter set — one provisioned before `checks: read` and\n  `statuses: read` joined it, say — lands in exactly this branch.\n\n- **No suitable App** — proceed to Step 3 (registration).\n\nThis is the create branch's half of the idempotency contract; the\nfind\u002Fverify half is owned by `skills\u002Flib\u002Fgh-app.md`.\n\n## Step 3: Walk the UI-gated registration\n\nGitHub gates App **creation** behind the web UI; there is no API to\ncreate an App from nothing (see \"Out of scope\"). The skill therefore\n**guides** the user and waits. Print the steps and **halt** for the\nuser to complete them.\n\n### 3a. Open the right \"New GitHub App\" page\n\n- **Org scope:**\n  `https:\u002F\u002Fgithub.com\u002Forganizations\u002F\u003Cowner>\u002Fsettings\u002Fapps\u002Fnew`\n- **Enterprise scope:**\n  `https:\u002F\u002Fgithub.com\u002Fenterprises\u002F\u003Cowner>\u002Fsettings\u002Fapps\u002Fnew`\n\n### 3b. Fill the registration form\n\nTell the user to set:\n\n- **GitHub App name:** `\u003Capp-name>` (must be globally unique; if taken,\n  pick a variant and tell the skill the final slug).\n- **Homepage URL:** the repo URL is fine\n  (`https:\u002F\u002Fgithub.com\u002F\u003Cowner\u002Frepo>`).\n- **Webhook → Active:** **uncheck.** No webhook is needed for\n  token-minting.\n- **Permissions → Repository permissions:** set exactly the resolved\n  map. For the starter set:\n  - Pull requests: **Read and write**\n  - Contents: **Read and write**\n  - Issues: **Read and write**\n  - Checks: **Read-only**\n  - Commit statuses: **Read-only**\n  - Metadata: **Read-only** (auto-selected; leave it)\n- **Where can this GitHub App be installed?** \"Only on this account\"\n  is the right choice for an internal automation App.\n\nThen **Create GitHub App**.\n\n### 3c. Capture the App ID and generate a private key\n\nAfter creation, on the App's settings page:\n\n- Note the **App ID** (a number near the top).\n- Scroll to **Private keys** → **Generate a private key.** The browser\n  downloads a `.pem` file. **Halt** and ask the user for:\n  - the **App ID** (number), and\n  - the **filesystem path** to the downloaded `.pem` file.\n\nDo **not** ask the user to paste the private-key *contents* into the\nconversation. Only the *path* is collected; the key material is piped\nstraight into `gh secret set` via stdin in Step 4 and never printed.\n\n### 3d. Install the App on the target repo(s)\n\nDirect the user to the App's **Install App** tab, install it on\n`\u003Cowner>`, and under \"Repository access\" select **Only select\nrepositories** → `\u003Ctarget-repo>` (or \"All repositories\" if that is the\nintent). **Halt** until the user confirms the install is done.\n\nThen verify the installation programmatically via the user-token path\nfrom `skills\u002Flib\u002Fgh-app.md` Step 4:\n\n```bash\ngh api \"\u002Fuser\u002Finstallations\" --paginate --jq \\\n  '.installations[] | select(.app_slug == \"\u003Capp-slug>\") | .id'\n```\n\n```bash\ngh api \"\u002Fuser\u002Finstallations\u002F\u003Cinstallation_id>\u002Frepositories\" \\\n  --paginate --jq \\\n  '.repositories[] | select(.full_name == \"\u003Cowner\u002Frepo>\") | .full_name'\n```\n\nIf the repo is not listed, report the \"installed on org but not\nconfigured for this repo\" gap from the library and halt for the user\nto fix the App's repository access, then re-check.\n\n## Step 4: Set the App ID and private key as secrets\n\nSet both secrets with `gh secret set`. Pick the org-vs-repo target\nfrom `--secret-scope`.\n\nApp ID (a value, safe to pass on the command line):\n\n```bash\n# repository scope (default)\ngh secret set \u003CAPP_ID_SECRET> --repo \u003Cowner\u002Frepo> --body \"\u003Capp-id>\"\n# organization scope\ngh secret set \u003CAPP_ID_SECRET> --org \u003Cowner> --visibility selected \\\n  --repos \u003Crepo> --body \"\u003Capp-id>\"\n```\n\nPrivate key (read from the `.pem` path via stdin — never expanded into\nargv or the conversation):\n\n```bash\n# repository scope (default)\ngh secret set \u003CAPP_KEY_SECRET> --repo \u003Cowner\u002Frepo> \u003C \"\u003Cpem-path>\"\n# organization scope\ngh secret set \u003CAPP_KEY_SECRET> --org \u003Cowner> --visibility selected \\\n  --repos \u003Crepo> \u003C \"\u003Cpem-path>\"\n```\n\nThe redirect target is quoted so paths with spaces work. `gh secret\nset` overwrites an existing secret of the same name, so re-running is\nconvergent. Report each secret as `set` (and, when it already existed,\n`overwritten`).\n\n## Step 5: Document the token-minting workflow snippet\n\nRead the reference snippet from the payload:\n\n```text\n${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002Fgh-create-app\u002Fapp-auth-snippet.yml\n```\n\nStrip its leading comment block, substitute `__APP_NAME__`,\n`__APP_ID_SECRET__`, and `__APP_PRIVATE_KEY_SECRET__`, and **show** the\nrendered snippet to the user. This skill does **not** write a workflow\nfile — consuming skills (e.g. `\u002Fgh-repo-setup-pr-automation`) own their\nworkflows. The snippet is the canonical pattern those workflows embed:\nmint a short-lived installation token with\n`actions\u002Fcreate-github-app-token`, expose it as `GH_TOKEN` (or pass\n`steps.app-token.outputs.token` to a token input), and do the\nprivileged work as the App.\n\nNever show the snippet with unresolved `__...__` placeholders; if any\nremain, abort per the `${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002FREADME.md`\nunresolved-placeholder rule.\n\n## Step 6: Verify a minted token acts as the App\n\nConfirm the secrets actually mint a working installation token. The\npaths below are in preference order:\n\n**Preferred — local mint with the collected private key.** If the\n`.pem` path is still available this run, mint an installation token\nlocally and call a representative API as the App. Use the App JWT →\ninstallation-token exchange:\n\n```bash\n# Mint a JWT (App auth), exchange for an installation token, call an API.\n# gh supports App auth via `gh api` with a generated JWT; if the local\n# tooling to sign a JWT is not available, fall back to the CI path below.\n```\n\nBecause signing an App JWT locally requires a JWT tool that may not be\npresent, treat the local mint as best-effort. If it succeeds, report\nthe representative call's result (e.g. the repo `full_name`).\n\n**Fallback — CI verification.** If a local mint is not feasible, tell\nthe user to run a one-off workflow (or the snippet from Step 5 in any\nworkflow) and confirm the `Mint App installation token` step succeeds\nand the representative `gh api` call returns. Report the expected\nsuccess signal:\n\n> The `Mint App installation token` step prints a masked token and the\n> `gh api` call returns `\u003Cowner\u002Frepo>`. A failure here means the\n> secrets are wrong or the App is not installed on the repo.\n\nDo not block the skill on the CI run; surface it as the verification\nstep the user performs.\n\n## Step 7: Save the App metadata doc\n\nRender the metadata doc from the payload and write it to\n`--metadata-path` (default `docs\u002Fgithub-app.md`, repo-root relative).\n\n1. Read `${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002Fgh-create-app\u002Fapp-metadata.md`.\n2. Strip its leading HTML comment block (the placeholder documentation).\n3. Substitute every placeholder:\n\n   | Placeholder | Value |\n   | --- | --- |\n   | `__APP_NAME__` | resolved App slug |\n   | `__APP_ID__` | the App ID |\n   | `__APP_OWNER__` | `\u003Cowner>` |\n   | `__APP_SCOPE__` | `organization` or `enterprise` |\n   | `__APP_INSTALL_URL__` | the App settings URL from Step 3a (minus `\u002Fnew`) |\n   | `__APP_PERMISSIONS__` | comma-separated granted permissions (see note) |\n   | `__APP_ID_SECRET__` | `\u003CAPP_ID_SECRET>` |\n   | `__APP_PRIVATE_KEY_SECRET__` | `\u003CAPP_KEY_SECRET>` |\n   | `__SECRET_SCOPE__` | `repository` or `organization` |\n   | `__CREATED_DATE__` | today's date (ISO `YYYY-MM-DD`) |\n\n   The `__APP_PERMISSIONS__` value is an inline, comma-separated\n   string (e.g. `Pull requests: write, Contents: write, Issues: write,\n   Checks: read, Commit statuses: read, Metadata: read`), not a\n   markdown list — the template renders it inside a sentence.\n\n4. **Converge** like the other setup skills: if the target file is\n   absent, write it; if present and **semantically equal** to the\n   render, do nothing and report \"metadata doc already converged\"; if\n   present and different, show the diff and **halt** before\n   overwriting (the doc may carry hand-added notes the render would\n   drop). Whole-file replace, never append.\n\nNever write the doc with unresolved `__...__` placeholders.\n\nThe doc is written **uncommitted**; the user reviews and commits.\n\n## Step 8: Report and next steps\n\n```text\ngh-create-app — \u003Capp-name> (ID \u003Capp-id>), \u003Cscope> scope, owner \u003Cowner>\n\nCreated \u002F configured on GitHub:\n  App:           \u003Capp-name> (ID \u003Capp-id>)        \u003Ccreated|reused existing>\n  Installed on:  \u003Cowner\u002Frepo>                     \u003Cverified>\n  Secrets (\u003Crepository|organization>):\n    \u003CAPP_ID_SECRET>            \u003Cset|overwritten>\n    \u003CAPP_KEY_SECRET>           \u003Cset|overwritten>\n\nUncommitted in this repo (review and commit when ready):\n  \u003Cmetadata-path>                                 \u003Cwritten|unchanged>\n\nGranted permissions: \u003Clist>\n\nNext steps:\n  1. Review the metadata doc:  git diff --stat \u003Cmetadata-path>\n  2. Commit and push when ready (this skill does not commit).\n  3. Use the App in a workflow with the snippet from Step 5\n     (or run \u002Fgh-repo-setup-pr-automation, which wires it in).\n  4. Verify in CI: trigger a workflow using the snippet and confirm\n     the token mints and the representative API call succeeds.\n  5. Re-run \u002Fgh-create-app any time — it detects the existing App and\n     converges (verify + refresh metadata) instead of re-creating.\n```\n\nWhen the App was **reused** rather than created, append the\ncheck-state upgrade note to the report:\n\n```text\n  6. Checks: read and Commit statuses: read joined the starter set\n     after some Apps were registered. If this App predates that, add\n     both in the App's settings AND accept the change on every\n     installation — granting alone leaves it pending and the minted\n     token unchanged.\n```\n\nBoth scopes are read-only, so an operator who reads that note is being\nasked for the two reads and nothing else.\n\n---\n\n## Idempotency (summary)\n\nRe-running this skill on an already-configured App must **detect and\nconverge**, never duplicate:\n\n- **App detection via the library.** Step 2 runs the find\u002Fverify path\n  of `skills\u002Flib\u002Fgh-app.md`. A suitable, installed App short-circuits\n  registration; the skill offers to verify and refresh the metadata\n  doc instead of creating a second App.\n- **Secrets overwrite, not duplicate.** `gh secret set` replaces a\n  secret of the same name, so re-running with the same key is a\n  convergent overwrite.\n- **Metadata doc semantic-compare before write.** An unchanged doc is\n  reported \"unchanged\"; a changed doc halts for review before a\n  whole-file replace, so hand-added notes are never silently dropped.\n- **No second App, ever, by accident.** When an App by the requested\n  name exists but is misconfigured, the skill reports the gap and\n  tells the user to fix the existing App — it does not register a\n  duplicate.\n\n---\n\n## Hard constraints\n\n- **Never attempt to create the App via API.** GitHub gates App\n  creation behind the UI (manifest flow excepted, which is out of\n  scope here). The skill walks the user through the UI and halts; it\n  does not automate creation.\n- **Never print private-key material to the conversation.** Collect\n  only the `.pem` path and pipe it into `gh secret set` via stdin. The\n  `gh secret set \u003CNAME> ... \u003C \"\u003Cpem-path>\"` form is required.\n- **Never commit or push.** The skill writes the metadata doc\n  uncommitted and applies remote changes (secrets, the user's UI\n  actions). The user reviews and commits the doc manually (global rule\n  §0).\n- **Never create a duplicate App.** Run the `skills\u002Flib\u002Fgh-app.md`\n  find\u002Fverify path first (Step 2); a suitable existing App\n  short-circuits registration.\n- **Never skip a halt.** The registration walkthrough (Step 3) has\n  explicit halts for the UI work and the App-ID \u002F key-path collection.\n  A \"looks fine, proceeding\" without explicit user confirmation is not\n  approval.\n- **Never write a file (metadata doc) or show a snippet with\n  unresolved `__...__` placeholders.** Abort per the\n  `${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002FREADME.md` unresolved-placeholder rule.\n- **Never edit anything outside the current repo.** The only on-disk\n  write is the metadata doc under `\u003Crepo-root>\u002F\u003Cmetadata-path>`.\n  Templates are **read** from\n  `${CLAUDE_PLUGIN_ROOT}\u002Fpayload\u002Fgh-create-app\u002F` (never written).\n  Scratch work, if any, goes under\n  `\u003Crepo-root>\u002F.claude\u002Ftmp\u002Fgh-create-app\u002F`, never `\u002Ftmp\u002F`, never the\n  user's home directory, never a path outside the repo.\n\n---\n\n## Out of scope\n\n- **Auto-creating the App via API.** GitHub does not expose an API to\n  create a GitHub App from nothing; the App-manifest flow that exists\n  is a separate, heavier mechanism. This skill walks the UI and\n  automates the automatable parts (secrets, verification, metadata).\n- **Rotation automation.** Rotating the App's private key on a\n  schedule is a follow-up concern. The metadata doc documents the\n  manual rotation steps; automating them is out of scope.\n- **The per-user Claude identity App.** A GitHub App that mints a\n  per-user Claude commit identity is a separate sub-issue \u002F design\n  doc, not this skill.\n- **Branch-protection bypass wiring.** Listing the App as a\n  bypass actor in a ruleset is `\u002Fgh-repo-setup-protection`'s \u002F a\n  protection skill's concern; this skill only provisions the App\n  identity and secrets.\n",{"name":5,"description":7},"main","4b187366f06afb374243166f6a0f5fc1514fa579","plugins\u002Fgithub-setup\u002Fskills\u002Fgh-create-app","https:\u002F\u002Fgithub.com\u002FTheVoskamps\u002Fclaude-plugins-marketplace","https:\u002F\u002Fgithub.com\u002FTheVoskamps","2026-11-14 13:16:57",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add TheVoskamps\u002Fclaude-plugins-marketplace --skill gh-create-app",{"tool":36,"command":37},"bunx","bunx skills add TheVoskamps\u002Fclaude-plugins-marketplace --skill gh-create-app",{"tool":39,"command":40},"pnpm","pnpm dlx skills add TheVoskamps\u002Fclaude-plugins-marketplace --skill gh-create-app","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheVoskamps\u002Fclaude-plugins-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fgithub-setup\u002Fskills\u002Fgh-create-app\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M77KH3GAXPPXNQS96KDEEZBS","mask-inappropriate-language","Replace inappropriate language (profanity, slurs, strong insults) in provided text or a file with asterisks, character-for-character, preserving everything else.","https:\u002F\u002Fgithub.com\u002FTheVoskamps\u002Fclaude-plugins-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwriting-tools\u002Fskills\u002Fmask-inappropriate-language\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M77KGY5TZDQT8QR23Y0R8P7A","theorem-agents-interface","The interface between the sdlc reviewer and the theorem agents it spawns — what each double-dash brief parameter means, and what each consequence class means. Preloaded into every theorem agent (sdlc:theorem-generator, the disprover, and the verifier) via its skills frontmatter, and read by name by the sdlc:theorem-based-pr-reviewer agent for what its briefs' parameters mean; not invoked from the user's slash menu.","https:\u002F\u002Fgithub.com\u002FTheVoskamps\u002Fclaude-plugins-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Ftheorem-agents-interface\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M77KGT5HW0XAE500WSSM0PZY","sdlc-config-user","Interactively create or merge-update the repo user sdlc config, `\u003Crepo-root>\u002F.sdlc\u002Fuser-config.yml` (tier 3 — this user, this repo, never committed), and add it to the repo's tracked `.gitignore`.","https:\u002F\u002Fgithub.com\u002FTheVoskamps\u002Fclaude-plugins-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fsdlc-config-user\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M77KGQGQVB0NYZX0WJRJPDEK","sdlc-config-repo","Interactively create or merge-update the shared repo sdlc config, `\u003Crepo-root>\u002F.sdlc\u002Frepo-config.yml` (tier 2 — tracked, every user of this repo).","https:\u002F\u002Fgithub.com\u002FTheVoskamps\u002Fclaude-plugins-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fsdlc-config-repo\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M77KGKPEN7C5RCEDSEP3Z1XB","sdlc-config-global","Interactively create or merge-update the global user sdlc config, `$XDG_CONFIG_HOME\u002Fsdlc\u002Fuser-config.yml` (tier 1 — this user, every repo on this machine).","https:\u002F\u002Fgithub.com\u002FTheVoskamps\u002Fclaude-plugins-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fsdlc-config-global\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M77KGFX95J2XEQBBD49QHTXK","pr-read-cli-interface","The contract for sdlc's PR-read CLIs — sdlc-pr-round, sdlc-pr-adjustments, sdlc-fixer-brief and sdlc-records-chain — their arguments, exit codes and output grammar. Preloaded into sdlc:theorem-based-pr-reviewer, sdlc:issue-fixer, sdlc:docs-writer and sdlc:pr-finalizer via their skills frontmatter; not invoked from the user's slash menu.","https:\u002F\u002Fgithub.com\u002FTheVoskamps\u002Fclaude-plugins-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fpr-read-cli-interface\u002FSKILL.md",[],[]]