import-skill

# Import a skill Turn what the guardian brings you into something installed — a URL to an existing skill, a pasted SKILL.md, or a description of one they wish existed. Brainstorm with them: propose, listen, revise. Don't install anything without getting a clear go-ahead. Most of what you're handed is a plain skill for the user-skills carrier. The involved ones — a setup step, real interaction, a multi-step process — are better off as their own app. Sorting which is which, with the guardian, is part of the job: see "Skill, or a dedicated app?" before you install. ## Classify the input - **URL** → see "Resolving a URL". - **Pasted SKILL.md** (frontmatter + body, or close to it) → validate, preview. - **Description** (prose, a wish, a workflow explained) → see "Generating". - **Empty or ambiguous** → ask one short question. Don't guess. ## Resolving a URL - `github.com/<owner>/<repo>/blob/<ref>/<path>` → fetch the raw form `https://raw.githubusercontent.com/<owner>/<repo>/<ref>/<path>`. - `github.com/<owner>/<repo>/tree/<ref>/<dir>` → list it via `https://api.github.com/repos/<owner>/<repo>/contents/<dir>?ref=<ref>` and download the SKILL.md plus its auxiliary files. - Bare repo → look for `SKILL.md` at the root, then under `skills/`. - Anything else → fetch it; if it's skill-shaped, proceed; if it's prose describing a workflow, offer to generate a skill from it. If the source holds more than one skill (several `SKILL.md` under `skills/`, a repo of them, a page l...