Skip to content

Cursor plugin specification and official plugins

TypeScript

Download the spec to disk and search it; never read it whole

Cursor Agent14989dda0038
diff --git a/origin-apps/README.md b/origin-apps/README.md
index dabd85fd..01151e05 100644
--- a/origin-apps/README.md
+++ b/origin-apps/README.md
@@ -21,7 +21,7 @@ where each comes from on Origin, the scopes to request, an end-to-end test
for your app, feedback for Cursor, and the questions your team has to
decide. It plans. It writes no code unless you ask.
-Both skills fetch the spec at run time and never name an endpoint from memory.
+Both skills read the live spec at run time and never name an endpoint from memory.
## When to use
diff --git a/origin-apps/skills/origin-api/SKILL.md b/origin-apps/skills/origin-api/SKILL.md
index d9094828..eba4eedb 100644
--- a/origin-apps/skills/origin-api/SKILL.md
+++ b/origin-apps/skills/origin-api/SKILL.md
@@ -22,9 +22,11 @@ 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, read `llms.txt` and fetch
-only the section that answers it. Fetch `llms-full.txt` or `openapi.yaml`
-whole when you need all of it, as a porting brief does. Cite `operationId`s
-and section names.
+only the section that answers it. `llms-full.txt` and `openapi.yaml` are
+each several hundred kilobytes, more than a context window holds. When you
+need all of them, as a porting brief does, download them to disk with
+`curl -o` and search with `rg`, reading only the matching sections. Never
+read or paste either file whole. Cite `operationId`s and section names.
## Where to look
diff --git a/origin-apps/skills/port-github-app-to-origin/SKILL.md b/origin-apps/skills/port-github-app-to-origin/SKILL.md
index 082b78bc..fafd2d21 100644
--- a/origin-apps/skills/port-github-app-to-origin/SKILL.md
+++ b/origin-apps/skills/port-github-app-to-origin/SKILL.md
@@ -50,11 +50,21 @@ find.
## How to map
-Fetch `openapi.yaml` and `llms-full.txt` whole. A brief needs all of it.
-`rg -B1 -A4 'x-origin-scopes:' openapi.yaml` lists every operation with its
-scopes. `rg -A3 'x-origin-webhook-events:' openapi.yaml` lists every event
-slug with its payload schema. Each endpoint and each webhook payload type has
-a docs section that spells out its fields as dotted paths.
+A brief needs the whole spec, but the files are too large to read into
+context (about 870 KB and 575 KB). Download them to disk and search them:
+
+```bash
+curl -sSL https://cursor.com/docs/api/origin/openapi.yaml -o openapi.yaml
+curl -sSL https://cursor.com/docs/api/origin/llms-full.txt -o llms-full.txt
+rg -B1 -A4 'x-origin-scopes:' openapi.yaml # every operation with its scopes
+rg -A3 'x-origin-webhook-events:' openapi.yaml # every event slug with its payload schema
+rg -n '^### Get Pull Request$' llms-full.txt # then read to the next ### heading
+```
+
+Read only the sections a match points at. Each endpoint and each webhook
+payload type has a section in `llms-full.txt` that spells out its fields as
+dotted paths. For a single question later, `llms.txt` names the one section
+to fetch.
- A matching name is a candidate, not an answer. Read the operation's
description, parameters, and response fields against what the code passes
@@ -83,6 +93,6 @@ a docs section that spells out its fields as dotted paths.
## Before finishing
-Every claim about Origin points at something in the fetched files. Every gap
+Every claim about Origin points at something in the downloaded files. 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.
diff --git a/origin-apps/skills/port-github-app-to-origin/references/brief.md b/origin-apps/skills/port-github-app-to-origin/references/brief.md
index 34138071..effb33d1 100644
--- a/origin-apps/skills/port-github-app-to-origin/references/brief.md
+++ b/origin-apps/skills/port-github-app-to-origin/references/brief.md
@@ -31,7 +31,7 @@ that has nothing to say. Pick whatever table shape fits the app. A good brief:
Back every claim about the app with `file:line`, or with "from
`<dependency>`" when a library does it for the app. Back every claim about
-Origin with something in the fetched docs. If you want short labels in a
+Origin with something in the downloaded docs. If you want short labels in a
table, use plain ones: works as is, workaround (say the cost), not available
(ask the team), gap (write feedback).
@@ -90,7 +90,7 @@ their internals first.
## Where GitHub features live on Origin
-Check this before calling anything a gap, then confirm in the fetched docs.
+Check this before calling anything a gap, then confirm in the downloaded docs.
This list goes stale; the docs win.
Has an Origin equivalent: install callback parameters → "Installation