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

# Import Skills from GitHub

> Install the Quivly GitHub App, pick a repo, and import SKILL.md files as draft skills. Re-import to sync changes.

Keep your [skills](/product/skills) in a Git repo — reviewed in PRs, versioned, shared — and import them into Quivly with the native GitHub App.

## One-time setup

Connect GitHub under **Settings → Integrations → GitHub**: click **Connect with GitHub** and install the Quivly GitHub App on the repos you want. The app only asks for read access to repository contents. The connection is org-wide — one install serves your whole Quivly organization. Public repos work without an install.

## Importing

From **Settings → AI → Skills → Create → Import from GitHub**:

<Steps>
  <Step title="Pick a repository">
    Browse or search the repos your installation can see.
  </Step>

  <Step title="Review discovered skills">
    Quivly scans for `SKILL.md` files (the [Agent Skills format](/developers/skill-format)) and previews what it found — nothing is written yet.
  </Step>

  <Step title="Attach tools">
    Optionally let AI suggest which Quivly data tools each skill should use — the spec's `allowed-tools` don't carry over.
  </Step>

  <Step title="Import">
    Skills land as drafts. Review and publish them like any other skill.
  </Step>
</Steps>

## Keeping skills in sync

There's no webhook auto-sync — re-importing is the sync:

* **Re-import the repo** — unchanged files are skipped, changed files update the skill's content (never its tools), new files create new drafts.
* **Refetch one skill** — from the skill's page, pull its latest content from GitHub in place.

Skills track their source repo and path, so updates land on the right skill. Failures are per-file: one bad skill doesn't block the rest.

## Limits

* Works comfortably up to \~100 skills per repo.
* Files over 1 MB import with empty instructions.
* `scripts/`, `references/`, and `assets/` folders aren't ingested (skills that have them are flagged).

## FAQ

<AccordionGroup>
  <Accordion title="Does Quivly store a GitHub token?">
    No personal tokens are stored. Access uses the GitHub App's short-lived installation tokens.
  </Accordion>

  <Accordion title="What happens to a skill if its file is deleted from the repo?">
    The skill stays in Quivly. A refetch reports the source as missing and lets you relink it.
  </Accordion>

  <Accordion title="Will re-importing overwrite tools I attached in Quivly?">
    No — updates only touch name, description, and instructions. Tool attachments are never changed by a sync.
  </Accordion>
</AccordionGroup>