Import a skill from GitHub

Import an existing skill from a GitHub repository or subfolder. The skill stays linked to the source, so pushing to GitHub updates the skill the next time you sync.

Import from a repository

Go to Skills and click Add skill.

Paste the GitHub URL

Paste a repo URL (https://github.com/owner/repo) or a subfolder URL (https://github.com/owner/repo/tree/main/skills/my-skill). The path you point at must contain a SKILL.md at its root.

Import

Click Import.

Your skill appears in Skills, synced from the source repo.

The SKILL.md at the URL is required. MCP Market also pulls every other file in the same folder (such as a references/ directory or scripts), so multi-file skills work as long as the entry point is SKILL.md. Files outside the folder you pasted are not imported.

Files must be text, except for these binary types: images (.png, .jpg, .jpeg, .gif, .webp, .ico) fonts (.ttf, .otf, .woff, .woff2), PDFs (.pdf), and Office files (.docx, .pptx, .xlsx). Each file can be up to 512,000 bytes, and a skill can have up to 50 files and 5,242,880 bytes in total. If any file doesn't fit these rules, the import stops and lists the files to remove.

PDF and Office attachments keep their bytes unchanged. MCP Market does not inspect, repair, or scan their contents. Whether an assistant can open them depends on the client.

Read-only behavior

Imported skills are read-only in MCP Market. Updates pushed to the source repo are picked up the next time you sync.

You can still install the skill into toolkits and download specific versions. To switch the source repo for an existing skill, delete the skill and re-import from the new URL.