SkillForge runs in the browser and as a desktop application. The browser is the fastest way to begin. Desktop adds direct access to local skill folders, conflict-aware saving, recovery snapshots, and the Codex or Claude command-line tool already installed and signed in on your computer.
Use the browser without installing
Open the web editor, continue with GitHub, and create a draft. Browser drafts are stored under the signed-in account in the current browser and survive reloads. They are not cross-device cloud sync. Download the resulting SKILL.md when you want to move it into a repository, personal skill directory, or another tool.
Download the Windows application
The current Windows portable build is version 0.2.0. It is served from versioned Vercel Blob storage rather than bundled into every website deployment. The application was launched as a packaged binary and exercised through its create, AI-build, review, and save interface after the renderer was rebuilt to match the website product frame.
Download SkillForge 0.2.0 for Windows. Keep the file name and hash with any managed distribution process. The verified SHA-256 is 071FD149FDEB9249E991C58E9CF7192F1558F09161469A8010EAFE9032BF3C5D.
Connect local AI once
Open Settings and choose Codex or Claude. The selected CLI must already be installed and authenticated. SkillForge uses that tool’s configured default model and does not require users to manage provider endpoints in the editor. The desktop request stages declared content and asks for a structured proposal without exposing the source for mutation.
Open and save a local skill
Choose a trusted skill folder or create a new draft. Supporting files are view-only evidence. Reference examples cannot be saved. When you save the target, SkillForge checks whether the source changed, writes atomically, and records a recovery snapshot. Resolve any conflict rather than replacing an externally edited file.
macOS status
The universal macOS DMG and ZIP were built on macOS for Intel and Apple Silicon. The complete product test suite passed in that environment and the packaged application was exercised. Public distribution still requires Apple Developer signing and notarization. The website does not present an unsigned build as a finished Mac download.
Verify after installation
- Launch the packaged app rather than the source development server.
- Create a draft and confirm the library, editor, reference, and status panes render.
- Run one build through the selected local provider.
- Review and apply a proposal.
- Save to a temporary skill folder, reopen it, and inspect the recovery record.
Report the platform, package version, and exact failing step when something breaks. A successful build configuration is not proof that a packaged desktop application works.