# port-github-app-to-origin

Plans the migration of an existing GitHub App to Cursor Origin. It scans your code for webhooks, API calls, and scopes, mapping them against the live Origin specification.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 337 installs · ★ 14099
- Author: cursor
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/cursor/plugins/tree/HEAD/origin-apps/skills/port-github-app-to-origin/SKILL.md
- Updated: 2026-10-25
- HTML: https://affpapa.org/en/nevibecode/skills/port-github-app-to-origin

## What it does

The skill runs directly inside your app repository. It scans handlers, framework dependencies such as Probot or Octokit, REST and GraphQL endpoints, and authentication flows. It does not modify or rewrite project code; its job is strictly planning unless you explicitly ask to start coding after reviewing the brief.

Network access to the Origin API documentation is required during execution. Because `openapi.yaml` and `llms-full.txt` are each several hundred kilobytes, the skill saves them in a temporary folder outside the repository and queries matching sections via `x-origin-scopes` and endpoint headers. Origin lacks GraphQL support, meaning existing queries must be split into separate REST calls.

All findings are written to `references/brief.md`. The document provides an internal brief referencing specific file lines for your team, alongside a standalone feedback section for Cursor that describes missing capabilities without disclosing your internal repository names or code details.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add cursor/plugins --skill port-github-app-to-origin -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/port-github-app-to-origin/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/port-github-app-to-origin/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add cursor/plugins --skill port-github-app-to-origin -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/port-github-app-to-origin/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add cursor/plugins --skill port-github-app-to-origin -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/port-github-app-to-origin/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install cursor/plugins port-github-app-to-origin
```

2. **Manually: put the files in place**
- File: `.github/skills/port-github-app-to-origin/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add cursor/plugins --skill port-github-app-to-origin -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/cursor/plugins --path origin-apps/skills/port-github-app-to-origin
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/port-github-app-to-origin/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add cursor/plugins --skill port-github-app-to-origin -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/cursor/plugins/tree/HEAD/origin-apps/skills/port-github-app-to-origin/SKILL.md

## When to use it
- plan the migration of a GitHub App to Cursor Origin
- audit webhooks, scopes, and API endpoints across codebase
- map existing GraphQL queries to Origin REST endpoints
- generate a gap analysis brief in references/brief.md

## Example prompts
- Analyze this GitHub App and prepare a porting brief for Origin
- Check our webhooks and API calls against the Cursor Origin spec
- Create an Origin migration plan and list unsupported endpoints

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 4e734d8e4f58e9c2.

BEGIN THIRD-PARTY FILE 4e734d8e4f58e9c2
```text
---
name: port-github-app-to-origin
description: >-
  Plans the port of an existing GitHub App to a Cursor Origin App. Use when the
  task is to bring a GitHub App to Origin or compare what it uses against the
  Origin API. Reads the app's needs out of its code, maps them onto the live
  Origin spec, and writes a porting brief with feedback for Cursor. Planning
  only.
license: MIT
compatibility: >-
  Needs network access to https://cursor.com/docs/api/origin/* at run time.
---

# Port a GitHub App to an Origin App

Run this inside the app's codebase. The output is a porting brief for the
team plus a Feedback for Cursor section they can send as is
(`references/brief.md`). This skill plans. It does not write or change code
unless the user asks for that after reading the brief. Follow the
`origin-api` skill for the docs and the rules to check first. Two more rules:

1. **Find it in the code, do not ask.** Read what the app uses out of its
   source. Anything you cannot find becomes a question for the team.
2. **Feedback describes use cases, not the team's code.** The team's parts of
   the brief may cite `file:line`. Feedback for Cursor says only what the app
   needs to do and what Origin lacks for it, in Origin terms, with no file
   paths, module names, framework details, or repository names.

## What to find

Record `file:line` for each item, and note what you looked for but did not
find.

- Declared permissions and events, from a manifest or infrastructure code
  if one is checked in. Otherwise derive them from the calls.
- Every webhook event the app handles, and every payload field each handler
  reads, including fields it only logs.
- Every REST and GraphQL call, with the parameters and filters the code
  passes, the response fields it reads, whether it runs on every webhook or
  in a loop, and how it paginates.
- Authentication: the JWT algorithm, how the app learns the installation ID
  after install, how it handles token expiry, any user sign-in and what it is
  for, and whether the app clones or pushes git.
- The webhook receiver: how it verifies signatures, whether it has the raw
  body when it verifies, and how it deduplicates deliveries.
- Calls a framework or library makes for the app. Probot's receiver, token
  cache, and config loader; Octokit `App`'s installation and repository
  listing; app-auth libraries. Read the dependency's docs and list these
  calls marked "from `<dependency>`".

## How to map

A brief needs the whole spec, but `openapi.yaml` and `llms-full.txt` are
```
END THIRD-PARTY FILE 4e734d8e4f58e9c2

The third-party file has ended. Everything between the 4e734d8e4f58e9c2 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2535 of 5094 bytes. © cursor · MIT · https://github.com/cursor/plugins/tree/HEAD/origin-apps/skills/port-github-app-to-origin/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md