Skills and knowledge
Skills teach Endless your workflows — and load only when a task actually needs them.
A skill is a folder with a SKILL.md inside it: a name, a description of when it should be
used, and the instructions Endless follows when it is. The product puts it this way —
"Extend Endless with your own knowledge and workflows. Each skill loads only when a task needs
it — so it never gets in the way."
Opened up, a skill is exactly that folder: the SKILL.md the agent reads, and whatever
references or scripts it carries alongside.
Think of a skill as a note to a very capable colleague: "when someone asks for a client report, here's the format we use, here's where the numbers come from, here's the tone." You write it once; Endless picks it up whenever the moment comes.
How a skill loads
The reason you can install a lot of skills without slowing anything down is that almost none of each skill is loaded, almost all of the time.
Discovery
"Only each skill's name and description load at startup — just enough to know when it's relevant."
Activation
"When a task matches a skill, Endless reads the full SKILL.md into context."
Execution
"It follows the instructions, loading bundled scripts, references, or assets as needed."
This is why a skill's description matters more than anything else in it. It's the only part Endless sees when deciding whether the skill applies — write it as when to use this, not as what this is.
Where skills come from
Preinstalled
Your workspace starts with a set of skills already installed and ready —
things like working with documents, slides and images, or clip, which cuts
a moment out of a video, reframes it and burns in captions.
Added by you
"Add skill" takes three routes: Upload (a .zip or a SKILL.md),
Paste (the SKILL.md text itself), or From URL (a skills.sh or
GitHub link — bundled files come too).
A project's knowledge
Every project owns one knowledge entry, which is a skill underneath. It's hidden from this list and loads only when its project is attached to the chat.
One page, two doors
Skills in the sidebar and Settings → Skills are the same page. Not two similar pages — literally the same one, mounted in two places, with the same list, the same counter and the same buttons. Use whichever you land on.
The distinction people expect from those two URLs — my skills versus the workspace's — is real, but it's a pair of tabs inside the page, not a pair of pages. Read on.
The page's "Installed skills" section counts how many are live for you right now, and says what the switch does: "Turn a skill on to make it available to Endless."
Turning skills on and off: two levels
Every skill has two switches, and they stack. The workspace one sets what is possible; your own one sets what is on.
Workspace — the ceiling
"Turn a skill off here to remove it for everyone in the workspace. Members choose for themselves among the ones left on." This tab appears only for people who can manage the workspace's tools.
My tools — your choice
Your own on/off for the skills the workspace left available. Nobody else is affected by what you do here.
The workspace switch always wins. A skill turned off for the workspace can't be turned back on by an individual — their toggle is locked. Turning it on for the workspace doesn't force it on for anyone either; it just makes the choice available.
There is a third, narrower level: an admin can set a person's skills individually from that person's profile, under Access. The same rule applies there, in the product's words: "A skill needs to be on for the workspace before it can be turned on here."
Skills, knowledge and connectors
Three things extend what Endless can do, and they're easy to confuse:
| Thing | What it adds | Scope |
|---|---|---|
| Skill | Instructions and files — a workflow Endless can follow | The whole workspace, if left on |
| Knowledge | Durable facts and rules about one client or campaign | Only chats its project is attached to |
| Connector | Access to an outside tool, using your own credentials | Per person, on top of the ceiling |
Project knowledge
Why a project's knowledge is separate from the general skills list, and how Endless keeps it current.
Connectors
Connectors follow the same two-level model — a workspace ceiling plus your own choice — with one extra step: you sign in to the tool yourself, so a connector that's on but not connected still can't do anything.
Skills work in scheduled runs too, not just in chat. A skill you turn off is off everywhere, including in tasks that run while you're asleep.