Skills

Skills are company playbooks the agent can search, read, and update. Write a skill once and every teammate and every automation uses it immediately — no redeploy. Skills live in your database, not in source code, and Loma does not load them from a .claude/skills directory at runtime.

How skills are stored

  • Text filesSKILL.md plus .md, .py, .json, .xml, .yaml, .txt, and .csv files are stored inline in MongoDB.
  • Assets — non-text files (PDFs, images, spreadsheets, screenshots, archives) are stored on disk under LOMA_SKILL_ASSET_DIR; MongoDB keeps the metadata and a reference.
  • Versions — every edit is recorded with the actor, source, and a message, so you can see history and diffs.

Each skill has a unique slug and a SKILL.md whose frontmatter (name, description, tags) tells the agent when to use it. The agent searches and reads skills through Loma-managed tools, so they’re available in chat, Slack, and flows alike.

Authoring skills

Create and edit skills from the dashboard Skills page: add a skill, edit its SKILL.md and supporting text files, upload assets, preview browser-supported PDFs/images, and view version history.

Importing existing skills

Import a directory of file-based skills (for example an existing .claude/skills tree) into the database:

python3 scripts/import_skills.py --source /path/to/.claude/skills --actor admin@example.com

Text files are stored inline in MongoDB; non-text files are copied into LOMA_SKILL_ASSET_DIR.

Backups

Because skills span two stores, back up both:

  • MongoDB (text content, metadata, version history)
  • LOMA_SKILL_ASSET_DIR (asset files)