agentleFS
Sign inStart free
marslomarslo/skills/origin/SKILL.md

origin

Skill0 starsChanged 2 months agoMITView on GitHub

Install, sign in, update, or repair the origin CLI for repos hosted on Cursor (origin.cursor.com). Use when the CLI is missing or outdated, git push/pull fails to authenticate against origin.cursor.com, or the user asks to set up, clone, or configure Cursor-hosted repos.

  • Pipes a download into a shell
  • Commits and pushes

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If origin is not on PATH but ~/.local/bin/origin exists, invoke it by that absolute path.

    line 35
  2. Distinctive:

    Never ask the user to paste tokens into chat, and never print credentials.

    line 61
  3. Very specific:

    Never run origin repo delete unless the user explicitly asked to delete that repository and has confirmed the exact repo name.

    line 90
  4. Distinctive:

    Never replace or rewrite an existing remote.

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

origin — set up and repair the origin CLI

Cursor hosts git repositories at origin.cursor.com. The origin CLI manages them. This skill covers getting the CLI working and recovering from its common failure states. It does not decide whether to use Cursor-hosted repos — workflow skills and the user do that.

Platform check first

Supported: macOS and Linux (including WSL). On native Windows (outside WSL), Origin repo operations are not supported yet — say so plainly. Do not improvise a Windows install.

1. Detect the current state

command -v origin || { test -x ~/.local/bin/origin && echo ~/.local/bin/origin; }
origin auth status
  • Binary missing → install (step 2), then authenticate (step 3).
  • Binary present but auth status shows no session → authenticate (step 3).
  • Both fine → nothing to set up; continue with whatever you were doing.

If origin is not on PATH but ~/.local/bin/origin exists, invoke it by that absolute path.

2. Install

curl -fsSL https://downloads.cursor.com/origin/install.sh | sh

The installer verifies the download's checksum and symlinks ~/.local/bin/origin. New shells may not have ~/.local/bin on PATH yet — use the absolute path for the rest of the session.

3. Authenticate

origin auth login

This opens the user's browser (the same Cursor login they already have — one click for most users) and configures the git credential helper for origin.cursor.com, so git push/git pull work afterwards with no extra setup. Wait for the command to complete.

  • Headless or SSH session: the CLI prints a login URL instead of opening a browser. Show the user that URL and wait.
  • Never ask the user to paste tokens into chat, and never print credentials. The CLI stores them in the OS keychain / its credentials file.

4. Recover from known failures

Failure signatureFix
origin: command not foundInstall (step 2).
Authentication failed for 'https://origin.cursor.com/...' on git push/pullorigin auth status, then origin auth login, then retry the git command.
No Origin namespace for the account (origin repo create / repo list errors mentioning a missing namespace)Relay the error's own guidance in plain language. For a user on a team, a team admin sets the namespace up at cursor.com/codebase. Do not retry in this session.
Not authorized to access a namespaceThe user's team has Origin, but this account lacks repo access there — a team admin can grant it.
origin auth login never completesThe user has not finished the browser step. Ask them to complete it or re-run the command; do not work around it.

A working installation is never reinstalled. Run origin update only when the CLI's own update hint suggests it; if the update fails, re-run the installer (step 2).

Useful commands once working

  • origin repo clone <org>/<name> — clone a Cursor-hosted repo using the saved login (later git push/pull relies on the credential helper that origin auth login configured).
  • origin repo list — list repos the account can access.
  • origin repo create <name> — create a repo; the CLI resolves the account's namespace automatically, so no org prefix is needed (namespace failures are in the recovery table above).

Hard limits

  • Never run origin repo delete unless the user explicitly asked to delete that repository and has confirmed the exact repo name.
  • Never replace or rewrite an existing remote.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free