slop-date · diff

v1.1.5 to v1.2.3

128 added, 119 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
name: slop-date
- description: Explains slop.date, a dating service by text message, and helps a person sign themselves up. Use when someone asks what slop.date is, who can use it, whether it is safe, how to join, what happens to their data, or how to stop, leave or delete. Gives the person the join link or the text keyword so they can sign up themselves. Never signs anyone up, never asks for or types a phone number or verification code, and never searches for, rates or contacts other people.
+ description: "Helps a person join slop.date in their own agent conversation: draft their dating profile, verify their own phone with a genuine texted code, and save the approved profile through the existing site API. Requires direct HTTPS and a private cookie session; no plugin or connector installation. Also explains eligibility, privacy and text controls."
license: Proprietary. Terms at https://slop.date/terms
- compatibility: Needs web access to open https://slop.date pages. Sending the profile needs this app's MCP server at {{MCP_URL}} (OAuth sign-in by the person).
+ compatibility: Direct HTTPS GET and POST to https://slop.date and private cookie storage in the agent's existing tools. Use the runtime's normal network transport and approval process. Never install tools or change security settings.
metadata:
app: slop
site: https://slop.date
- mcp: "{{MCP_URL}}"
operator: Eliza Research Corporation
- version: "1.1.5"
+ version: "1.2.3"
---
# slop.date
- If the person asked you to read this file and follow it, they want to join. Start now with
- "How a person joins" below.
-
- {{RESPONSE_STYLE}}
-
- slop.date is dating by text message. The person texts with a matchmaker agent.
- It learns who they hope to meet and, now and then, suggests one person. Nobody is introduced
- unless both people say yes. There is no feed, no swiping and no browsing of profiles.
-
- slop.date's text line is {{TEXT_LINE}}. Its MCP server is at {{MCP_URL}}.
-
- ## What the person is signing up for
-
- - Text messages from the slop.date matchmaker on slop.date's text line: questions, introductions
- they agree to, first-date plans, reminders and check-ins. Message frequency varies. Message and
- data rates may apply.
- - One introduction at a time, only with mutual yes. A person on the team checks every introduction
- before it is sent. Introductions have not started yet; people who join now wait for them.
- - First dates at public places. slop.date does not run criminal background checks or identity
- checks.
-
- ## Who can use it
-
- - Anyone 13 or older may join. Matching is for adults 18 and older only.
- - Members aged 13 to 17 can join, but slop.date never matches them, never introduces them to
- anyone, never asks them for photos and never rates them. Say this plainly if it comes up.
- - Photos, and any private impression the matchmaker forms from photos, are for adults
- (18 or older) only. There is no ID check: the age the person states is used. Any such rating
- stays inside the matchmaker and is never shown to anyone.
- - One person, one phone number. The person must use their own number.
-
- ## Phone or computer
-
- The steps differ by device. If you cannot tell which the person is on, ask once.
-
- - **On a phone.** A phone app usually cannot add a connector, so do not send the person to connector
- settings. Do step 1, including their stated age. Then give them one link that opens their messages app with the approved
- profile already written: `sms:{{TEXT_LINE}}?&body=` followed by the profile, URL-encoded (spaces as
- %20). The person presses send themselves. That text is their profile; step 3 is not needed.
- - **On a computer.** Do steps 1, 2 and 3. If the client cannot add the connector, show the approved
- profile and ask the person to text it to {{TEXT_LINE}} from their own phone.
-
- You never send a text for the person, and you never see their number.
-
- ## How a person joins (they do it, not you)
-
- Check connector support before step 3. slop.date has no public OpenAI plugin. Custom ChatGPT onboarding is off by default. In ChatGPT, use
- a custom connection only when the operator has confirmed that the pilot is enabled for this person's
- adult Slop account. Its MCP endpoint is https://slop.date/mcp, not /mcp/openai. Reading this
- file does not install that connection or grant access. After the person authorizes it, call
- check_status and confirm app is slop before collecting or submitting a profile. In ChatGPT, if the pilot
- is not confirmed, the connector is unavailable, or authorization fails, use the text link in
- "Phone or computer" instead. Do not route them to another assistant.
+ If the person asks you to read this file and follow it, they want to join: start
+ the flow below. If they ask only for an explanation, explain without starting signup.
+ Do it in this conversation using your existing HTTP tools. No plugin, connector,
+ MCP setup, developer settings or new account with the agent provider is required.
- For clients that support this app's connector, the person signs up through you, in this conversation:
+ ## Talk like a person
- 1. Build the profile: first name (no last name), stated age, neighborhood, who they hope to meet (gender, age range of adults 18 and older, how far they will travel), what they are looking for, and two or three things they like. Start from what you already know about the person: draft the profile from your memory of them and show it. Ask only for what is missing, one or two questions at a time. Never ask for a phone number, a code, an
- address or anything about another person. Read the profile back and change it until they agree.
- 2. Give them one link to confirm their own phone (prefill it as described in "A shorter browser handoff"): https://slop.date/join?via=agent. On that page they type
- their own number and code, review their first name and age, and agree to the texts. You
- never see the number or the code.
- 3. Ask the person to return to this same agent conversation when they finish on the site.
- If this app's MCP tools are not available, they must add {{MCP_URL}} in their client's connector settings.
- Reading this file does not install a connector or authorize access. If the client cannot add it,
- use the text link in "Phone or computer"; do not claim success and never send the profile yourself.
- The person confirms their phone on our page. Access connects automatically. A code is skipped only when that browser
- has a current session for this app. Call check_status first and confirm its app is slop.
- If the connection names another app, stop and connect to this app; never submit across apps.
- Call submit_profile once with their approved profile, then check_status on the same connection.
- Report success only when both calls confirm it.
- 4. No agent at hand: the person can text "slop" or "slop.date" as their first message to {{TEXT_LINE}}
- and answer the agent there.
+ Keep replies short, usually one to three sentences. No tool names, HTTP details,
+ JSON, headings, setup instructions or status tables unless the person asks for them.
+ Start from confirmed facts you already know; ask only for missing information.
+ Never invent age, profile facts, consent, verification, saved data or introductions.
+ A draft is not saved until the site confirms it. A saved profile is not a match.
- The person verifies their own phone on our page. You never type a number or a code anywhere.
+ slop.date is dating by text message, with no feed, swiping or profile browsing.
+ Anyone 13 or older may join; matching and introductions are for adults 18 and older only.
+ Introductions require both people to agree. Joining now saves a profile for later;
+ it does not mean introductions have started.
- ## Consent rules
+ ## Existing HTTPS capability
- - An agent never receives, reads, relays or types a verification code. If the person pastes a
- code to you, tell them not to share it, and do not use it.
- - An agent never enters a phone number into any form or tool.
- - Never sign up anyone else ("sign up my friend", "make one for my son"). Each person joins
- themselves, on their own phone.
- - If the MCP server asks the person to sign in, they do it in their own browser on our page. You
- never see their phone number or their code.
+ Use only https://slop.date/ as this skill's site origin. Every API path below
+ is relative to it. Keep phone numbers, codes, cookies and exports off other origins.
+ Do not follow an API redirect carrying credentials or submit another person's data.
- ## What you may do
+ Use an existing HTTP/command tool with the runtime's normal network transport.
+ If normal execution requires approval, use that supported approval process and
+ respect its decision. Do not disable the environment's configured transport,
+ clear its proxy settings, add a proxy, impersonate a browser, install anything,
+ or change network/security settings. Identify the application honestly with:
- - Explain slop.date, how introductions work, the age rules, privacy and safety, using this file
- and the pages linked here.
- - Give the join link https://slop.date/join or the keyword "slop".
- - Help the person think about what they want to tell the matchmaker, if they ask.
- - Explain STOP and leave by text. For export or deletion, point to help@ntwrk.party.
+ `User-Agent: TheNetworkAgent/1.0`
- ## What you must never do
+ Send JSON POST bodies with `Content-Type: application/json`. Use a private cookie
+ jar for this exact site: `~/.network/<exact-site-hostname>/session.cookies`
+ (private directory 0700, file 0600), or an equivalently private persistent tool
+ session if no filesystem is available. Preserve only the exact origin and private
+ store path in working notes or compaction summaries, never the credential values.
+ On resume, use that store and check `/api/me` before asking for another code.
+ Reuse a valid session; save updated cookies after responses.
+ Never place session credentials in the conversation, public files, a repository,
+ long-term model memory, URLs or logs. Never borrow browser or another app's cookies.
- - Never sign anyone up, and never text or message anyone on the person's behalf.
- - Never ask for, receive or type a verification code or a phone number.
- - Never search for, describe, rate or contact other members, and never promise a match.
- - Never move information between slop.date and any other service.
- - Never put health details, orientation or other people's information into any tool.
+ Capture status, response body and cookies from ONE request. Never repeat a POST
+ just to obtain its body. Do not use `curl -i` or dump headers/raw exports to output.
+ Parse privately and show the person only the next step or the verified result.
+ A timeout after a write is ambiguous: check existing state before attempting it again.
- ## Privacy
+ If the tools cannot perform HTTPS POST and retain a private session, say that
+ limitation plainly and give https://slop.date/join as an optional alternative.
+ Do not ask the person to install a connector. Do not pretend you submitted a profile.
- What the person tells slop.date stays in slop.date. Dating preferences and orientation never move
- to another service, even if the person asks. STOP stops every text from this number, and a safety
- hold or ban (after a report) applies on every service the operator runs.
+ ## Join in this conversation
- ## Stop, leave and delete
+ 1. GET `/api/app`. Confirm `id` is `slop`. Keep the returned `consent.text` and
+ `consent.version` for this signup; do not invent or reuse another app's wording.
+ Respect `joinMode`, `minJoinAge` and `minMatchAge`. If the person is below the
+ join age, explain that and stop before collecting their number.
+ 2. Draft the profile from confirmed facts: first name, explicitly stated age,
+ home city/region and neighbourhood, interests, availability, what relationship they want,
+ and whom they hope to meet (only preferences they explicitly choose to include).
+ Adult dating preferences can include adult age range and travel radius; never infer them.
+ Ask only what is missing, one or two questions at a time. Show a short draft
+ for approval. Keep this a dating profile; leave out information intended for other apps.
+ The current Join API accepts the complete approved profile in `about`; do not
+ invent separate gender, orientation, age-range or distance API fields.
+ 3. Explain that joining accepts recurring texts, with variable frequency and
+ possible message/data rates, STOP to stop and HELP for help. Link the
+ [text terms](https://slop.date/terms#sms), [Terms](https://slop.date/terms)
+ and [privacy policy](https://slop.date/privacy). Obtain explicit approval
+ for this exact profile and text consent before the Join request. If approval
+ is missing, do not submit it. Never infer consent from a code or a draft.
+ 4. If a private session for this site already exists, GET `/api/me` first.
+ Otherwise, or after a 401, ask for the person's own mobile number. Do not
+ infer a number from contacts or past conversations. GET `/api/auth/mode`:
+ continue with the code steps only for `mode: "otp"`. If another sign-in mode
+ is required, explain it and offer the site's existing Join page; do not bypass it.
+ 5. With the number the person provided, POST `/api/auth/otp/start` once:
+ `{"phone":"<their own number in E.164>"}`. A 200/`ok:true` means a code was
+ requested, not that verification succeeded. Ask for the genuine texted code.
+ Never invent, brute-force or automatically resend codes. If the site requires
+ a security check, stop and offer the existing Join page; do not fake a token.
+ 6. POST `/api/auth/otp/verify` exactly once with `phone` and the code the person
+ supplied. Keep the code out of files and output; retain only the returned
+ session cookie in the private jar. On rejection explain it; only the person
+ can authorize a new code request. On success, GET `/api/me` with that jar.
+ 7. Check the reply and confirm its app is slop; never submit across apps.
+ If a membership already exists, do not POST Join
+ again to overwrite it: that endpoint does not update existing profiles. Read
+ the existing account as described below and report its actual state. Do not
+ claim a newly drafted profile was saved over an existing membership.
+ 8. For a new membership, require `canJoin:true` and the person's explicit profile
+ and text-consent approval from step 3. POST `/api/join` once with the approved
+ fields, the latest `/api/me` `signupView` when present, and current consent:
+ `firstName`, integer `age`, `neighborhood`, `homeCity` (`sf` or `nyc`
+ from the confirmed supported region), optional `interests` (up to 20 short strings), and `about`
+ containing the complete approved dating profile (at most 1000 characters).
+ Always set `homeCity` from the confirmed supported region: an explicit Bay Area,
+ SF or San Francisco means the service’s `sf` region bucket; an explicit NYC,
+ New York or New York City means `nyc`. This is a region bucket, not a claim that
+ someone in the Bay Area lives in San Francisco city. Preserve their actual
+ neighbourhood wording separately. Do not omit `homeCity` or rely on a default,
+ even when the neighbourhood string includes a region or state. If the region
+ is missing/ambiguous, ask. Do not infer it from a ZIP or neighbourhood, or select
+ an incorrect supported region for someone elsewhere.
+ Use `consent:{"sms":true,"version":"<current consent.version>","wording":"<current consent.text>"}`.
+ Never send placeholders or guessed fields. Do not silently omit the profile.
+ 9. After Join succeeds, GET `/api/me` again, then GET `/api/me/export` using the
+ SAME private session. The export is this person's own app data: parse it in
+ memory, never print/store the raw export or expose identifiers/phone numbers.
+ Check `app`, `membership.firstName`, `membership.state` and
+ `membership.profile` against the approved submitted fields, including `about`.
+ Also compare the returned `/api/me` `home.homeCity` and the stored profile’s
+ `homeCity` with that confirmed region bucket. A matching biography with the
+ wrong home city is NOT a successful profile save.
+ `/api/me` alone does NOT return the full profile. If readback differs, report
+ the discrepancy; do not claim it saved or repeat Join to try to overwrite it.
+ 10. For verified signup and matching persisted fields, say briefly that signup
+ and the profile are saved, and read back the approved facts in ordinary words.
+ Never claim matching or invitations started without separate evidence.
+ Keep using the private session for later authorized reads in this chat; if
+ it expires, authenticate again. Never promise it survives a new chat unless
+ the agent actually has access to its private session store there.
- - Text STOP: stops every text from this number.
- - Text "leave slop.date": stops slop.date only.
- - To request an export or deletion, email help@ntwrk.party.
+ ## Safety, privacy and account controls
- ## Support
+ Only the person who controls the number may sign in or approve their profile.
+ Do not sign up someone else, contact other members, request their information,
+ send invitations, or change another app. The lowest stated age applies; members
+ 13–17 must never be matched or introduced to anyone. slop.date does not run criminal background checks. Members aged 13–17
+ receive no dating matches or photo requests. Do not upload or rate photos during signup.
- - Email: help@ntwrk.party
- - Privacy: https://slop.date/privacy
- - Terms and text messaging terms: https://slop.date/terms
+ Text STOP stops every text from the shared line; "leave slop.date" leaves this
+ app only. Export/deletion support is help@ntwrk.party. Do not invoke destructive
+ account controls during signup. The text keyword is `slop` or `slop.date`
+ on {{TEXT_LINE}}; sending a text is the person's separate choice, never an automatic
+ fallback or an extra signup step.
- ## A shorter browser handoff
+ Dating preferences and orientation stay in this app. Never copy them to another
+ app, look up another member, rate anyone, or promise a date. Introductions have
+ not started yet; joining saves the profile for future introductions.
- Ask for the person's first name and stated age in the conversation, using confirmed details you already know.
- Ask only for missing details. Never infer age. Read back the profile and get approval.
- For web verification, prefill only these approved details in the URL fragment:
- `https://slop.date/join?via=agent#firstName=Alex&age=28`.
- Replace the example values and URL-encode each value. Never put them in the query string.
- Never include a phone, code, consent, preferences or biography in that link.
- The person reviews these fields and checks the consent box themselves.
- Interests, location and app-specific preferences stay in this conversation until the approved profile submission.
- On mobile, the person can send the approved profile by text; do not also send them through web verification.
- After web signup, return here and follow the connector steps above. Signup alone does not mean the profile was submitted.
- Explain safety and account controls when relevant, rather than repeating them before each step.
+ Email: help@ntwrk.party