> ## Documentation Index
> Fetch the complete documentation index at: https://docs.saphion.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Shared and Organisation skills

> Use skills your Admin offers, and understand which one runs when two share a command.

Skills do not have to be your own. An Admin can offer skills to the whole Organisation. You cannot share a skill yourself yet. They sit in your **Settings > Skills** list beside your own and run the same way, with a slash command.

> [!NOTE]
>
> Everyone with a Platform seat can use skills shared with them or offered by the Organisation. Only an Organisation Admin brings in, offers or removes an Organisation skill.

## Where they appear

Open **Settings > Skills**, under **Customise**. On **Yours**, a switch under the head narrows the list to **All**, **Yours**, **Shared with you** or **Organisation**, the same four words as Creations and Files. Inside each view, the plugins are grouped by who made them:

| Group | What it holds |
| - | - |
| **Yours** | Skills you wrote. See [Skills](https://docs.saphion.co.uk/beacon/skills.md). |
| **Shared with you** | Skills someone has given you access to. People cannot share a skill yet, so this group is usually empty. Their row says "from a colleague". |
| **Organisation** | Skills your Admin brought in. Their row says "from your Organisation". |
| **From Saphion** | Skills Saphion provides. See [Skills from Saphion](https://docs.saphion.co.uk/beacon/skills.md#skills-from-saphion). |

Skills from a marketplace source your Admin added sit in a group of their own, headed From and the repository owner's name, above **From Saphion**.

Each skill belongs to a plugin: a set of skills with its files and any connectors it uses. A plugin is what an Admin offers and you switch on. Open one to read its **Overview**, **Contents**, **Skills** and **Connectors**. **Try in chat** opens Beacon with the skill already in the box and nothing sent.

## Run a shared or Organisation skill

A skill runs when its plugin is on. Open the plugin and use its switch, or choose **+** on its card in **Discover**. Then, in the Beacon box, type `/` and choose the skill, or choose **Add** and then **Skills**. Only skills that are on are in the list.

A shared or Organisation skill follows the same rules as your own: Beacon still works inside your permissions, and every tool it uses still follows its own setting. See [Run a skill](https://docs.saphion.co.uk/beacon/skills.md#run-a-skill).

## How it works

### Who can do what

| | Yours | Shared with you | Organisation |
| - | - | - | - |
| Who made it | You | A colleague | An Admin brought it in |
| Who can run it | You | You, once you switch it on | Everyone it is made available to, as the offer below says |
| Remove | You | Only its owner | Admins |

To change a skill you cannot edit, open its plugin and choose **Duplicate** from the ⋯ menu. The copy is yours.

### What an Admin's offer means

An Admin chooses what the Organisation offers each plugin, Saphion's plugins included. Open the plugin and look under **For your Organisation**, **Availability**. You see the offer in words, and an Admin gets the control.

| Offer | Effect for you |
| - | - |
| **Not available** | Members do not see it and cannot use it. Admins still see it. |
| **Available** | Members can turn it on from Discover. It runs only once you switch it on. |
| **On by default** | On for you until you switch it off. |
| **Required** | On for every member, with no switch to turn it off. |

A plugin your Organisation's marketplace source brings in starts as **Not available** until an Admin offers it. **Not available** can be chosen only for plugins the Organisation brought in. A Saphion plugin starts on until an Admin chooses otherwise.

### Skills with the same command

Two skills can end up with the same slash command. Every one of them still runs, but only one keeps the plain command. The others are called by their plugin and skill name, such as `/weekly-reports:status`, which the plugin's **Skills** tab shows.

1. A Saphion skill always keeps its plain command, so `/design` never changes meaning under you.
2. Between the rest, an Organisation skill beats one you wrote, and one you wrote beats one shared with you.
3. Between two shared skills of one name, only one can be on at a time. Switching one on while the other is on is refused with a message naming the one to switch off first.

### Whether Beacon may choose it

Each skill says how it runs. Open the skill inside its plugin and read **How it runs**. Some start only when you ask for them by name. Others can also be chosen by Beacon when your request calls for them. A skill you write in the form is the second kind. Standing guidance for every chat belongs in [Instructions](https://docs.saphion.co.uk/admin/instructions.md).

## Bring in skills for the Organisation

This is for Admins. In **Settings > Skills**, an Admin has a third tab, **Sources**, and **Add marketplace source** in the Add menu.

**1. Add the source**

Paste the address of a public GitHub repository of plugins in the Claude plugin format, one with a `.claude-plugin/marketplace.json`. Private repositories cannot be read. An Organisation keeps up to 20 sources.

**2. Sync it**

Adding a source does not read it. Choose **Sync now** and Saphion lists every plugin the repository holds. A plugin that cannot be taken in, such as one with executable files or credentials, is listed with the reason and nothing is dropped.

**3. Offer what you want**

Open a plugin from the source's last sync report and choose its offer. Until you do, members do not see it.

Choose **Sync now** again to read the repository again. A plugin that changed becomes a new version, and one that did not changes nothing. To stop reading a repository, choose **Remove** from the source's ⋯ menu.

## Ask Beacon

Type `/` and the skill's command, such as `/site-diary`, then add your notes. A skill that Beacon may choose for itself can also run when your request fits it; a skill that runs only when asked needs its `/` command.

## FAQ

> [accordion] Why is a shared skill in my list but not in the / menu?
>
> The menu lists only skills that are on. A shared skill starts off, and an Organisation plugin that is only **Available** starts off. Open its plugin and switch it on.

> [accordion] Can a colleague see my skills?
>
> No. A skill you write is private to you.

> [accordion] Can a shared skill do things I cannot?
>
> No. A skill is a procedure. Beacon works inside your permissions whoever wrote it.

> [accordion] Why can I not switch an Organisation skill off?
>
> Your Admin has made it **Required**, so it is on for every member.

## Related

* [Skills](https://docs.saphion.co.uk/beacon/skills.md): Write your own skill and run any skill with a slash.
* [Instructions](https://docs.saphion.co.uk/admin/instructions.md): Standing guidance that applies to every chat.
* [Chat with Beacon](https://docs.saphion.co.uk/beacon/chat.md): Run a skill from the Add menu or with a slash.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.