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

> ## Agent Instructions
> Use the exact commands, endpoints, and product terms in these docs. Check the context map before connected services or the web.

# Create a skill

> Author, import, or upload an Agent Skill to your library.

Open **Skills** in Port of Context, then select **Add skill**.

## Choose a source

> [tab] Search
>
> Search the public skills registry, choose a result, set its scope and placement, then add a snapshot to your library.
>
> An admin must enable external skill import.

> [tab] Author
>
> Enter a lowercase kebab-case name, an optional description, and the complete `SKILL.md` content.
>
> ```markdown SKILL.md theme={null}
> ---
> name: customer-brief
> description: Prepare a sourced brief before a customer meeting.
> ---
>
> ## Prepare the brief
>
> Start with the context map. Confirm the account owner and relevant systems.
> Then gather current activity from connected services.
> ```

> [tab] Upload
>
> Upload one of these formats:
>
> * A single `SKILL.md`
> * A `.zip` bundle
> * A `.skill` bundle
>
> The bundle can contain `scripts/`, `references/`, and `assets/` beside `SKILL.md`.

> [tab] Import by URL
>
> Paste a supported repository path, a file URL, or a repository plus skill name. Port of Context copies a snapshot into your library.
>
> An admin must enable external skill import.

## Set scope and placement

Choose who can use the skill, then optionally place it on the context map.

**1. Choose a scope**

Use **Personal** while drafting. Choose **Team** or **Workspace** when the skill should be shared.

**2. Choose a place**

Select the team, system, or domain where the skill applies. Leave it empty for a general library skill.

**3. Create the skill**

Save the skill. In a review-required workspace, a shared skill remains personal until an admin approves it.

## Bundle supporting files

Use a bundle when the main instructions depend on scripts, reference material, or reusable assets.

**customer-brief**

**SKILL.md**

**scripts**

**normalize-activity.py**

**references**

**brief-standard.md**

**assets**

**brief-template.md**

You can add, replace, download, or remove bundled files from the skill card.

## Write a useful skill

* Name the result: `incident-brief`, not `sre-helper`.
* Describe when the skill applies and what a successful output contains.
* Refer to context and tools by purpose instead of hard-coding one person's paths.
* Keep the main instructions short; move detailed reference material into bundled files.
* Make approval criteria explicit when a mistake would be expensive.

> [card] [Next: Skill governance](https://docs.pctx.ai/skills/governance.md)
>
> Require review, control external imports, and manage the shared library.


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