Where Can You Actually Run System Weaver?

By (@anselm) ·

The best part about this project? It follows an open standard, meaning you aren’t locked into just one AI tool. If your tool can read a Markdown file, it can run System Weaver. Here is how to hook it up to your favorite setup: 💻 The Terminal / CLI GuysIf you like living in the command line, you're covered: Claude Code: This is its native home. You can grab it straight from my GitHub using the plugin marketplace (/plugin marketplace add anselm1234-eng/system-weaver) and you're good to go. OpenAI Codex CLI: It’s super easy. Just drop the skills into the .agents/skills/ folder, and Codex will scan and use them. Gemini CLI: It reads skills automatically from .gemini/skills/ and .agents/skills/. GitHub Copilot CLI: It has a neat /skills command where you can install and toggle skills on or off. Mistral Vibe, OpenClaw, and OpenHands: These guys are fully compatible with the standard. Just toss the files into .agents/skills/ and let them do their thing. 🖥️ The IDE & Editor SquadIf you prefer a visual interface, here is how it works: Cursor: It's awesome with this. Cursor naturally discovers the SKILL.md files, and you can even trigger the workflows straight from the slash command menu. VS Code (GitHub Copilot): It supports it natively (via preview flags). Just put the skills in .github/skills, .claude/skills, or .agents/skills, and Copilot will pick them up. Windsurf, Kilo Code, Roo Code, Aider, OpenCode: All of these are fully compatible. TL;DR: No matter if you're a hardcore terminal user or a visual IDE fan, you can just clone the repo, drop the skills folder into your tool's directory, and start designing hyper-scale systems!

4 likes · 4 views

Explore more on Prompted

Loading