Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

symbiotic-ai Skill

Repository ↗

by lout33★ 7381 skills

Install

What it does

A symbiotic AI agent that remembers everything, challenges you, and extends your cognition.

  • Connects Instruction files the AI reads
  • Account or key No key found in README or SKILL.md
  • Category Coding
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/lout33-symbiotic-ai.svg)](https://mcp.popnx.com/en/skills/lout33-symbiotic-ai)

Use together with

MCP servers that connect the AI to services for the same work

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 468.8KUpdated 8 days ago

MCP · Connects a serviceRuns on your computer

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

by fallow-rsWidely used↓ 2.4M/wk★ 5.4KUpdated yesterday

MCP · Connects a serviceRuns on your computer

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 740.3K/wk★ 10.4KUpdated 2 days ago

MCP · Connects a serviceRuns on your computer

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
symbiotic-ai
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
Makerlout33morlutomultica-aiGraphify-Labsharry0703
Skills11111
GitHub stars738468,733234,332150,287144,566
Last code changeJun 27, 2026Nov 19, 2026Apr 20, 2026Nov 18, 2026Nov 18, 2026
License–MIT–Apache-2.0MIT

1 skills (instruction sets) by lout33 that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Claude CodeOpenCode

From the maker’s README and the folders in the repo

Install

Is it safe?

  • Who made it

    GitHub account lout33 (person), 8 years old

  • Use and upkeep

    ★ 738 stars · code last changed Jun 27, 2026

  • Any scripts?

    No, plain text files the AI reads and follows

  • Uses the internet?

    No scripts, so it does not go online by itself

  • Changes machine-wide settings?

    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

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

  1. Download from GitHub

    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

  2. Open Skills on claude.ai and upload

    +Create skillUpload a skillpick symbiotic-onboard.zip

    Open claude.ai/customize/skills ↗

  3. No Upload button? Turn on file creation first

    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 Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

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

Restart Claude Code, then type /symbiotic-onboard or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Claude Code, then type /symbiotic-onboard or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

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

Option 2Put the folder there yourself

Put the symbiotic-onboard folder at ~/.agents/skills/symbiotic-onboard

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

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 picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

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

In Cursor’s Agent chat, type / and pick symbiotic-onboard

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. In Cursor’s Agent chat, type / and pick symbiotic-onboard

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

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 Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

Showing the first 8,000 characters · Open the full file on GitHub

---
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 rarely

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
738
Maker
lout33
License
No license stated This repo states no license. By default the author keeps all rights: ask before you share it or use it commercially.
Last code change
Jun 27, 2026
SKILL.md files in the repo (including translated copies and templates)
1
Topics
agent, agent-skills, ai, ai-agents, assistant, claude, claude-code