skill-createlisted

Create a new skill in this claude-skills collection, from scaffolding through a lightweight trigger/dry-run test before commit. Use when the user wants to turn a workflow they just did into a reusable skill, capture a repeated process, or add a new skill to their toolbox. Applies this collection's conventions (domain prefixes, description-with-triggers, just install) plus skill-authoring practices from Anthropic's skill-creator (progressive disclosure, trigger-tested descriptions, bundled scripts/references/assets). Triggers on phrases like 'make this a skill', 'create a skill for this', 'save this as a skill', 'add a new skill', 'turn this workflow into a skill'.
Srltas/claude-skills · ★ 0 · AI & Automation · score 69

Install: claude install-skill Srltas/claude-skills

# Create a new skill in claude-skills Scaffold a new skill and write a complete, trigger-tested `SKILL.md` (plus `scripts/`, `references/`, `assets/` when the skill needs them) from the surrounding context. This layers Anthropic skill-creator practices onto the collection's own conventions. ## Step 1: Find the collection root Walk up from the current directory looking for a `justfile` that contains `npx skills add`. That directory is the collection root. If none is found, ask the user for the collection path. ## Step 2: Derive the skill name From `$ARGUMENTS` (or, if empty, from the workflow gathered in Step 4): - Drop filler words: `a`, `the`, `this`, `that`, `skill`, `make`, `save`, `as`, `create`. - Convert to an imperative verb + object, lowercase and hyphenated: e.g. "a skill that checks migration parity" → `check-parity`. - Apply the domain prefix from the collection's convention: - `hhh-`: Hibernate ORM / dialect work - `cmt-`: CUBRID Migration Toolkit (runs, schema/data parity) - `jdbc-`: CUBRID JDBC driver - `cubrid-`: general CUBRID (manual, containers) - no prefix: truly general-purpose Propose the candidate name and wait for confirmation before continuing. ## Step 3: Check for conflicts Confirm `<collection-root>/<skill-name>/` does not already exist. If it does, ask whether to update the existing skill or pick a new name. ## Step 4: Gather context From the current conversation, collect: - **Workflow**: the exact sequence of commands, tools,