-
Notifications
You must be signed in to change notification settings - Fork 2
Install
Foreman is one folder of markdown. Nothing compiles, nothing runs. It installs anywhere an agent can read files.
The only route that is a single command, which is why it is listed first.
/plugin marketplace add Turki-Sh/Foreman
/plugin install foreman@alshuaibi
The marketplace is named alshuaibi, so the install id is foreman@alshuaibi. Both lines, in that order: the first adds the marketplace, the second installs from it.
Download foreman.skill and upload it in the skills settings.
git clone https://github.com/Turki-Sh/Foreman.git
cp -r Foreman/plugins/foreman/skills/foreman ~/.agents/skills/
| Tool | Destination |
|---|---|
| Universal skills directory | ~/.agents/skills/foreman/ |
| Cursor |
~/.cursor/rules/ or .cursor/rules/ in the project |
| Codex |
~/.codex/skills/foreman/, or reference it from AGENTS.md
|
| GitHub Copilot |
.github/copilot-instructions.md, or point it at SKILL.md
|
| Windsurf |
.windsurfrules, or the workspace rules directory |
| Gemini CLI |
GEMINI.md, or the extensions directory |
| Cline, Continue, Roo | The custom instructions or rules field |
Paths move as tools change. The rule that always works: put SKILL.md where your tool reads standing instructions, and keep references/ and assets/ beside it so the relative paths resolve.
Paste SKILL.md into the conversation and say "run this on me." The seven phases and the gates are all in that one file. The references only deepen individual phases.
Say:
help me build my portfolio
It should answer with two questions, not with code. If it starts writing HTML, it did not load.