Create a public GitHub repo

Running this skill is the user's go-ahead to publish, so ask only for what you can't work out. The two scripts hold every fixed choice: scripts/scaffold.sh writes the files that are the same in every repo, and scripts/configure.sh applies and checks the GitHub settings. Paths to the scripts are relative to this skill's folder.

Steps

1. Check the folder. It must hold no project files: only an empty git repo, .claude/ or editor folders such as .idea/ may be there, and they stay out of the commit. Otherwise stop and say this skill starts new projects only.

2. Ask for the description. The owner is the active gh account (gh api user --jq .login) and the repo name is the folder's name. In one message say "Creating <owner>/<repo> as a public repo" and ask for a one-sentence description. Skip the question when the user already gave one.

3. Write the files. Answer the other skills' questions from here, so the user gets no more of them.

   1. Run git init -b main unless the folder is already a git repo, then scripts/scaffold.sh <owner> <repo>.
   2. Use the gitignore skill. No stack is chosen yet.
   3. Use the readme skill with the name, the description, the status "Early development, not usable yet", and the license AGPL-3.0-or-later.
   4. Use the agentsmd skill with the name and the description, and put these two lines in its Rules:
      • CI checks go in the Verify job of .github/workflows/verify.yaml, which the main ruleset requires. Pin every action to a full commit SHA: the repo rejects tags.
      • When you add a build file, add its ecosystem to .github/dependabot.yml.

   Done when LICENSE, README.md, AGENTS.md, .gitignore and the .github folder exist.