Once a plugin exists, you shape its skills on its **Skills** page and add any other services they call on **Connectors**. Changes save as you go, and members get them when you publish.
## Add and remove skills
The plugin's **Skills** page groups its skills under **Managed skills** and **Custom skills**. A starter skill you add becomes a custom skill.
To add skills:
1. On **Skills**, choose **Add skills**. The Library's skills open inside the plugin.
2. Choose **Add** on each skill you want. **Blank skill** adds an empty custom skill for you to write.
3. Go back to **Skills** to add preferences, instructions and files.
A plugin holds up to 50 skills.
To remove a skill, open it, choose **Remove skill**, then confirm. Members keep it until you publish changes, and published versions keep it too. If the skill isn't in any published version, its preferences, files and, for a custom skill, instructions can't be restored once it's removed.
A skill's card shows what it still needs: **Needs instructions** or **Needs a description** for a custom skill that isn't ready to publish, and **Not in your release** for a managed skill your organisation's release doesn't have. See <mention-page url="https://app.notion.com/p/41b4815eed4f81ed8b58cfe210582143">Managed skills releases</mention-page>.
## A skill's sheet
Choose a skill's card to open its sheet. Choose **Done** to close it.
### Custom skills
Under **Skill**, a custom skill has:
- **Name**, shown in agent skill lists;
- **Address**, in lowercase words separated by hyphens;
- **When should the agent use this skill?**, the description agents use to choose it;
- **Instructions**, in Markdown. Refer to supporting files by their paths in the skill, such as `references/guide.md` or `assets/template.docx`.
A custom skill needs instructions and a description before you can publish the plugin. Custom skills don't take preferences: change their instructions directly.
### Organisation preferences
Only managed skills take preferences. A managed skill's sheet shows **What it does**, but not Tilt's instructions, and has an **Organisation preferences** field for your house style, output requirements, terminology and extra context.
Agents get your preferences with the skill's instructions. Where the two differ, your preferences take precedence, except for the skill's fixed rules, which Base lists with them. Preferences can't grant access, change the licence or go beyond what the user asked for.
### Supporting files
Supporting files are templates, precedents, references and helper scripts a skill uses.
- Each file can be up to 1 MB, with up to 20 files per skill and 20 MB of files in a plugin.
- Allowed types are Markdown, text, CSV, JSON, PDF, Word (.docx), Excel (.xlsx), PNG, JPEG, WebP, Python and YAML.
- A custom skill keeps its files in `assets/`, `references/` and `scripts/`, and any folder you make with **New folder**. Open a folder, then choose **Upload** or drop a file on it.
- A managed skill's files go in `preferences/assets/`.
- Uploading a file with the name of one already there asks before it takes the old one's place. Published versions keep the old one.
- Select a file to remove it. Published versions keep it; to get it back, upload it again.
Base serves Python helper scripts but never runs them.
<callout icon="⚠️" color="yellow_bg">
	**Don't upload matter data.** Supporting files are for your organisation's know-how, not a client's documents.
</callout>
### Keep confidential
The sheet's **Confidentiality** section says how agents treat the skill.
- Managed skills are always confidential under Tilt's licence.
- A custom skill is confidential once you switch on **Keep confidential**. Agents are then told to keep its instructions and files confidential under your organisation's licence, and not to share or reproduce them. It's off by default: agents may then describe or share the skill when asked.
**Keep confidential** is an instruction agents follow, not a technical lock. A confidential custom skill's card reads **Custom skill · Confidential**. <mention-page url="https://app.notion.com/p/41b4815eed4f810fa66ed2c1031451b1">Confidential skills</mention-page> explains what it means for members, and the licence wording is in <mention-page url="https://app.notion.com/p/41b4815eed4f81688775cf0aaca8d164">Organisation settings</mention-page>.
## Connectors
A connector is a remote MCP service your plugin's skills can use. Each member connects to it with their own account in their AI.
A plugin with skills always has the **Tilt Base** connector, which delivers every skill. Add another connector only when a skill needs tools from another MCP service.
1. On the plugin's **Connectors** page, choose **Add connector**.
2. Enter a **Connector name**: lowercase words separated by hyphens, not used by another connector in the plugin. `tilt-base` is reserved.
3. Enter the service's **MCP endpoint**. It must use HTTPS.
4. Choose **Add connector**.
A plugin holds up to 10 connectors. To change or remove one, open its card's menu and choose **Edit** or **Remove**. Members keep a removed connector until you publish changes.
<callout icon="⚠️" color="yellow_bg">
	**Keep credentials out of plugins.** Never put access tokens, passwords or secret query parameters in an endpoint, instructions or preferences. Each member signs in to the service in their own AI.
</callout>
## Related
- <mention-page url="https://app.notion.com/p/41b4815eed4f81fb84a8d9bf7d03c16d">Create a plugin</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f8162941ed9732567b645">Publish and versions</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f810fa66ed2c1031451b1">Confidential skills</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f81ed8b58cfe210582143">Managed skills releases</mention-page>