cursor-port-github-app-to-origin
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
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- cursor-port-github-app-to-origin
- license
- MIT
- 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.
- compatibility
- Needs network access to https://cursor.com/docs/api/origin/* at run time.
02 资源文件 9
- 许可证LICENSE.upstream1.0 KB
- 参考文档MIRROR.md962 B
- 参考文档references/brief.md6.9 KB
- 参考文档references/runtime/method.md6.0 KB
- 参考文档references/runtime/native-codex.md6.0 KB
- 参考文档references/runtime/original-codex.txt5.6 KB
- 参考文档references/runtime/runtime-files.json573 B
- 参考文档references/runtime/selection.md1.7 KB
- 参考文档references/runtime/t3.md5.0 KB
03 SKILL.md 正文
Runtime selection
Before runtime-dependent work, read execution selection. In a verified T3 host follow the T3 contract and its method reference; the inline section below is the native Codex branch, not literal T3 dispatch. Outside T3, native Codex follows that inline branch unchanged. If the host is ambiguous or a required capability is unavailable, report the gap; a permission refusal never authorizes switching branches.
Native Codex branch
Native Codex boundary
Origin remains the named external product. Fetch the current official public documentation through an available native web surface when this skill is invoked; the mirrored source pin is not a live API contract. Resolve actual capabilities and permissions before any API operation. Do not authenticate, install, create an app, register webhooks, send feedback, publish repository details or migrate code from guidance alone. The porting skill produces a local planning brief; feedback is draft material until explicitly authorized for sending. No connector, provider, credentials, cloud runtime or installation is supplied by this mirror.
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
cursor-origin-api skill for the docs and the rules to check first. Two more rules:
- 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.
- 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
each several hundred kilobytes, too large to read into context whole. Save
them locally if you can, in a temporary location outside the app's
repository so nothing in the working tree is overwritten or left behind,
then search them and read only the matching part:
x-origin-scopes:inopenapi.yamlmarks every operation with its scopes; theoperationIdsits a line above.x-origin-webhook-events:inopenapi.yamlmarks every webhook payload schema with the event slugs that deliver it.### <Endpoint name>and### <Payload type>headings inllms-full.txtstart the section that spells out that endpoint's or payload's fields as dotted paths; read from the heading to the next###.
For a single question later, start at llms.txt and fetch just that
section.
- A matching name is a candidate, not an answer. Read the operation's description, parameters, and response fields against what the code passes and reads. If a parameter or field the code depends on is missing, that is a workaround or a gap, not a match.
- GitHub's pull request calls that live under
/issues/{n}/…(comments, labels) live under the pull request endpoints on Origin. If the code uses them on real issues, see "Where GitHub features live on Origin" inreferences/brief.md. - Origin has no GraphQL. Break each query into REST calls and record the fan-out.
- The scopes to request are the union of
x-origin-scopes.scopesover the operations you named. Do not translate the GitHub manifest. - Each GitHub event and action pair maps to at most one slug in "Events". The action is part of the slug. A pair with no slug is not an event on Origin.
- For each payload field the code reads, record whether it is in the
payload, in the delivery envelope around the payload (
event.typecarries the action), needs an extra read (say which operation and how many calls per event), can be computed from other fields, or is missing. Payloads are snapshots. A field the REST resource has but the payload lacks needs an extra read. - A capability the docs never mention is not available today. Ask the team about it. A behavior the docs neither confirm nor deny gets a question plus a step in the end-to-end test that checks it. Do not assume it works the way it did on GitHub.
Before finishing
Every claim about Origin points at something in the saved docs. Every gap has a feedback entry that names its cost. The feedback reveals nothing about the team's internals. The summary names the native-or-mirror question.
04 同仓库更多 Skills
X MCP guide
ALWAYS read this before using any X tool (the X plugin, any X MCP, or Grok Bot's built-in public X reads) and again on any X error. X tools are included in Grok Bot at no cost: never estimate costs, check credits, or tell the user to buy credits. tools=0 / user-X-* not found is a setup failure, not a paywall. Covers Spaces, communities, and Lists (reads and list writes), X Chat (XChat, inbox, DMs, unread, message requests, Chat PIN, juicebox, xchat_lite: clone xchat-grokbot-helper yourself and decrypt locally), scheduled X calls (schedule_call, list_scheduled_calls and the other call tools), and livestreams (stream sources, broadcasts, scheduled broadcasts, broadcast chat, moderators, mutes). Chat, call, livestream, Spaces, or Lists tools missing while other X tools work: reconnect the X plugin.
X Money guide
Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability. Covers the approval rule for every action that moves money (always ask, every time, no exceptions), how the connection works (connection code plus passkey in the X app), how to guide the user through connect, reconnect, and revoke at x.com/i/money/settings/connections, and what each failure message means.
google-slides
Build and edit Google Slides through the google-slides MCP tools - slides, grids of cards and columns, text boxes, shapes, images, tables, styling, layout inspection, and per-slide PNG rendering. Use when creating a deck, laying out slide elements, matching a template, or verifying how a slide looks.
google-sheets
Build and edit Google Sheets with the google-sheets tools - values, formatting, charts, conditional formatting, structure, validation, named and protected ranges. Use when creating a spreadsheet or dashboard, formatting cells, adding or fixing charts, or reorganizing tabs and rows.
google-drive
Work with Google Drive through its MCP tools - search, read, create, organize, share, comment, and export files. Use when creating files in specific folders, moving or renaming, converting Markdown/CSV into Docs/Sheets, managing comments, or exporting a rendered PDF.
google-docs
Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers/footers. Use when creating a formatted document, editing document content, or applying styles.