New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Port GitHub App To Origin

by cursor in cursor/plugins

Plans the port of an existing GitHub App to a Cursor Origin App.

OfficialMITAuto-check passedBackend & APIs

Install Port GitHub App To Origin

skills CLI
$ npx skills add cursor/plugins --skill port-github-app-to-origin -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cursor/plugins port-github-app-to-origin --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/origin-apps/skills/port-github-app-to-origin .claude/skills/port-github-app-to-origin && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
port-github-app-to-origin
GitHub stars
10k
Token cost
~1.3k tokens
SKILL.md length
752 words
Files
2 (incl. references)
Skills in repo
99
Repo updated
First seen
Licence
MIT

At a glance

Plans the port of an existing GitHub App to a Cursor Origin App.

  • Works in 2 steps: Find it in the code, do not ask. Read… → Feedback describes use cases, not the…
  • The task is to bring a GitHub App to Origin
  • SKILL.md covers What to find, How to map and Before finishing
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Port GitHub App To Origin is an agent skill from cursor/plugins, published by the product's own GitHub organization. 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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/brief.md`). Compatibility notes: Needs network access to https://cursor.com/docs/api/origin/ at run time.

It sits in Backend & APIs. It works with GitHub. The repository describes itself as: Cursor plugin specification and official plugins. The licence is MIT.

When your agent uses it

  • The task is to bring a GitHub App to Origin
  • Compare what it uses against the Origin API

Example prompts

  • “Use the port-github-app-to-origin skill to plan the port of an existing GitHub App to a Cursor Origin App”
  • “/port-github-app-to-origin”

Requirements

  • Compatibility (from SKILL.md): Needs network access to https://cursor.com/docs/api/origin/* at run time.

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Find it in the code, do not ask. Read what the app uses out of its
  2. Feedback describes use cases, not the team's code. The team's parts of

What it can do on your machine

Read from SKILL.md and the folder at commit 9f451cf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Needs network access to https://cursor.com/docs/api/origin/* at run time.

    From compatibility in the SKILL.md frontmatter.

Context cost

Port GitHub App To Origin loads about 1.3k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 752 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cursor/plugins at commit 9f451cf, republished under its MIT licence (© cursor). 752 words, ~1,273 tokens.

Download SKILL.mdSave it as .claude/skills/port-github-app-to-origin/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
port-github-app-to-origin
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.
license
MIT

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 origin-api skill for the docs and the rules to check first. Two more rules:

  1. 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.
  2. 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: 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 ###.

For a single question later, start at llms.txt and fetch just that section.

Show full SKILL.md (294 more words)Show less
  • 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" in references/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.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 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.type carries 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.

© cursor, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in origin-apps/skills/port-github-app-to-origin of cursor/plugins.

  • SKILL.md
  • references/brief.md

Open the folder on GitHubat commit 9f451cf

Compare with similar skills

Port GitHub App To Origin next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Port GitHub App To Origin compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Port GitHub App To Origin this skillcursor/plugins10k—~1.3kAutomated safety check: PassMIT
Summarize Activityalpinejs/alpine32k—~1.6kAutomated safety check: NotesMIT
Plugin Release CheckVoidenHQ/voiden1.9k—~857Automated safety check: PassApache-2.0
Repo2skillzhangyanxs/repo2skill246—~3.6kAutomated safety check: PassNone
Ccb DiagnoseSeemSeam/claude_codex_bridge3.5k—~2.1kAutomated safety check: PassCustom licence
Cuga GitHub Issuescuga-project/cuga-agent893—~1.2kAutomated safety check: PassCustom licence

Similar skills

  • Summarize Activity

    alpinejs/alpine

    Summarize recent GitHub activity — discussions, PRs, issues, events, traffic — into an actionable report so you can stay on top of the project without reading everything.

    32k GitHub stars~1.6k tokensUpdated 2 days ago
    Backend & APIsAuto-check: notes

  • Plugin Release Check

    VoidenHQ/voiden

    A skill your agent uses whenever a plugin under plugins/<name is updated/pushed, or whenever asked to write a changelog/release for the app or a plugin.

    1.9k GitHub stars~857 tokensUpdated today
    Backend & APIsAuto-check passed

  • Repo2skill

    zhangyanxs/repo2skill

    Convert GitHub/GitLab/Gitee repositories into comprehensive OpenCode Skills using embedded LLM calls with multiple mirrors and rate limit handling

    246 GitHub stars~3.6k tokensUpdated 7 mo ago
    Backend & APIsAuto-check passed

  • Ccb Diagnose

    SeemSeam/claude_codex_bridge

    Diagnose a named CCB agent by combining authoritative runtime and job lineage with deep read-only pane inspection, apply bounded recovery when evidence supports it, verify the result, and request…

    3.5k GitHub stars~2.1k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Cuga GitHub Issues

    cuga-project/cuga-agent

    Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking.

    893 GitHub stars~1.2k tokensUpdated today
    Backend & APIsAuto-check passed

  • Jwx Guide V4

    lestrrat-go/jwx

    Guide for developing Go applications with github.com/lestrrat-go/jwx v4 — parse/sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid the common footguns.

    2.4k GitHub stars~5.3k tokensUpdated today
    Backend & APIsAuto-check passed

More from cursor/plugins

All 99 skills in this repo

  • Show Me Your Work Decision Log

    cursor/plugins

    Official

    Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.

    10k GitHub starsUsed in 9 repos~1.6k tokens
    Auto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    Auto-check passed

  • Reflect on Session Learnings

    cursor/plugins

    Official

    Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.

    10k GitHub starsUsed in 5 repos~1.2k tokens
    Auto-check passed

  • Technical Writing Standard

    cursor/plugins

    Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    10k GitHub starsUsed in 10 repos~2.4k tokens
    Auto-check passed

  • Advisor Mode

    cursor/plugins

    Official

    Adds a second, stronger model that the main agent consults before major decisions, when stuck and before finishing, controlled by /advisor commands.

    10k GitHub stars~2.6k tokensUpdated today
    Auto-check: notes

  • Make PR Easy To Review

    cursor/plugins

    Official

    Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior.

    10k GitHub starsUsed in 3 repos~569 tokens
    Auto-check passed

Works with

Categories

Questions about Port GitHub App To Origin

What does Port GitHub App To Origin do?

Plans the port of an existing GitHub App to a Cursor Origin App. Port GitHub App To Origin is an agent skill from cursor/plugins, published by the product's own GitHub organization. Plans the port of an existing GitHub App to a Cursor Origin App.

When should I use Port GitHub App To Origin?

Port GitHub App To Origin fits situations like: the task is to bring a GitHub App to Origin; compare what it uses against the Origin API.

How do I install Port GitHub App To Origin in Claude Code?

Run `npx skills add cursor/plugins --skill port-github-app-to-origin -a claude-code`. Or copy the skill folder (origin-apps/skills/port-github-app-to-origin in cursor/plugins) into .claude/skills/port-github-app-to-origin in your project. Claude Code loads it when a task matches its description.

How do I install Port GitHub App To Origin in Codex?

Run `npx skills add cursor/plugins --skill port-github-app-to-origin -a codex`. Or copy the skill folder (origin-apps/skills/port-github-app-to-origin in cursor/plugins) into .agents/skills/port-github-app-to-origin in your project. Codex loads it when a task matches its description.

Can I use Port GitHub App To Origin in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cursor/plugins --skill port-github-app-to-origin -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/port-github-app-to-origin, .gemini/skills/port-github-app-to-origin, .github/skills/port-github-app-to-origin and .opencode/skills/port-github-app-to-origin in your project.

What does Port GitHub App To Origin need to run?

SKILL.md names no scripts, command-line tools or credentials: Port GitHub App To Origin is instructions for the agent only. Compatibility (from SKILL.md): Needs network access to https://cursor.com/docs/api/origin/* at run time..

Does Port GitHub App To Origin access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Port GitHub App To Origin safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Port GitHub App To Origin use?

Port GitHub App To Origin is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Port GitHub App To Origin use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Port GitHub App To Origin?

Skills that share tags, products or a category with Port GitHub App To Origin: Summarize Activity (alpinejs/alpine, 32k stars), Plugin Release Check (VoidenHQ/voiden, 1.9k stars), Repo2skill (zhangyanxs/repo2skill, 246 stars) and Ccb Diagnose (SeemSeam/claude_codex_bridge, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Port GitHub App To Origin?

cursor (a GitHub organization, an official publisher) maintains it in cursor/plugins, which has 10,130 GitHub stars. The repository holds 99 skills in this directory. The repository was last updated on October 6, 2026.

Source: cursor/plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.