/skillify

name: skillify
description: When you want to create, adapt, or update an Agent Skill (Claude Code, Codex, Cursor, and other hosts) in one of your repos (listed in ~/.config/makerskills/skillify/repos.yaml; defaults to makerskills). Modes — CREATE (from chat, video, dump, or scratch) turns a workflow into a new skill. ADAPT ports an external skill with keep/adapt/add classification, license check, and attribution. UPDATE improves existing skills from learnings with cross-skill propagation, memory-vs-skill triage, and semver. Checks new skills for host portability. Triggers on "/skillify," "create a skill," "make this a skill," "skill from this chat," "adapt this skill," "port this skill," "fork this skill," "update X skill," "apply this to the relevant skills," "propagate this learning," "improve [skill]," "fix [skill]." Part of the -ify trifecta (skillify / toolify / loopify).
metadata:
  version: 0.2.1

/skillify — Create, adapt, or update a skill

One skill, three modes. Routes automatically to the right one based on input signal.

Consolidates and replaces the prior `create-skill`, `adapt-skill`, and `update-skill` (all merged as of v0.2.0 for vocabulary-moat consistency with the `-ify` trifecta).

Step 0 — Detect mode

Route by signal:

| Signal | Mode | |---|---| | Invoked mid-conversation with substantive recent workflow discussion | **CREATE / from-chat** (default) | | `/skillify from-video <url>` OR `/skillify` + a video URL | **CREATE / from-video** | | `/skillify from-dump` + pasted brief/transcript/notes | **CREATE / from-dump** | | `/skillify from-scratch <name>` OR "make a new skill called X" with no context | **CREATE / from-scratch** | | `/skillify <github-url>` OR "adapt this skill" / "port this skill" / "fork this skill" + external source | **ADAPT** | | `/skillify <existing-skill> <change>` OR "update X skill" / "propagate this learning" | **UPDATE / targeted** | | `/skillify update` (mid-conversation) | **UPDATE / from-chat** — scan recent chat for learnings | | `/skillify usage <skill>` | **UPDATE / usage** — review recent runs, suggest improvements |

If ambiguous, ask before proceeding. Never guess between CREATE and ADAPT if there's an external URL involved.

---

Mode: CREATE

Build a new skill from chat / video / dump / scratch.

Step 1 — Confirm the input source

| Sub-mode | What | |---|---| | **from-chat** (default) | Extract the skill from the workflow discussed in this conversation. Most common case. | | **from-video** | User recorded a Loom / Zoom / screen-share. Calls `watch-video` in visual mode → transcript + key visual moments → SKILL.md. Best for visual/UI-heavy workflows. | | **from-dump** | User pastes a brief, prior conversation transcript, exported chat, or notes. | | **from-scratch** | Fresh idea with no source material — interactive Q&A. |

Step 2 — Defer to Anthropic guidance for the schema

Don't reinvent SKILL.md format rules. For frontmatter, description-writing, references/ structure, and skill best practices:

• **`compound-engineering:create-agent-skill`** (agent) — expert guidance for creating + editing Claude Code skills
• **`compound-engineering:skill-creator`** (skill) — deeper guide for effective skills
• **`compound-engineering:heal-skill`** (skill) — for fixing existing skills
• **[anthropics/skills](https://github.com/anthropics/skills)** — official Anthropic examples
• **[agentskills.io](https://agentskills.io)** — open Agent Skills spec

Call those directly when in doubt about format. `skillify` orchestrates *your* workflow — which repo, which conventions, which cross-references. Format expertise lives upstream.

Step 3 — Pick target repo

Load the user's sibling repo list from `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/skillify/repos.yaml` if present. Otherwise default to `makerskills` (this repo). Example format:

# ~/.config/makerskills/skillify/repos.yaml
repos:
  - name: makerskills
    domain: Personal cross-cutting operator work
    path: ~/code/makerskills
  - name: marketingskills
    domain: Generic marketing tactics
    path: ~/code/marketingskills

Infer target if obvious from the skill's domain; ask if ambiguous.

Step 4 — Synthesize per sub-mode

**from-chat:** 1. Read backward through this conversation. Look for a workflow repeated multiple times, a process re-explained, opinions restated, tooling/voice/output decisions. 2. Identify the load-bearing pieces: trigger, steps, references, success shape, voice. 3. Surface gaps that need clarification before scaffolding — ask 2–4 tight questions. 4. Draft SKILL.md, citing chat moments inline ("Per your message about X…") so the user can verify.

**from-dump:** 1. Parse the dump (Notion page, Slack thread, Loom transcript, teammate brief, exported ChatGPT conversation). 2. Same synthesis logic as from-chat. 3. Cite where in the dump each rule came from.

**from-video:** 1. Take the URL or local path. 2. Call `watch-video <url> visual` — get transcript + key visual moments + summary. 3. Read outputs: `<workdir>/transcript.txt`, `<workdir>/moments.md`, `<workdir>/summary.md`. 4. Synthesize: trigger (first 30s), steps (visual moments + matching transcript), tools used, decision points ("if X do Y" moments), success shape (last few seconds), voice cadence. 5. Surface gaps — ambiguous moments needing clarification. 6. Draft SKILL.md citing video moments by timestamp. 7. Optionally save the source to `second-brain` as `call-<slug>.md` or `note-<slug>.md`.

Heuristic: recording >10 minutes = process probably too big for one skill. Suggest splitting before drafting.

**from-scratch:** Interactive Q&A: 1. Name (kebab-case, verb-noun preferred — matches `watch-video`, `read-book`, `paste`) 2. One-line purpose 3. Trigger phrases (4–8) 4. Initial reference files? 5. Composes with which other skills?

Step 5 — Generate frontmatter

---
name: <kebab-case>
description: <rich, trigger-rich, ~2–4 sentences. Lead with "When you