OneRun

What the company appears to be: OneRun is a tool that allows users to convert successful AI workflows into portable Codex Skills using a structured pipeline of extraction, testing, repair, and export. It is built as a web application using Next.js, TypeScript, and Tailwind CSS, with GPT-5.6 as its core AI engine.

What changed: The author describes building OneRun as an experiment in treating AI workflows like code compilation, applying software engineering discipline to prompt engineering. The project was submitted to the OpenAI 2026 hackathon.

Single most important open question: Is there a market need for converting AI workflows into portable, testable skills, or is this primarily a proof-of-concept?

The description states that OneRun takes a workflow description and examples, then packages it into a portable Codex Skill. It compiles the skill into real files (SKILL.md, examples, tests, README), runs automated tests, grades output, and repairs broken skills before exporting as ZIP.

• Evidenced: Yes
• Inferred: No

The author positions OneRun as a tool that turns “great chat sessions” into real software by applying standard software engineering practices to AI workflows. It claims to bring structure and reliability to prompt engineering through a five-stage pipeline (Extract → Test → Repair → Export).

• Evidenced: Yes
• Inferred: No

The description does not state who the target customer is or what their specific needs are.

• Evidenced: No
• Inferred: No

There is no evidence in the description of a business model or pricing structure.

• Evidenced: No
• Inferred: No

OneRun is built with Next.js, TypeScript, Tailwind CSS, and uses GPT-5.6 via OpenAI’s Responses API with Zod schemas for validation. It includes:

• 57 unit tests
• 1 Playwright end-to-end test
• Mock mode for demos without API keys
• Structured handling of AI calls behind a single module
• Timeout handling for latency issues

• Evidenced: Yes
• Inferred: No

There is no evidence of revenue, customers, or adoption beyond the author’s own development and demo.

• Evidenced: No
• Inferred: No

The description does not mention any competitors or how OneRun fits into existing AI workflow tools or Codex ecosystems.

• Evidenced: No
• Inferred: No

• The project is described as a hackathon submission, suggesting it may be experimental or incomplete.
• There is no evidence of market traction, user feedback, or commercial viability.
• The tool relies heavily on GPT-5.6 and OpenAI APIs, which could pose dependency risks.
• No mention of scalability, persistence, or long-term sustainability.

• Evidenced: Yes
• Inferred: Yes

1. What specific problem are you solving for users beyond the hackathon demo?
2. How do you plan to monetize this tool if it's not just a prototype?
3. Have you validated demand from potential users or customers?
4. What is your roadmap for moving from a demo to a production-ready product?
5. Are there any technical dependencies that could limit scalability or performance?

• Evidenced: No
• Inferred: Yes