skill-exporterlisted

Package an already-installed Claude Code skill from ~/.claude/skills/ into the folder structure required by a shared skills GitHub repo (README.md, SKILL.md, INSTALLATION.md), ready to commit and push. Use this skill whenever the user asks to export, publish, package, or share one of their existing custom skills, wants to "add this skill to my repo" or "make this skill shareable," or names a specific installed skill and asks to prep it for GitHub or hand it to someone else.
DeltaCorvi/Claude-Skills-for-Smart-Crows · ★ 0 · AI & Automation · score 70

Install: claude install-skill DeltaCorvi/Claude-Skills-for-Smart-Crows

# Skill Exporter This skill turns a working, installed Claude Code skill into the three-file bundle a shared skills repo expects: `SKILL.md`, `README.md`, `INSTALLATION.md`. The repo convention (see the target repo's own `README.md` "Contributing" section) is one subfolder per skill, self-contained, so anyone can copy just that folder and install it. The goal is fidelity, not polish. The installed skill already works: the job here is packaging it so someone else can install and understand it, not rewriting its behavior. ## Step 1: Identify the source skill If the user names a skill, look for it at `~/.claude/skills/<name>/SKILL.md` (check plugin-scoped paths too if the skill was installed via a plugin). Read the whole file: frontmatter and body. If the user hasn't named a skill, or the file can't be found in this environment, ask them to point you at it or paste the `SKILL.md` content directly. Don't guess at a skill's behavior from memory: the exported copy needs to match what's actually installed, not a paraphrase. Check the skill's directory for bundled resources (`scripts/`, `references/`, `assets/`) alongside `SKILL.md`. Note anything found: a skill with bundled scripts needs those files copied into the exported folder too (e.g. under a matching `scripts/` subfolder), not just the prose. ## Step 2: Determine the target folder name Use the skill's `name` field from its own frontmatter as the folder name, kebab-case, matching the convention already used in the repo