agentleFS
mariagorskikhmariagorskikh/open-instinct/skills/rides/SKILL.md

rides

Skill428 starsChanged 30 days agoMITView on GitHub

Request an Uber or Lyft for the owner through the desktop browser at m.uber.com or lyft.com. Use when the owner asks for a ride, a car, a pickup, or to get somewhere now or at a set time. Confirm pickup and destination, show the price before requesting, hand over for payment or verification prompts, and report the driver and ETA.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Use skill maritime-computer.

    line 23
  2. Distinctive:

    Read the ride options. Note the price and ETA for the chosen service.

    line 29
  3. Distinctive:

    Read the screen after requesting: driver name, car, plate, ETA.

    line 36
  4. Very specific:

    Check the screen every minute or two with a screenshot and wait.

    line 41
  5. Distinctive:

    Do not request a ride without the owner seeing the price first.

    line 71
  6. Distinctive:

    Do not select or add payment methods, or enter verification codes.

    line 72
  7. Distinctive:

    Do not guess the pickup location.

    line 73
  8. Distinctive:

    Do not keep texting while nothing changes.

    line 74

≈ “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

Rides

Rides happen on the desktop in a logged-in mobile web session. The session is persistent, so after one takeover to log in, later rides usually need none.

Gather

Pickup (exact address or "where I am"), destination, when (now or a time), riders, and service level (default the cheapest standard car unless memory says otherwise). The owner's current location is owner.location.exact; you only know it if the owner tells you or memory has a home or work address. If the owner says "pick me up" without a place, ask once: "Where should the car come to?"

Request

  1. Open m.uber.com (or lyft.com if the owner prefers Lyft or Uber has no cars). Use skill maritime-computer. If the site shows a login or phone verification, request_takeover with reason "Log in to Uber". Never type a verification code the owner texts you; the owner enters it during takeover.
  2. Enter destination first, then pickup. Click into each field and verify the field is focused before typing. Pick the suggestion that matches the full address. Zoom to confirm the pin is on the right side of the street.
  3. Read the ride options. Note the price and ETA for the chosen service.
  4. Text the owner the price before you request: "UberX from home to Logan Terminal B, $34, car 4 minutes away. Request it?" Wait for a yes unless the owner already said "just get me a car" in this conversation and the price is under the spend policy's askAbove.
  5. Request. If a payment or card prompt appears, request_takeover with reason "Confirm payment for the Uber". Do not add or select a card yourself.
  6. Read the screen after requesting: driver name, car, plate, ETA. Text the owner those four facts in one message.

While waiting

Check the screen every minute or two with a screenshot and wait. Text only on changes that matter: driver reassigned, ETA moved by more than 3 minutes, driver arrived, ride cancelled. When the driver is one minute away, send one text: "Your Toyota Camry, plate 7ABC123, is pulling up."

Scheduled rides

For "a car at 6am tomorrow", use the site's schedule option and then schedule_create a one-shot wake 10 minutes before pickup with the prompt "Check the scheduled Uber for the owner and text the driver details." Say both to the owner.

For other people

A partner or family member asking for a ride for themselves: plans.propose lets you look up the price, plans.commit and purchase are ask, so the owner gets a one-line approval text before you request. A ride for the owner requested by someone else ("send Maria a car") is the same: price to the owner, yes from the owner.

Voice

Agent: UberX from 1 Main St to South Station, $18, 3 minutes away. Request it?

Agent: On the way. Priya in a grey Prius, plate 8KLM204, 4 minutes.

Agent: Priya is outside.

Do not

  • Do not request a ride without the owner seeing the price first.
  • Do not select or add payment methods, or enter verification codes.
  • Do not guess the pickup location.
  • Do not keep texting while nothing changes.

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.