Skip to content

Cursor plugin specification and official plugins

TypeScript

Keep forge and fan-out

Cursor Agent7624c3f96079
diff --git a/origin-apps/README.md b/origin-apps/README.md
index 01151e05..272a728d 100644
--- a/origin-apps/README.md
+++ b/origin-apps/README.md
@@ -1,7 +1,7 @@
# Origin Apps
Two skills for building on [Cursor Origin](https://cursor.com/docs/api/origin),
-Cursor's code host. They cover creating an Origin App, calling the API,
+Cursor's code forge. They cover creating an Origin App, calling the API,
receiving webhooks, and moving an existing GitHub App over. The plugin is
skills only, so it runs in Cursor, Claude Code, Codex, and any agent that
reads [Agent Skills](https://agentskills.io).
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 fafd2d21..9951e320 100644
--- a/origin-apps/skills/port-github-app-to-origin/SKILL.md
+++ b/origin-apps/skills/port-github-app-to-origin/SKILL.md
@@ -74,8 +74,8 @@ to fetch.
labels) live under the pull request endpoints on Origin. If the code uses
them on real issues, see "Where GitHub features live on Origin" in
`references/brief.md`.
-- Origin has no GraphQL. Break each query into REST calls and count the calls
- per event.
+- 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.scopes` over 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
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 effb33d1..22173fa6 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
@@ -48,8 +48,8 @@ different identifier, a changed path, filtering on the client, or a marker
the app controls. Often it is the right answer. It becomes a gap, and gets a
feedback entry, when it costs one of these:
-- extra calls per event that grow with repository or activity size, at this
- app's volume;
+- fan-out, meaning extra calls per event, that grows with repository or
+ activity size at this app's volume;
- a possibly wrong answer, such as guessing which check run or comment is the
app's own, inferring a pull request from a SHA that several versions
share, or building a URL whose format the docs do not promise;
@@ -71,7 +71,7 @@ Write one entry per gap, in Origin terms, with nothing that reveals the
team's internals. When there is at least one entry, also write the section
to `ORIGIN-FEEDBACK.md` next to the brief. When there is none, write no file
and say so in one line. The file carries no license header, repository name,
-product name, or mention of another code host. If the docs and observed
+product name, or mention of another forge. If the docs and observed
behavior disagree, put that in a short "Docs questions for Cursor" list at
the end of the feedback, not in the team's questions. A suggested shape: