addskilllisted

# Add skill — install a skill into this repo Skills only appear in a Claude Code web session if they're committed to `<repo>/.claude/skills/<name>/`. Personal installs (`~/.claude/skills/`) and CLI-only plugins do NOT follow the user to the web. The fix is always: put the skill folder in the repo and commit it. ## Step 1: Confirm the skill source Ask the user (or infer from `$ARGUMENTS`) where the skill content comes from: - **A name + description** the user wants you to author from scratch - **An existing local folder** (e.g. `~/.claude/skills/<name>/`) to copy in - **A third-party skill** (e.g. `superpowers`) — these usually ship via a Claude Code plugin marketplace. Ask the user for the source URL/repo. Do NOT invent contents. If the source is ambiguous or the user only gave a name you don't recognize, ask once before authoring. ## Step 2: Create the skill folder Skill location is **always**: ``` /<repo-root>/.claude/skills/<skill-name>/SKILL.md ``` - Folder name is the skill name as it will appear after `/` (kebab-case, no spaces). - The file MUST be named `SKILL.md` (capitalized exactly). - Sub-files (helper scripts, references) are allowed in the same folder. ``` mkdir -p .claude/skills/<skill-name> ``` ## Step 3: Author SKILL.md Required structure — YAML frontmatter then markdown body: ````markdown --- description: One-paragraph description. Lead with what the skill does, then the trigger phrases ("Use when the user says /<name>, asks to ..."). The harness