Skill installer — import a skill from a public repo

The user wants you to import a capability (skill) that already lives in a public repository (github.com / gitlab.com — e.g. the agentskills.io ecosystem like anthropics/skills, awesome-agent-skills). You import it into the user's own skills; the platform clones the repo, scans it for committed secrets, validates the SKILL.md, and installs it.

Say what an import is, before you make one. An imported skill is a set of instructions somebody else wrote that you will then follow, with the connectors this assistant already holds. The platform's scan looks for committed secrets and for a well-formed SKILL.md; it does not vouch for what the instructions ask you to do. So name the repository to the user and tell them that in one line, and import only what they then confirm.

When to activate

Trigger patterns:

• "import the skill from <github/gitlab repo url>"
• "add capability X from "
• "I want to enable the skill from "

Don't activate for:

• writing a new skill from scratch — that's skill-creator
• installing a connector / integration — that's an admin action, not this skill

Stage 1 — get the public repo URL

You need a PUBLIC https://github.com/<owner>/<repo> or https://gitlab.com/<owner>/<repo> URL.

• If the user gives a repo URL, use it.
• If they give just a name ("docx da anthropics"), ask for the exact public repo URL — don't guess.
• Private repos are not supported here; if it's private, tell the user.

If in doubt, show the user the repo you're about to import + ask for a green light.

Stage 2 — import it

call_recipe("skills.import", {
  git_url: "<https://github.com/... or https://gitlab.com/... repo url>"
})

The capability is cloned, secret-scanned, its SKILL.md is validated, and it is installed as the user's OWN skill — usable from the next turn. It returns {ok, skill_id, slug} on success.

Stage 3 — confirm

Tell the user, in plain language, that the capability is now available — refer to it by its name, not by ids or paths.

Failures

• The import is refused if the repository contains a committed secret, the SKILL.md is missing/invalid, or the URL isn't a public github/gitlab repo → explain in plain language and suggest checking the repo.
• A name clash ("a capability with this name already exists") → suggest a different source or tell the user it's already available.

Don't

• Don't paste the full SKILL.md body back to the user — just confirm the name.
• Don't try to fetch / clone the repo yourself via web-fetch or bash — the platform handles clone + secret-scan + validation correctly.
• Don't import from a private or non github/gitlab URL — it's not supported.