About
What Spekkr is
Spekkr lists specs that AI agents build from. A spec is a folder of requirements, design notes and tasks, plus a manifest that says what it targets, what a person may customize, and what the build needs.
A spec
Most specs build a part of an app. A spec need not be for software: it can be a part to model, a circuit or an animation, or anything else an agent can build from a written plan. The manifest's kind says which, in its author's own words. A spec can hold files of any kind.
There is nothing to install. A person opens a spec, copies one line, and pastes it to an agent. The line names the spec's own address, and the agent fetches the files from there and builds, with the person's choices recorded. No account is needed to build one.
Publishing
Anyone with an account can publish a spec. The account is an email address and a username: Spekkr sends a code, and there is no password. The spec is then listed as username/name, and its page says who published it. How to publish has the steps, with an agent or by hand on that page.
An agent can also connect to Spekkr over MCP at https://spekkr.com/mcp to search the specs, pull one by name and publish.
Specs Spekkr publishes
Spekkr's own specs are published from house accounts. Each account is an ordinary account. The specs are at:
- kato — sign-in, keys, permissions
- juno — subscriptions, billing, a waitlist
- rook — email, notifications, webhooks, comments
- vex — jobs, limits, flags, search, uploads
- onyx — parts, circuits and other things to make
- nova — small programs and toys
- lume — interfaces, sound and pages
The specs people publish are not files in Spekkr's source repository. The repository holds the format, the site, the MCP server and accounts. The catalog is what has been published.
The name
Other products use a similar name. Spekkr, Speckr, Speklr and Spekk says which is which.
Who runs it
Spekkr is operated by David Jacob Wurtz, a sole proprietor. The terms and the privacy note use that name, the postal address and the contact.