Skip to main content
Keep your 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:
1

Pick a repository

Browse or search the repos your installation can see.
2

Review discovered skills

Quivly scans for SKILL.md files (the Agent Skills format) and previews what it found — nothing is written yet.
3

Attach tools

Optionally let AI suggest which Quivly data tools each skill should use — the spec’s allowed-tools don’t carry over.
4

Import

Skills land as drafts. Review and publish them like any other skill.

​
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

No personal tokens are stored. Access uses the GitHub App’s short-lived installation tokens.
The skill stays in Quivly. A refetch reports the source as missing and lets you relink it.
No — updates only touch name, description, and instructions. Tool attachments are never changed by a sync.