← ClaudeAtlas

idea-to-open-source-github-app-skilllisted

Turn an idea, a workaround, or a small tool an agent just built into a finished open-source app published on GitHub, and own the two jobs around it — finding existing open-source solutions before building anything, and making a repository discoverable (About, topics, README, visual assets). Use when the user says "make this an app", "post it to GitHub", "open source this", "is there an existing repo or library for this", "optimize this repo for stars or SEO", or when a session produced a working local script, daemon, menubar app, MCP server, CLI or plugin that others could use. Covers prior-art search and reuse, choosing the artifact shape, surviving reboots, a clean public tree, licence and upstream attribution, a one-command installer, real release assets, registry and plugin manifests, repo metadata, and a stranger-eye install test before calling it done.
samihalawa/idea-to-open-source-github-app-skill · ★ 0 · Code & Development · score 62
Install: claude install-skill samihalawa/idea-to-open-source-github-app-skill
# Idea to open-source GitHub app A session often ends with something that works on one machine: a watcher script, a patched fork, a small server. This skill carries it the rest of the way to a public repository that a stranger can install with one command and that keeps working after a reboot. Run every step yourself; do not hand steps back to the user. This skill also owns two jobs that used to be separate: finding existing open-source work before building (section 1), and making a repository discoverable and convincing (sections 7 and 8). Use those sections on their own when that is all the task needs. Related skills, when installed: `optimal-mcp-designer-skill` (MCP tool surface and remote/stdio publishing), `plugin-creator` (plugin manifests), `universal-mobile-deploy-skill` (store apps). Use them for their part instead of repeating it here. ## Standing rules - Minimum that works. Most of any idea already exists somewhere; search extensively, reuse, and add only the missing piece. Do not over-engineer. - One product, one repository. Its app, website, plugins and MCP tools live together; split copies drift. When the source must stay in a private monorepo, publish a public mirror and run the mirror workflow from the public repo. - Never ship a second variant beside the first. Change the existing app and put the choice in its UI or a flag (for example an endpoint picker: original service or self-hosted), then delete the superseded repo, folder, install and lis