Skip to main content

Install a Skill from GitHub

Your Bankr agent can install skills directly from any public GitHub repository — or from a bankr.bot skill link. This is the fastest way to add a new capability: point your agent at a repo or a link, and it pulls the skill in.

Install in one message​

Tell your agent the GitHub URL of the skill you want:

install the skill at https://github.com/owner/repo/tree/main/path/to/skill
install the botchan skill from https://github.com/BankrBot/skills/tree/main/botchan
install the erc-8004 skill from https://github.com/BankrBot/skills/tree/main/erc-8004
install the skill at https://github.com/your-org/your-repo/tree/main/your-skill

Your agent will:

  1. Fetch the SKILL.md file from the URL.
  2. Pull in any files in the skill's references/ folder.
  3. Save the skill to your agent so it's available in future conversations.

Reinstalling from the same source replaces the installed copy — that's how updates work. If you already have a different skill with that name (one you wrote yourself, or one from another source), the install is refused so it can't overwrite it: rename or delete yours first.

What URLs work​

The URL should point to a public GitHub repo, folder, or skill file. All of these are accepted:

  • A tree/<branch>/<path> folder URL containing a SKILL.md at its root
  • A plain https://github.com/owner/repo — the agent uses the SKILL.md at the root, or the only one in the repo; if there are several, the install lists them so you can pick one with a tree/ URL
  • A blob/<branch>/<path>/SKILL.md URL — blob URLs are auto-rewritten to their raw equivalent, so they work too
  • A direct https://.../skill.md file URL (including non-GitHub hosts)
  • Bare owner/repo GitHub shorthand, a GitLab URL, or a git@host:owner/repo SSH URL

The skill folder can also include a references/ subfolder of supporting markdown — those files are pulled in alongside SKILL.md and become available to your agent on demand.

You can also paste a link straight out of Bankr's own skills UI — no GitHub URL needed. Each shape installs the skill the page shows:

  • https://bankr.bot/terminal/skills/<slug> — a Discover page
  • https://bankr.bot/terminal/skills/partner/<partner> — a partner page, which installs that partner's flagship skill
  • https://bankr.bot/skills/<wallet>/<slug> — the public share link from the skill drawer's Copy share link button
install https://bankr.bot/terminal/skills/partner/<partner>

If a link doesn't match a catalog entry, the agent says so rather than trying to fetch the page — a mistyped slug gives you a real error, not a format complaint.

For the full file format, see the SKILL.md format reference.

After installation​

Once installed, your agent will use the skill automatically when a request matches what the skill describes. You can also review or remove installed skills in the Installed skills tab of the terminal's Skills section — see Create a skill manually for the same UI from the create side.

Suggested skills​

Bankr curates a short list of skills for requests the agent can't handle natively. When you ask for something one of them covers and you haven't installed it, the agent names the skill and offers to install it — and installs it only if you agree. Where the agent can't install skills — for example on a read-only API key — it doesn't make the offer.

Limits​

  • SKILL.md is capped at 1 MB; a larger one fails the install.
  • Each references/ file is capped at 100 KB. An oversized reference is skipped and named in the install result, and the rest of the skill still installs. A skill holds up to 30 references; past that you can't add more, though a larger existing install still saves.
  • Other files in the skill folder (scripts, templates, data) are copied into your file storage under /skills/<skill-name>/, up to 2 MB per file and 5 MB per skill; files past either cap are skipped and named.
  • You can have up to 50 skills. If you hit the cap, remove an unused one in the Skills section and retry.

Troubleshooting​

"SKILL.md not found"​

Confirm the URL points to a folder that has a SKILL.md file at its root, or directly to a SKILL.md file, and that the branch in a tree/ URL exists. GitHub blob/ URLs are accepted (they're rewritten to their raw form automatically). The repository must be public — a private repo reads as not found, so copy its contents into a skill manually instead.

The skill installed but my agent isn't using it​

Skills are loaded by description match. If the skill's description frontmatter doesn't mention the kind of request you're making, your agent may not pick it up. Tell it explicitly:

use the <skill-name> skill to ...

If that works, consider rewriting the skill's description field so it triggers automatically next time.

Next steps​