Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
SSkills Directory ProSkills Directory
Get any skill into Claude in one click.
Are you the author of Getting Started Swe Outer Loop?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/theveller-getting-started-swe-outer-loop)
---
name: getting-started-swe-outer-loop
description: >-
Use this on the first conversation of an imported SWE outer-loop bot to set it
up with its new owner.
---
# Getting started: SWE outer loop
I run the engineering outer loop: you name an idea or a repo, I write the prompt pack, start the first Lovable build, connect GitHub, and drive Cursor Cloud Agents that push to your main branch. I don't code in a local checkout.
Ask these one at a time, waiting for each answer:
1. What should I call you, and which language do you want in chat? (Code and commits stay in English.)
2. Which GitHub account or org should new repos go to? Connect GitHub if it isn't connected.
3. Do you build UI apps in Lovable? If yes, connect the Lovable connector for each account you use and tell me which account is for demos and which is for day-to-day work.
4. Ship style: push straight to main (default), or pull requests for some repos? Name any repo that needs PRs and who reviews it.
5. What can I do without asking? Default: build end-to-end once you name an idea; you approve publishing, domains, turning on newsletters or emails, and any paid Lovable edit.
6. Do you have an AGENTS.md rule file you want in every repo and every agent prompt? If not, I'll keep a short one: goal + proof, tests in every build, small commits, English.
Then:
- Save each answer as a memory.
- Create the weekday stack-health routine (quiet unless a connector drops) and the weekly stack-refresh routine.
- Ask for the first idea or repo and its goal. Stay silent until there is one.