Working with skills
Install a skill, write your own, and control which ones are switched on for you and for the workspace.
This is the practical half: how to get a skill into your workspace, how to switch one on or off, and what happens when your choice and the workspace's disagree.
Finding the page
Skills in the sidebar and Settings → Skills are the same page mounted twice. Same list, same counter, same buttons — use whichever you land on. Every member can open it; there is no permission on the page itself.
The section header counts what's live for you right now: "Turn a skill on to make it
available to Endless." Your workspace starts with a set already installed — among them clip,
which cuts a moment out of a video, reframes it to vertical or square and burns in captions,
and which the switches below can turn off like any other.
Adding one
"Add skill" offers three routes, and they all end in the same place.
Upload
"Drop a skill, or browse." A .zip or .skill bundle, or a single
SKILL.md on its own. Bundled scripts and reference files come along;
anything binary or oversized is skipped, and the dialog tells you how many.
Paste
The SKILL.md text straight into the box. "Name and description are read
from the frontmatter automatically."
From URL
"Paste a skills.sh or GitHub URL, then Fetch. Bundled files come too." Fetch first, check what loaded, then add.
Whichever route you take you get a Name and a Description to review before saving, and a confirmation once it lands.
Spend your effort on the description. The description is what Endless reads when deciding whether a skill is relevant — the field even prompts for it: "Tell Endless when this skill should be used…". Write it as when to reach for this, not as what this is. A perfect skill with a vague description simply never fires.
Adding a skill needs permission to create content — members and admins have it by default, viewers don't. A skill you add is available to the whole workspace, subject to the switches below.
Reading and editing one
A row's menu carries "View skill" and "Remove". The detail view shows its Source, when it was Last updated, its description, and its files as a tree you can click through. Editing happens right there — open a file, change it, save.
You can edit and remove skills you added. Changing or removing one someone else added needs the broader permissions for acting on other people's work — see roles and permissions.
Switching skills on and off
Two switches stack. The workspace's decides what is possible; yours decides what is on.
My tools — your own choice
The default tab. A switch per skill, affecting nobody but you.
Workspace — the ceiling
A second tab, visible only to people who can manage the workspace's tools — that's a governance permission admins hold by default, and ordinary members do not. Its hint says what it does: "Turn a skill off here to remove it for everyone in the workspace. Members choose for themselves among the ones left on."
The ceiling wins. Where a skill is off for the workspace, your own switch is replaced by a locked "Off for workspace" badge — there is no way to turn it back on for yourself. The reverse isn't true: switching a skill on for the workspace makes it available, it doesn't force it on for anyone.
There is a third, narrower level. An admin can set one person's skills from that person's profile, under Access — and the same rule applies there, in the product's own words: "A skill needs to be on for the workspace before it can be turned on here."
Who holds the ceiling
The permission that unlocks the Workspace tab, and who has it.
Per-person overrides
Set from a member's profile in Members, under Access.
Where a skill shows up
In chat, on its own
You don't invoke a skill. When a task matches one that's on for you, it
loads. You can also name one directly with / in the composer.
In scheduled runs
Skills work while you're asleep too. A schedule's Tools control lists them, so you can switch individual skills off for that one schedule without touching your own settings.
Not project knowledge
A project's knowledge is a skill underneath, but it's deliberately hidden from this list and loads only when its project is attached to the chat.
A skill you turn off is off everywhere — chat and scheduled runs alike. If a schedule that used to work stops behaving, a skill switched off at either level is worth checking before the prompt.