SkillGild vs free GitHub agent skills: which fits your workflow?

Choose a free GitHub skill when you want to read, edit and run the whole workflow yourself. Choose a hosted SkillGild skill when you want a documented input schema, a common sign-in and connection path, and capabilities whose implementation stays on a server. Many teams use both. This guide compares the two on setup, dependencies, source access, maintenance and cost, and says where we have not measured anything.

#The short answer

Neither column is a general winner. We have not run a controlled test of one against the other, so this page makes no claim that either is faster, more reliable or more secure.

#Different tools play different roles

Comparing these options only makes sense once you separate what each one does.

• A GitHub repository is where a skill's source lives. GitHub provides repository search, READMEs, releases and distribution tools. A repository may document its own installer. Account requirements and run limits depend on the workflow and any services it calls.
• A skill directory helps you find skills in repositories. skills.sh describes itself as a directory of reusable capabilities for agents with a single-command installer, and points to skills hosted on GitHub. SkillsMP describes itself as a marketplace that aggregates open-source skills from GitHub repositories and offers browsing, a REST API and an MCP server. Both were checked on October 4, 2026. Neither page states a review or vetting process, so treat that field as unknown.
• SkillGild is a catalog with a hosted runtime. Its public listings show a license and creator credit, and some skills depend on server tools that SkillGild runs. Skills in the catalog are published after review; that review is not a security certification.
• Hosted MCP infrastructure is a different category again, covered below.

#Discovery

Free agent skills are spread across repositories, so discovery depends on GitHub search, curated lists and directories. Our marketplace shortlist compares those discovery options with hosted catalogs. A directory widens what you can find; it does not tell you whether a given skill fits your task or still works.

SkillGild's catalog is smaller and curated. Each listing has a description, a public input schema and its current allowance. Browse the catalog or collections, or read the selection guide for the ten free hosted skills we checked on October 4, 2026.

#Installation

A local skill is a folder you place where your client looks for it, for example .claude/skills/<name>/ in Claude Code or .agents/skills/<name>/ for Codex. Copy the entire folder, because scripts and references may sit beside SKILL.md. See how to install Claude Code skills and the Codex guide.

A hosted SkillGild skill needs more steps, and we will not call them one-click. You install the CLI, run skillgild login, register the MCP server with your client and install the wrapper. The CLI currently builds from source and needs Go 1.26 or later; prebuilt binaries are listed as coming soon. The CLI skills overview shows the sequence for each client.

We have not timed either route. If you want a real number for your own setup, time both on one task and one machine, and note the repository, version and client you used. Do not rely on any figure that comes without those details.

#Execution and dependencies

Downloaded skills give your agent local instructions and supporting files. Their scripts can run locally or call remote APIs and MCP services. Dependencies may include Python packages, renderers, command-line tools or external accounts. Check the author's README, dependency files, installation checks and support channels; their completeness varies by repository.

SkillGild's hybrid skills split the work. Your own agent and model do the reasoning and local file work, and may need local libraries or renderers. Hosted tool calls handle the protected capabilities. Prompt skills run remotely and return a result. See agent skills vs MCP servers for the distinction. A hosted skill therefore depends on SkillGild being reachable and on your account's allowance, which a local file never does.

#Source access and customization

This is where free GitHub skills are clearly stronger. In a public repository, you can read the bundled source, fork the folder and change its instructions. External proprietary services may keep their implementations private. Keeping a local copy preserves those files if the author disappears, but does not keep external dependencies available. License terms still apply, so check the repository's license before reusing or redistributing a skill.

A hosted skill is not a good fit if you need to modify its internals. You can read the wrapper and the public schema, and you can wrap or adapt your own workflow around it, but protected prompts and server tool code stay hosted. That reduces direct copying; it does not stop someone from approximating a skill's behaviour from its outputs.

#Maintenance

For a free GitHub skill, maintenance is whatever the author provides. Check the repository's last commit, open issues and license. A recent commit is not a guarantee, and an old one does not always mean the skill is broken.

For a hosted skill, creators maintain their listing and SkillGild reviews submissions. That review does not establish a security certification, a reliability guarantee or a maintenance SLA, and we do not claim one. We also do not publish a statistic on how many free tools are abandoned, because we have not measured it.

#Costs and allowances

Copying a free skill costs nothing, but running it uses your agent's model, which you pay for or have an allowance for.

SkillGild's free hosted skills each included 25 free runs a month when we checked the catalog on October 4, 2026. Your agent's own model costs are separate from SkillGild access. Check each listing and the pricing page for current terms before you rely on an allowance.

#MCP infrastructure is a separate category

Some platforms host MCP servers rather than curate skills. They solve a different problem: running and managing a server that exposes tools.

• Glama documents hosting for MCP servers, with container deployment from a registry, GitHub, Docker, npm or PyPI, an authentication gateway, access control and call logging.
• Smithery documents managed MCP connections, including credential handling, and a registry where developers publish MCP servers.
• GitHub documents that Copilot supports MCP, including local and remote servers, with a stated limit on remote servers that use OAuth.

These are not interchangeable with a skills catalog. A skill describes a method. These platforms help you run or reach a tool. A workflow can use both, as SkillGild itself does by delivering skills over MCP. All three pages were checked on October 4, 2026.

#Who should choose which

Choose a free GitHub skill if you want to read and change the source, you already know what you need, you are comfortable setting up its dependencies, or you need a workflow that works with no hosted service.

Choose a hosted SkillGild skill if you want a listed workflow with a documented input schema, one account and connection for several skills, and a capability whose implementation you do not need to maintain.

Use both if you keep your own instruction files for team conventions and add a hosted skill for a specific job. For example, a local project skill can set your repository's standards while Academic Plotting handles figure work. The research plots walkthrough shows what that kind of task looks like.

#What we have not measured

Everything above is based on product behavior and each source's own documentation. We have not measured setup time, success rate, output quality or cost per task across these options, and we have no customer ratings to report. When we do measure, we will record the repository, version, client and task so you can repeat it.

#Next steps

• Browse the skills catalog and open a listing to read its inputs.
• Follow the Claude Code installation guide for local or hosted setup.
• Read Claude skills and workflow examples if you are new to skills.