skill-creatorlisted

Create, migrate, adapt, test, and improve skills in Claude Code plugin repositories, especially skill-forge. Use when users ask to create or update a skill, migrate an upstream skill, compare official skills, design RED/GREEN verification, run skill evals, benchmark skill behavior, optimize triggering descriptions, or package a skill/plugin.
gzb1128/skill-forge · ★ 1 · AI & Automation · score 77

Install: claude install-skill gzb1128/skill-forge

# Skill Creator This Skill Forge adaptation is modified from Anthropic's Apache-2.0 `skill-creator`. Keep the bundled license files with copied upstream resources. Use this skill to create or improve skills as durable agent runtime assets, not as one-off prompt text. Prefer the local repository's plugin and verification conventions over upstream defaults whenever they conflict. ## First Decision Identify the target before editing: | Target | Source of truth | Verification | |---|---|---| | Skill Forge plugin skill | `plugins/<plugin-name>/skills/<skill-name>/SKILL.md` | `python3 .../quick_validate.py <skill-dir>`, `git diff --check`, `make validate`, and relevant `docs/verify` scenario | | New Skill Forge plugin | `plugins/<plugin-name>/.claude-plugin/plugin.json` plus `skills/<skill-name>/` | Marketplace entry, README/AGENTS updates, `make validate` | | Existing installed skill | Copy or patch the editable source repository, not the cache path | Use the source repo's validation first | | Standalone `.skill` package | Skill folder with `SKILL.md` and optional resources | `scripts/package_skill.py` only when the user asks for a `.skill` artifact | In `skill-forge`, plugin directories use `.claude-plugin/plugin.json`, not `.codex-plugin/plugin.json`. Plugins intentionally omit `version`; Claude Code resolves installed versions to git commit SHAs. ## Skill Forge Defaults - Keep project-facing content in English. - Do not migrate an official skill just because it exists u