skill-customize

Record and display persistent per-skill customisation instructions stored as markdown extras files.

Updated May 26, 2026
One-click install
npx skills add https://github.com/cagriy/dev-skills --skill skill-customize-cagriy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-customize
Source: https://github.com/cagriy/dev-skills/tree/main/skills/skill-customize
Command: npx skills add https://github.com/cagriy/dev-skills --skill skill-customize-cagriy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preferences stated mid-run to a dev-skills skill die with that run. This Skill turns a one-off instruction like "always draw three alternatives" into a durable per-skill customisation file that the target skill reads at the start of every future run, without forking or editing any SKILL.md. ## Core Features & Use Cases - Record customisations: Capture a behaviour change in the user's own words, normalise it into imperative bullets, and write it to <slug>.extras in the plugin data directory. - Show recorded customisations: Print the existing extras file verbatim in a fenced block when the user asks what has been customised. - Safety enforcement: Refuse any instruction that collides with the target skill's non-negotiable constraints, relaxes a safety rule, or disables a load-bearing step. - Use Case: Tell the plugin "make /feature-mockup always draw three alternatives" and the instruction is persisted so every future mockup run applies it automatically. ## Quick Start Ask the assistant to record a lasting customisation for a specific dev-skills skill, for example by saying you want /feature-design to always produce two alternatives.

Frequently Asked Questions about skill-customize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I permanently change how a dev-skills skill behaves?

Run /skill-customize with the skill's slug and your instruction, for example "/skill-customize feature-mockup always draw three alternatives". The instruction is written to a per-skill extras file that the target skill reads at the start of every future run.

How do I see what customisations I have recorded for a skill?

Run /skill-customize with the slug followed by "show", for example "/skill-customize feature-design show". The skill prints the extras file verbatim in a fenced block, or tells you in one line that no customisations are recorded.

Can a customisation override a skill's non-negotiable constraints?

No. Customisations refine behaviour but never override rules a skill marks non-negotiable. An instruction that contradicts a constraint, relaxes a safety rule, or disables a load-bearing step is refused at write time with the collision named.

Where are skill customisation files stored?

Each customisation lives in a single markdown file named <slug>.extras inside the plugin's data directory, resolved from the CLAUDE_PLUGIN_DATA location. Nothing is written to the project, and no commits or pushes are made.

What happens if I give an unknown or misspelled skill name?

The slug is validated against the skills directory on disk. A near-miss triggers a one-time confirmation question with candidate matches, and an unknown name with no close match stops the skill with the list of accepted slugs.