Symbiotica Skills

The pack's agent stack is built around definitions on disk: a personality (SOUL), instructions (CLAUDE), and a set of skills - markdown capabilities the agent can reach for. Symbiotica Skills is the switchboard: it scans the skills directory, shows each skill as a toggle, and outputs the enabled ones for the agent settings node.

If you've never touched the agent stack, this node does nothing useful on its own - it's the middle of a three-node graph (Agent Settings → Skills → Agent). If you have, it's the difference between an agent that can use ten tools and one you've deliberately restricted to two.

How it works

It scans a skills directory for subfolders containing a SKILL.md, and each skill becomes a toggle on the node. Enabled skills are gathered into an AGENT_SKILLS list that flows into the agent's settings. The directory comes from three places, in priority order: the skills_path widget, the SYMBIOTICA_SKILLS_DIR environment variable, then skills_dir in the pack's config.ini. The widget wins when set.

The pack's skills repo is symbiotica-ai/skills - clone or point this at it, or at your own folder of SKILL.md definitions. Each skill's frontmatter name is what shows on the toggle.

The inputs and output

• skills_path (optional) - path to the skills directory. Overrides the env var and config.ini. Leave empty to use the configured default.
• skills (output) - the AGENT_SKILLS list of enabled skills. Wire it into Symbiotica Agent Settings.

That's the whole surface: one optional path, one typed output.

Install

Standard pack install - search Symbiotica in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/symbiotica-ai/comfyui-nodes.git symbiotica
pip install -r symbiotica/requirements.txt

Then configure the skills directory once:

# config.ini in the package root
[skills]
skills_dir = /path/to/skills

or export SYMBIOTICA_SKILLS_DIR=/path/to/skills. Restart after.

Gotchas

The most common "why is it empty" is a path problem: the node only lists subfolders that contain a SKILL.md - a directory of loose markdown files shows nothing, and so does a path the env var names that doesn't exist (it silently falls back to the default). The toggle granularity is also worth thinking about: skills are all-or-nothing per folder, so keep each capability in its own subfolder rather than lumping them, or you can't restrict one without losing the rest. And remember the security framing from the KB: any node in this stack runs arbitrary Python with your keys, and an agent with skills is an agent with tools - only enable what the workflow actually uses.