planning-with-files
Optional persistent file-based planning for multi-phase or long-running work that benefits from recovery across sessions or…
Create or update portable agent skills and their supporting resources.
$ npx -y skills add khaneliman/khanelinix --skill skill-creator --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/skill-creatorContext preview
The summary Claude sees to decide when to auto-load this skill.
Create or update portable agent skills and their supporting resources.
name: skill-creator description: Create or update portable agent skills and their supporting resources. license: Complete terms in LICENSE.txt metadata: disable-model-selection: "true"
Create skills that supply non-obvious guidance for a defined task. Preserve the user's scope, existing authorization, invocation metadata, and licenses. Assume the agent can handle ordinary programming and tool use.
supported feature or broad keywords that attract unrelated tasks.
supporting references with a clear read condition. Do not load all modes.
sequences for fragile operations or concrete correctness constraints.
detail, and assets for reusable output. Inspect callers before removing existing resources. Do not add empty scaffolding or duplicate documentation.
unless the user requests explicit-only invocation. Sensitivity alone is not a discovery gate; check authorization before the consequential action.
Use the request and existing package to establish the trigger, output, and constraints. Ask only when missing information materially affects the result. A narrow update may need only an edit and focused validation, not initialization or package planning. Do not turn a past example into a universal requirement.
For new packages, use `scripts/init_skill.py` when it helps. Preserve a requested location and create only resources with a current use. Use `scripts/package_skill.py` only when an archive is part of the requested output.
placement and degree-of-freedom decisions.
files and resource types.
substantially revised package, adapting its steps to the task.
[output-patterns.md](references/output-patterns.md) when a workflow or output contract needs examples.
Run `scripts/quick_validate.py <skill-dir>`. Check reference reachability, metadata preservation, and trigger precision. Run new or changed scripts against representative inputs. Structural validation does not prove useful behavior.
For a complex or risky skill, use an independent agent with a realistic request and raw artifacts when delegation is available. Do not supply the intended answer. Keep evaluation side effects within the authorized scope, inspect the result, and revise only where observed behavior warrants it.
Run packages directly with: Or install from the packages output. For example:
Optional persistent file-based planning for multi-phase or long-running work that benefits from recovery across sessions or…
Audit coding-agent sessions and mine cross-harness history for recurring corrections, skill-routing gaps, and harness faults. Use…
Design and audit agent instructions, skills, plugins, subagents, prompts, hooks, and provider configuration. Use for AI-tool…
Sketch interfaces, state, and module structure before code. Use for explicit design-led implementation or as a caller-owned…
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena,…
Bevy workflows for ECS, migrations, first-party UI/input/rendering/assets/shaders, plugin selection, scenes, scheduling, hot…