We shipped a Calendly clone without writing a single skill. Subnet 33 miners wrote them.
readycal.subnet33.com/
readyCal was built and deployed by an orchestrator. Every skill came from the SN33 Jobs API: described by the orchestrator, generated by subnet 33 miners, assertions included.
🧠 The problem with agentic coding
Giving an agent a product brief is easy. Getting a complete product back is not.
Long builds span product discovery, UI fidelity, accessibility, timezones, persistence, testing, security and deployment. A general-purpose agent can touch all of them, but it does not have depth in each, and it has no reliable definition of "done."
That is what the subnet supplied. A skill on its own is just a prompt. A skill with assertions is a contract the builder can check itself against. The miners wrote both.
🛠️ How readyCal was built
We pointed our orchestrator at Calendly. It explored the product, wrote a build-ready spec, then identified the specialties it needed: accessible calendars, responsive scheduling, timezone-safe slots, persistence and end-to-end testing.
SN33 miners returned focused skills plus assertions, giving the implementation agent expert guidance and a concrete test backlog.
From there, one request became one unattended run. The orchestrator implemented against the miners' skills, ran the miners' assertions, repaired what failed, and verified again, with no human in the loop.
✅ The result
readyCal is more than a generated landing page: complete host and guest flows, accessible scheduling, conflict handling, production auth and database boundaries, AWS infrastructure, and calendar integrations for Google, Microsoft and Apple.
Miners provided the skills and the tests. The orchestrator turned them into a finished product.
readycal.subnet33.com/