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

# Importing Skills

> Drag-drop a ZIP, paste a GitHub URL, or pick from the official library.

Skills come into Foundry from three places: a ZIP file, a GitHub repo, or the official library.

<Note>
  **Screenshot coming.** Skill upload dialog with three sources.
</Note>

## Upload a ZIP

The simplest path. In the Skills manager, click **Import → Upload**.

**Accepted formats:** `.zip` or `.skill`. If you drop a **folder**, Foundry zips it for you on the fly.

**What goes in the ZIP:**

```
my-skill/
├── SKILL.md          ← required. The instructions.
├── templates/        ← optional. Files referenced from SKILL.md.
│   └── ...
└── examples/         ← optional. Reference examples.
    └── ...
```

Once uploaded, the skill lands in your library at `skills/<your-user-id>/<uuid>/` (private — only you see it).

## From GitHub

Click **Import → GitHub**, paste a public repo URL. Foundry pulls the repo and treats the root as the skill directory (it expects a `SKILL.md` at the root).

Updates auto-sync as the repo changes — useful when you want a team-shared skill that evolves.

## Official library

Click **Import → Official** to browse skills maintained by IronLabs. One-click install; they live at `skills/official/...` in storage.

## What a SKILL.md looks like

A `SKILL.md` is a prompt — frontmatter + instructions. Example:

```markdown theme={null}
---
name: PDF Summarizer
description: Summarize PDFs into structured one-pagers.
version: 1.0
connector: firecrawl
---

# Role

You are a meticulous PDF summarizer.

# How to behave when active

- When the user attaches a PDF, extract the structure.
- Produce a one-pager: TL;DR, key claims, sources, glossary.
- Cite page numbers for every claim.
```

The optional `connector:` field binds the skill to one of your [connectors](/foundry/connectors/overview) — useful for tool-using skills.

## Tips

* **Start with one `SKILL.md`** and grow. You can add supporting files later.
* **Version it.** Bump `version:` when behavior changes; old chats stay on their original version.
* **Test in a throwaway chat** before activating across your daily drivers.

## Limits

* ZIPs and repos are size-capped (sensible defaults — tens of MB).
* GitHub imports require the repo to be **public**. Private-repo imports are on the roadmap.

## Related

<CardGroup cols={2}>
  <Card title="Skills overview" icon="puzzle-piece" href="/foundry/skills/overview">
    What a skill is.
  </Card>

  <Card title="Using skills" icon="play" href="/foundry/skills/using-skills">
    Activate, stack, manage.
  </Card>
</CardGroup>