For courses, hackathons and student groups

Every team gets asked what the AI did and what they did. On a submission form, in a judging rubric, or out loud at the demo. Then the event ends, that answer stays wherever it was collected, and the repo goes on without it.

One of those repos is the next real product. Nobody can tell which, because they're never lined up anywhere with that answer attached.

What listing does

The same answer, kept with the code as a six-line file: what the AI did, what the humans did, which event, who. A page for your event or course at https://slopscore.org/b/{your-event} that reads those files and shows what students actually built, next to every other event's projects, and keeps updating as the repos grow. Attribution that exists before anyone needs it.

It works whether submissions come through a hackathon platform, a form, or a repository link, because the file lives in the repo, not the form.

How, in one paste

The short way: tell the agent that wrote the code, "add a slopscore file per slopscore.org". It reads https://slopscore.org/skill.md and commits the file. The long way is the same six lines by hand, at the root of the public repo:

---
slopscore: 2
spec: https://slopscore.org/spec
ai_generated: entirely
human_touch: light
content_rating: everyone
contains: []
category: [cli]
status: works-on-my-machine
slopbucket: [your-event-2026]   # the event, course or school: one line, and the page exists
maintainers: [teammate1, teammate2]   # GitHub logins; everyone on the team gets owner controls
---

The crawler finds it within the hour and lists the project in the bucket. Not sure what to put? Seven questions and it drafts the file for you.

For the organiser

1. Pick a bucket name before the event: hackrumble-2026, cs-3400-fall, your-school. Short, lowercase, hyphens. Nothing to register; the bucket exists the moment the first file names it.
2. Put one line wherever you collect submissions: "Add a slopscore.md to your repo with slopbucket: [your-bucket]."
3. Tell us the name and the dates, and a moderator gives the bucket a title and a blurb so the page says what it is.

That's the whole job. The school owes nothing, signs nothing, and installs nothing. If a course wants its own page and a hackathon wants another, use two bucket names; a repo can carry up to three.

Running a contest

A contest is a bucket with a deadline. Projects that land in it before the closing date are the field; the bucket page is the standings. Ranking on this site is public and the rules behind it are published: votes from logged-in people, weighted by account trust, plus the site's own critics at half weight, which never pick winners. Organisers judge however they like on top of that; the page is the shortlist, not the verdict.

Ask about a contest and we'll set the bucket up with the dates on it and a line that says who's running it and what the prize is.

What it costs

Nothing. No accounts for students, no forms, nothing to install. The site is open source. Delete the file and the listing goes with it on the next check.

What stays out

Private repos (the crawler can only read public ones). Repos without a licence. Anything that fails the content gates: the rules are public and every rejection has a public reason. Nothing here is graded by a detector; the file is the ticket in, and what it says is up to the team.

Say hello

Running an event or teaching a course? Write to hello@slopscore.org with the bucket name and the dates, or use the contact form. If you want the longer answer to "why", it's in the manifesto.