slop-date SKILL.md skillA
slop-date from eliza-research/thenetwork is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add eliza-research/thenetwork/slop-date@v1.2.5Pins v1.2.5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- eliza-research/thenetwork
- Path
plugins/claude/skills/slop-date/SKILL.md- Versions recorded
- 5
- Latest version
- v1.2.5, committed Oct 24, 2026
- First version recorded
- Oct 20, 2026
- Size
- 11,305 bytes
- Repository stars
- 67
- License
- none declared
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# slop.date 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. ## Talk like a person 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. 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. ## Existing HTTPS capability Use only https://slop.date/ as this skill's site origin. Every API path below …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_we5fmh5nqdufsvcp/a1723bbdc0b23ff770bea6bf298a2c84f4082c4edf9e49d087a213028134bc7f.json
Then /plugin install slop-date@markdownregistry-we5fmh5nqdufsvcp in Claude Code. It installs v1.2.5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add eliza-research/thenetwork/slop-date@sha256:a1723bbdc0b23ff7The line at the top of this page pins the label v1.2.5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_we5fmh5nqdufsvcp)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in eliza-research/thenetwork/slop-date since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of slop-date from somewhere else? Ask it: where did my slop-date come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Oct 20, 2026 and Oct 24, 2026, about one every day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.5 latest | 2026-10-24 | e17ddd3 | 11,305 B | A | view · diff |
| v1.2.4 | 2026-10-24 | 0f1797a | 10,991 B | A | view · diff |
| v1.2.3 | 2026-10-24 | 650c912 | 10,432 B | A | view · diff |
| v1.1.5 | 2026-10-20 | 3eddebf | 11,991 B | A | view · diff |
| v1.1.5 | 2026-10-20 | 86192f9 | 10,999 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/slop-date/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11305 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
eliza-research/thenetwork · 67 stars · license none declared · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_we5fmh5nqdufsvcp GET https://markdownregistry.com/api/v1/resolve?ref=eliza-research/thenetwork/slop-date GET https://markdownregistry.com/api/v1/blob/a1723bbdc0b23ff770bea6bf298a2c84f4082c4edf9e49d087a213028134bc7f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from eliza-research/thenetwork
Every file in eliza-research/thenetwork