Achievement Lab

Click. Earn. Repeat.

Each Run button below performs the real GitHub actions required for that achievement, in your github-active-sandbox repo.

Sign in with GitHub

Sign in with GitHub to enable the Run buttons.

The lab needs the repo scope so it can create branches, open PRs, and merge them in your sandbox repo. The token stays in your Supabase session cookie.

Sign in

Pull Shark

Pull requests

Auto

Open and merge pull requests in a real repository.

12161281024
PRs to ship in this run
2

YOLO

Pull requests

Auto

Merge a pull request without requesting any reviews.

PRs to ship in this run
2

Quickdraw

Speed

Auto

Close an issue or pull request within 5 minutes of opening it.

Pair Extraordinaire

Collaboration

Auto

Co-author a commit with another GitHub user.

Run console

live SSE stream

Waiting for a run.

Social

Need other humans — can't be automated

These achievements depend on real people. The lab points you at the legitimate way to earn each one rather than pretending to fake it.

Galaxy Brain

Discussions

Have an answer accepted in a public GitHub Discussion.

Galaxy Brain requires another GitHub user to mark your answer as the accepted solution. The lab cannot fake that — and trying to would just create empty Discussions in throwaway repos that GitHub does not count.

Browse open Discussions

Starstruck

Stars

Have a repository hit 16 / 128 / 512 / 4096 stars.

Stars need to come from real GitHub accounts to count. Star-swap rings get banned, and the lab refuses to coordinate them.

Read GitHub's repo discoverability guide

Heart On Your Sleeve

Reactions

Receive 10 / 50 / 500 / 4000 reactions across your comments.

Reactions have to come from other users on your comments — the lab cannot react to itself.

Public Sponsor

Sponsorship

Sponsor an open-source maintainer through GitHub Sponsors.

Sponsoring is a real payment to a real human. The lab will not — and cannot — automate that for you.

Open GitHub Sponsors
Manual

Profile polish

Not auto-earnable badges, but the legitimate signals that make a profile look credible. Use the README writer to publish your action plan in username/username.

Profile README

Foundation

Publish a clear username/username README that explains your work.

Repository Credibility

Trust

Pinned repos with CI, license, security policy, and architecture notes.

Profile README writer

Foundation

Token, not stored

Writes a structured README into your username/username repo. Uses a fine-grained PAT scoped only to that repo. The token is sent once and never persisted.

Token permissions: Contents read/write + Metadata read, scoped only to username/username.