Cursor plugin specification and official plugins
TypeScript
Describe doc access without naming tools; save specs outside the repo
Cursor Agent5dda5041a4e1
diff --git a/origin-apps/skills/origin-api/SKILL.md b/origin-apps/skills/origin-api/SKILL.mdindex 29959107..a791bc45 100644--- a/origin-apps/skills/origin-api/SKILL.md+++ b/origin-apps/skills/origin-api/SKILL.md@@ -21,12 +21,13 @@ The docs live under `https://cursor.com/docs/api/origin/`. `llms.txt` isthe 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. `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.+`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+`operationId`s and section names.## Where to lookdiff --git a/origin-apps/skills/port-github-app-to-origin/SKILL.md b/origin-apps/skills/port-github-app-to-origin/SKILL.mdindex f43a24ea..0002dcf4 100644--- a/origin-apps/skills/port-github-app-to-origin/SKILL.md+++ b/origin-apps/skills/port-github-app-to-origin/SKILL.md@@ -50,23 +50,22 @@ find.## How to map-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:+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:-```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-```+- `x-origin-scopes:` in `openapi.yaml` marks every operation with its+ scopes; the `operationId` sits a line above.+- `x-origin-webhook-events:` in `openapi.yaml` marks every webhook payload+ schema with the event slugs that deliver it.+- `### <Endpoint name>` and `### <Payload type>` headings in `llms-full.txt`+ start the section that spells out that endpoint's or payload's fields as+ dotted paths; read from the heading to the next `###`.-Read only the sections a match points at. Do not open `openapi.yaml` or-`llms-full.txt` with a plain file read; file readers stop after about 50 KB,-so find the line with `rg -n` and read that line range. 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.+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'sdescription, parameters, and response fields against what the code passes@@ -95,6 +94,6 @@ to fetch.## Before finishing-Every claim about Origin points at something in the downloaded files. Every gap+Every claim about Origin points at something in the saved docs. Every gaphas a feedback entry that names its cost. The feedback reveals nothing aboutthe 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.mdindex 22173fa6..4117c4f4 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 downloaded docs. If you want short labels in a+Origin with something in the saved docs. If you want short labels in atable, 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 downloaded docs.+Check this before calling anything a gap, then confirm in the saved docs.This list goes stale; the docs win.Has an Origin equivalent: install callback parameters → "Installation