coreyhaines31/makerskills / skills/skillify
skillify
VerifiedWhen 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. TEST role-plays users through a skill and judges transcripts against a rubric. Checks new skills for host portability. Triggers on "/skillify," "create a skill," "make this a skill," "adapt this skill," "port this skill," "update X skill," "propagate this learning," "improve [skill]," "fix [skill]," "test this skill," "exercise [skill]." Part of the -ify trifecta — integrations and MCP servers go to toolify, schedules and loops to loopify.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 22.3 KB |
| references/adapt-buckets.md | markdown | 3.5 KB |
| references/adapt-license-check.md | markdown | 3.1 KB |
| references/test-rubric.md | markdown | 8.0 KB |
| references/update-change-types.md | markdown | 4.4 KB |
| references/update-propagation.md | markdown | 5.2 KB |
| references/update-versioning.md | markdown | 3.0 KB |
references/adapt-license-check.md
View on GitHub# License check
Run this before adapting. Skill defaults to **stop** on unclear or restrictive licenses — don't proceed without explicit the user approval on red cases.
## Policy
| License | Action | Why |
|---|---|---|
| **MIT** | ✅ Proceed | Permissive. Requires only attribution + license notice. |
| **Apache 2.0** | ✅ Proceed | Permissive. Requires attribution + NOTICE file. |
| **BSD (2-clause, 3-clause)** | ✅ Proceed | Permissive. Requires attribution. |
| **ISC** | ✅ Proceed | Equivalent to MIT. |
| **CC0 / Public Domain** | ✅ Proceed | No attribution required (but include anyway for credit). |
| **Unlicense** | ✅ Proceed | Public domain equivalent. |
| **MPL 2.0** | 🟡 Warn | File-level reciprocity — modified MPL files must stay MPL. Adapt sparingly; consider rewriting from scratch instead of copying. |
| **LGPL** | 🟡 Warn | Library-linking exception, but skill files would be derivative. Usually rewrite from scratch is cleaner. |
| **GPL 2.0 / 3.0** | ❌ Stop | Strong copyleft — adaptation creates a derivative work that must also be GPL. Stops your repo from being your-license-of-choice. Surface to the user. |
| **AGPL** | ❌ Stop | Even stronger — network-use clause triggers. |
| **Custom / proprietary** | ❌ Stop | No legal basis to copy. |
| **No LICENSE file** | 🟡 Warn | Default copyright = no rights. Don't copy. Ask author OR rewrite from scratch using only the *ideas* (not the text). |
| **Unclear / conflicting** | 🟡 Warn | Surface to the user for a call. |
## Detection script
```bash
# In the source repo
curl -s "https://api.github.com/repos/<owner>/<repo>/license" | jq -r .license.spdx_id
```
Or read the LICENSE file directly:
```bash
cat <repo>/LICENSE | head -5
```
Standard SPDX identifiers: `MIT`, `Apache-2.0`, `BSD-2-Clause`, `BSD-3-Clause`, `ISC`, `MPL-2.0`, `LGPL-3.0`, `GPL-2.0`, `GPL-3.0`, `AGPL-3.0`, `CC0-1.0`, `Unlicense`.
## Required artifacts per license
**MIT / BSD / ISC**: copy the LICENSE text into `references/attribution.md` (or as a separate `LICENSE-<source-name>` file in the skill dir). Include the copyright line verbatim.
**Apache 2.0**: same as MIT + copy any `NOTICE` file from the source.
**CC0 / Unlicense / Public Domain**: attribution not required, but include in `attribution.md` for credit.
**MPL / LGPL / GPL**: don't proceed without the user's explicit call.
## When the source has no license
This is the most common case for skills on personal GitHub repos. Treat it as ❌ red:
- Default copyright applies — you have *no* right to copy or redistribute
- Options:
1. **Open an issue / PR** asking the author to add a permissive license
2. **Email / DM** the author and ask permission, save the response
3. **Rewrite from scratch** using only the *ideas* (mechanics, concepts) — not the text. Then it's a fresh independent work that happens to be similar. Document this clearly in `attribution.md` so it's not confused with a port.
## Edge case: skills you wrote yourself in another context
If the source is YOUR OWN code in another repo of yours (e.g., personal note → adapt for a sibling plugin), license doesn't apply. Skip this step and just attribute for traceability.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |