cursor-origin-api
Routes questions about the Cursor Origin API to the right section of the Origin docs and names the few rules to check first. Use when a task mentions Origin, the Origin API, Origin Apps, or Origin webhooks, including creating an Origin App, authenticating as one, calling Origin endpoints, or handling Origin webhook deliveries.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- cursor-origin-api
- license
- MIT
- description
- Routes questions about the Cursor Origin API to the right section of the Origin docs and names the few rules to check first. Use when a task mentions Origin, the Origin API, Origin Apps, or Origin webhooks, including creating an Origin App, authenticating as one, calling Origin endpoints, or handling Origin webhook deliveries.
- compatibility
- Needs network access to https://cursor.com/docs/api/origin/* at run time.
02 资源文件 8
- 许可证LICENSE.upstream1.0 KB
- 参考文档MIRROR.md932 B
- 参考文档references/runtime/method.md3.7 KB
- 参考文档references/runtime/native-codex.md3.7 KB
- 参考文档references/runtime/original-codex.txt3.4 KB
- 参考文档references/runtime/runtime-files.json558 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.
Origin API
The docs are the source of truth. Do not name an endpoint, scope, event slug, header, or limit from memory. Where this file and the docs disagree, the docs win.
The docs live under https://cursor.com/docs/api/origin/. llms.txt is
the index and links every section, endpoint, and webhook payload.
openapi.yaml is the contract, and "Endpoint reference" explains its
x-origin-* extensions. llms-full.txt is the whole reference in one file.
changelog says what moved. For one question, start at llms.txt and
fetch only the section that answers it. llms-full.txt and openapi.yaml
are each several hundred kilobytes, too large to read into context whole.
When you need all of them, as a porting brief does, save them locally if you
can, outside any repository you are working in, search them for the section
heading or annotation you need, and read only the matching part. Cite
operationIds and section names.
Rules to check first
- Native or mirror. A repository is either native (created on Origin)
or a GitHub mirror. On a native repository an installation has its full
scopes and every write. On a GitHub mirror, every event except
repository.pushedstill arrives, every call beyond metadata and contents reads returns403, and merging a pull request or changing the default branch is not available ("Mirrored repositories", "Events"). - Subscribe. Only
installation.*events arrive without a subscription. A missing subscription produces silence, not an error ("Events"). - Verify, dedupe, acknowledge. Verify the signature over the raw body
before parsing, dedupe on the delivery ID, return
2xx, then process ("Signature verification", "Retries", "Automatic disable"). Origin signs a digest, which Standard Webhooks does not, so a generic verifier fails. - Scopes from the spec. Request the union of
x-origin-scopes.scopesover the operations the app calls ("Scopes"). - Opaque tokens and IDs. Do not build or parse page tokens or IDs ("Pagination", "IDs").
One section name the index does not make obvious: what happens to a check-run post that arrives out of order is under "Ordering writes".
Porting an existing GitHub App: use cursor-port-github-app-to-origin in this
plugin.
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.