Documentation

Projects, Workflows and Skills

A Project gives related chats the same background and files. A Workflow is a reusable plan inside one Project. A Skill is a reusable capability that works in every chat.

Applies to LlamaBoss 0.1.23 for Windows. Updated October 12, 2026.

Projects

Create or attach a Project from the Project control in the top bar. The chat remembers its Project, and the sidebar tags it. To move a chat to another Project, drag it onto that Project in the sidebar or use Move to project in its menu.

When a Project is attached, its PROJECT.md is sent to the model as background. Use it for the project's purpose, rules, vocabulary, build steps and conventions.

Project folder layout

%USERPROFILE%\LlamaBoss\Projects\My Project\
├── project.json
├── PROJECT.md
├── Sources\
├── Workflows\
├── Outputs\
└── Notes\NOTES.md     (0.1.21, created when first used)

From 0.1.23, new notes go to your personal Notes folder instead of the Project; see Notes.

The Project menu opens these folders, opens PROJECT.md, adds source files, creates or opens a Workflow, switches Projects, or clears the Project from the current chat.

Source files

Put reference documents in Sources. Unlike a one-off attachment, a source stays available to every chat that uses the Project: policies, specs, code snapshots, templates, reference spreadsheets.

Keep PROJECT.md short and point it at the sources. The model reads a source when it needs it, instead of every message carrying everything.

Project Workflows

A Workflow is a folder in the Project's Workflows directory with a WORKFLOW.md plan and, optionally, helper scripts or templates. It's a set of instructions, not something that runs by itself. The agent reads the plan and carries out the steps with its normal tools and approvals.

Use a Workflow when a process depends on this Project's files, naming or rules. If a Workflow has the same name as a Skill, the Workflow wins inside that Project.

Skills

Skills live in one folder and work in every chat:

%USERPROFILE%\LlamaBoss\Skills\

Each Skill is a folder with a SKILL.md file, following the Agent Skills layout used by other assistants: a short YAML header with the Skill's name and description, instructions in Markdown, and an optional scripts\ folder for helpers.

Skills → New Skill designs one with you in the chat. Describe what it should do, and LlamaBoss drafts the SKILL.md and decides whether a helper script is worth including.

Skills that use API keys

Save the key in Settings → Connections → Manage service keys, then list the provider in the Skill's SKILL.md:

## Connections
- runpod

The Skill's scripts then receive the key as an environment variable such as RUNPOD_API_KEY. You can also write connections: runpod in the YAML header, or list the variable name itself. When a new Skill's helper needs a key, Skills → New Skill adds this section for you.

  • A script gets only the keys its own SKILL.md lists. A Workflow script uses its folder's WORKFLOW.md the same way.
  • Scripts the agent creates in a chat get no keys.
  • AI provider keys never reach a script unless its SKILL.md names that provider.
  • The tool card shows which keys a run received, for example keys: runpod. If a script fails because a key was held back, the error names the key and the file to add it to.
0.1.21 and earlier

These versions pass every saved key to every script run. Add the section to your Skills now so they keep working after you update to 0.1.23.

Import and export

Skills → Import a Skill accepts a SKILL.md file or a Skill .zip, including Skills written by other AI assistants. Selecting SKILL.md imports its containing Skill folder, including helper files. From 0.1.23, if that folder also holds unrelated files (a SKILL.md sitting in Downloads, for example), LlamaBoss asks whether to import just the SKILL.md or the whole folder. The dialog previews the name, description and size. A name collision gets a new folder name instead of replacing the existing Skill. Archives are checked so they can't write outside the Skills folder.

Skills → Export a Skill packs a Skill folder into <name>-skill.zip so you can share it or move it to another PC.

Notes

Notes are what LlamaBoss remembers across chats: paths, names, preferences and short facts you ask it to keep. With Agent Mode on, ask in plain language, for example "remember that my music folder is D:\Music" or "save this to my notes". The model checks your notes when a task needs them.

From 0.1.23: the Notes folder

%USERPROFILE%\LlamaBoss\Notes\
├── paths.md                 short facts, one per line
├── mac-mini\setup-log.md    one subject per file
└── projects\My Project.md   notes about a Project
  • Each file covers one subject, at most one subfolder deep. Files are plain Markdown you can open and edit yourself.
  • LlamaBoss builds a one-line index of the files from the description: line at the top of each file and gives the model only that index. The model reads a file when the task needs it.
  • A short fact, up to 300 characters and 3 lines, is added to paths.md (or to another existing notes file) without an approval card. An exact duplicate is not saved twice.
  • Longer material, such as setup history or project details, goes in its own file that starts with a description. The first such write in a chat asks for folder access; granting it covers the whole Notes folder for that chat.
  • Notes about a Project go in Notes\projects\, not in the Project folder.
  • To correct a fact, ask the agent to edit that line rather than add a new one.
Updating from 0.1.21

0.1.23 does not move or delete your old notes. If %USERPROFILE%\LlamaBoss\NOTES.md exists, the model is told about it as older notes not yet sorted into the folder. Project notes in <Project>\Notes\NOTES.md are no longer read automatically; move anything you still need into the Notes folder.

In 0.1.21

NotesLocationUse
Personal notes%USERPROFILE%\LlamaBoss\NOTES.mdThings that should follow you into every chat.
Project notes<Project>\Notes\NOTES.mdFacts and progress for one Project.

In Agent Mode, say "save this to my notes" or "save this to project notes". Notes are appended. With a Project attached, the general notes tool stores the full entry in Project notes and a pointer in personal notes; the Project-only tool stores the entry only in that Project.