REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A symbiotic AI agent that remembers everything, challenges you, and extends your cognition.
Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/skills/lout33-symbiotic-ai)MCP-Server, die die KI für dieselbe Arbeit mit Diensten verbinden
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
Gleiche Art Arbeit, sortiert wie die Skill-Liste
| Dieser symbiotic-ai | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Anbieter | lout33 | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub-Sterne | 738 | 468.733 | 234.332 | 150.287 | 144.566 |
| Letzte Codeänderung | 27. Juni 2026 | 19. Nov. 2026 | 20. Apr. 2026 | 18. Nov. 2026 | 18. Nov. 2026 |
| Lizenz | – | MIT | – | Apache-2.0 | MIT |
1 Skills (Anweisungssammlungen) von lout33, die eine KI liest und befolgt · kein MCP-Server
MCP = die Hände
Verbindet die KI mit einem externen Dienst oder Daten, etwa Notion lesen oder eine Rechnung erstellen. Ein Programm oder Server muss laufen.
Skill = das Handbuch
Eine Textdatei, die der KI zeigt, wie eine Aufgabe geht. Sie verbindet sich mit nichts.
Manches überschneidet sich: Einige Skills starten Skripte mit Werkzeugen, einige MCP-Server liefern nur Wissen. Geh von der Aufgabe aus.
Claude CodeOpenCode
Laut README des Anbieters und den Ordnern im Repo
GitHub account lout33 (person), 8 years old
★ 738 stars · code last changed 27. Juni 2026
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit ec9df97 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
Zuerst: Welche KI nutzt du?
Wähle deine App, dann zeigt diese Seite nur die Installation für diese App
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the skills/symbiotic-onboard folder again. The ZIP must have a symbiotic-onboard folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick symbiotic-onboard.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 12. Nov. 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Kopiere diesen Satz und füge ihn in einen Claude Code-Chat ein
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code neu starten, dann /symbiotic-onboard tippen oder eine passende Aufgabe stellen; Claude nutzt den Skill
Checked against official docs 12. Nov. 2026 · Source: code.claude.com
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md
Befehle werden geprüft · Kopier-Buttons erscheinen, sobald sie bestanden sind
Selbst installierte Skills funktionieren in der ChatGPT-Desktop-App, in Codex CLI und in der Codex-Erweiterung für die IDE · ChatGPT im Web und auf dem Handy kann selbst installierte Skills nicht nutzen, nur Skills, die mit einem Plugin aus dem Verzeichnis kommen
Die ChatGPT-Desktop-App enthält Codex, und Codex liest Skills aus dem Ordner ~/.agents/skills
Öffne Codex in der ChatGPT-Desktop-App und füge diesen Satz in den Chat ein
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Lege den Ordner symbiotic-onboard unter ~/.agents/skills/symbiotic-onboard ab
~ ist dein Home-Ordner ($HOME)
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md
Befehle werden geprüft · Kopier-Buttons erscheinen, sobald sie bestanden sind
Checked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com
Selbst installierte Skills funktionieren hier nicht, nur Skills, die mit einem Plugin aus dem Verzeichnis kommen
Um diesen Skill mit ChatGPT zu nutzen, verwende die ChatGPT-Desktop-App wie oben beschrieben
Checked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com
Kopiere diesen Satz und füge ihn in einen Codex-Chat ein · Funktioniert in Codex in der ChatGPT-Desktop-App, in Codex CLI und in der IDE-Erweiterung
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex erkennt neu installierte Skills selbst; wenn einer nicht erscheint, starte Codex neu · So nutzt du ihn: In ChatGPT @ tippen und den Skill wählen · in Codex CLI oder der IDE-Erweiterung /skills ausführen oder $ und den Skill-Namen tippen
Checked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md
Befehle werden geprüft · Kopier-Buttons erscheinen, sobald sie bestanden sind
Kopiere diesen Satz und füge ihn in einen Cursor-Chat ein
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Im Agent-Chat von Cursor / tippen und symbiotic-onboard wählen
Checked against official docs 12. Nov. 2026 · Source: cursor.com
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md
Befehle werden geprüft · Kopier-Buttons erscheinen, sobald sie bestanden sind
Für andere Apps, die Skills lesen. Der Satz enthält die Pfade für Claude Code, Codex und Cursor, damit die KI den für deine App wählt · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 12. Nov. 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Andere Apps mit Agent Skills (etwa Gemini CLI oder GitHub Copilot) nutzen andere Ordner. Sieh in deren Anleitung nach und kopiere den Ordner mit der SKILL.md dorthin.
Skill-Ordner am 11. Nov. 2026 mit den offiziellen Anleitungen von Claude Code, Codex und Cursor geprüft
Der folgende Text stammt aus dem Repo des Anbieters, nicht von PopNx MCP
Die ersten 8.000 Zeichen · Ganze Datei auf GitHub öffnen
---
name: symbiotic-onboard
description: Onboard a new user into a Symbiotic AI setup by interviewing them one sharp question at a time and writing their own context files (SOUL.md, USER.md, NOW.md, and AGENTS.md) as plain Markdown they keep. Use this whenever someone is setting up a personal AI agent, wants their assistant to remember or understand them across sessions, mentions Symbiotic AI / SOUL.md / USER.md / NOW.md, is staring at blank template files full of [bracketed placeholders], or asks how to give an AI persistent context they own and can move between models. Trigger even if they do not say the word "onboard".
metadata:
author: symbiotic-ai
version: 1.0.0
---
# Symbiotic Onboard
## What this does and why
This skill sets a brand-new user up with a working Symbiotic AI configuration in one short conversation. The whole point of Symbiotic AI is **ownership and portability**: a person's context lives in plain Markdown files they own, can read and edit by hand, can version, and can carry to any model. Native platform memory cannot offer that. It is opaque, automatic, and locked to one vendor.
So the job here is not to "store" anything in a hidden place. It is to **interview the user and write plain files they keep.** When you finish, the user has four files (`SOUL.md`, `USER.md`, `NOW.md`, and optionally `AGENTS.md`) that any agent runtime can load. They own them.
The hard part of onboarding is the blank page. A new user opens template files full of `[bracketed placeholders]`, does not know what to type, and stalls. This skill removes that wall by doing a short, sharp interview and filling the files for them.
## The core rule
**Interview one sharp question at a time. Never dump a list of questions.** A wall of questions makes people freeze or write thin, generic answers. One question, wait, write the answer into the right file, then ask the next. This is how you get real content instead of a survey.
Stay in **SOUL voice** while you do it: short, direct, references what they just said, no filler. You are a co-pilot who is going to know this person, not an intake form.
## Setup before the interview
1. Decide where the files go. Default to the current working directory. If the user has a workspace or repo for their agent, use that. Ask in one line if unclear: "Where should your files live? (default: here)"
2. Seed the files from the bundled templates so the structure is correct and the user can see what a finished setup looks like:
- Copy `assets/SOUL.md`, `assets/USER.md`, `assets/NOW.md`, and `assets/AGENTS.md` into the target directory.
- `SOUL.md` and `AGENTS.md` are already filled (agent identity and operating protocol). You usually leave them as-is. Offer to tune `SOUL.md` voice later if the user wants a different personality.
- `USER.md` and `NOW.md` contain `[bracketed placeholders]`. These are what the interview fills.
3. Tell the user, briefly, what is about to happen and why it matters: "I am going to ask you a few sharp questions and write your answers into plain files you own. A handful of questions now, the rest fills in as we work together."
If the user would rather start from a realistic example than a blank template, that is fine: copy a filled example profile over the templates and rewrite it as them, one answer at a time. Editing a real example beats filling blanks. (In the Symbiotic AI repo these live under `examples/`.)
## The interview
Ask these first. They are enough to make the agent useful today. Ask, wait, write, move on.
1. **Name** - "What should I call you?" -> write into `USER.md` Identity.
2. **Current goal** - "What are you actually trying to make happen right now?" -> `USER.md` Mission / The Real Goal, and reflect the near-term version into `NOW.md`.
3. **What they are avoiding** - "What is the thing you keep not doing?" -> `USER.md` Psychology (start a "Bugs" entry) and/or Who You Are.
4. **Today's MIT** - "If you finished one thing today and felt good tonight, what is it?" -> `NOW.md` under `# QUEUE > ## TODAY` as the first checkbox.
Then, only if the user has energy for more, you can deepen: stack/skills, what charges vs drains them, how they work best, a recent win. Each still one question at a time, each written into the matching `USER.md` section.
**Defer the heavy stuff.** Financial reality and deep psychology (drivers, fears, long patterns) are real sections in `USER.md`, but do not mine for them in session one. Leave those placeholders for later sessions. Pushing for money and trauma on day one kills the onboarding. Get them operational first; the deep profile accumulates over time, which is exactly the Symbiotic advantage.
### How to write the answers
- Replace the matching `[bracketed placeholder]`, do not append next to it. The file should read like the user wrote it.
- Keep their voice. If they say "I keep rewriting my landing page instead of shipping," write that, not "Tendency toward perfectionism."
- Mirror anything raw before moving on. If an answer is heavy, acknowledge it in one line, then continue. This is setup, not therapy, but do not steamroll a real moment.
- After each write, you can briefly confirm what you captured so they see the file taking shape and trust that it is theirs.
## Finish the file: defer what you did not ask
This step matters as much as the interview. A short interview fills the high-value fields (name, goal, avoidance, today's MIT) but leaves dozens of secondary `[bracketed placeholders]` in `USER.md` and `NOW.md` (age, location, stack, energy map, relationships, financials). If you leave those raw, a first-time user sees broken-looking brackets and assumes the skill half-failed. Do not turn the interview into a 40-question wall to avoid this. Handle it at the end instead.
As your final write, sweep `USER.md` and `NOW.md` and resolve every remaining `[bracketed placeholder]` you did not fill, using whichever reads cleaner per field:
- **Replace it with a deferred marker** so the structure stays visible but reads as intentional: `_(not set yet, your agent will fill this in as it learns you)_`. Use this for fields worth keeping in view (stack, energy map, psychology bugs, milestones).
- **Drop the whole optional subsection** when an empty scaffold adds noise rather than value (for example a `Career` or `Shipped` table the user has nothing for yet). Removing it is cleaner than a table of deferred markers.
Leave markdown checkboxes like `[ ]` alone. Those are list syntax, not placeholders. You are only resolving the descriptive `[Your ...]`-style fill-ins.
The end state is firm: **no raw `[Your ...]`-style brackets remain.** Every field is either filled in the user's words or shows the clear deferred treatment. The file should read as complete and intentional, never as broken output.
Because the deferred marker uses parentheses, not brackets, it will not re-trigger the agent's onboarding protocol on the next session. The bundled `AGENTS.md` tells the agent to fill these deferred fields naturally as it learns the user, so they complete through use rather than a wall of questions.
## Close
When name, goal, avoidance, and today's MIT are written, the deferred sweep is done, and no raw `[bracketed placeholders]` remain:
1. Confirm: "You are set up. I know who you are and what today is about."
2. State today's MIT back to them in their own words.
3. Tell them how to actually use the files (see below).
4. One line forward: "Go."
## Tell them how to use the files
This is the step that makes the work real. End by showing the user how their new files plug into an agent. Keep it to what fits their setup:
- **The files are yours.** They are plain Markdown in their directory. They can open, edit, correct, delete, and version them in git anytime. Nothing is hidden.
- **At session start, the agent reads all four** (`SOUL.md`, `USER.md`, `AGENTS.md`, then `NOW.md`) and acts from them. `NOW.md` updates as they work; the stable files change rarelyFragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.