Skill Personalizer

Overview

Audit and tune a skill for one user's real environment. The goal is not public portability; it is better triggering, less friction, and stronger fit with the user's actual tools, paths, style, and recurring tasks.

When To Use

• A user installs a skill from GitHub or creates one from scratch and wants it to fit their setup.
• A skill undertriggers, overtriggers, asks unnecessary questions, or misses the user's preferred workflow.
• A user asks whether an existing skill is good, broken, noisy, too long, conflicting, or worth keeping.
• Local paths, aliases, memories, CLIs, MCP tools, or repo conventions should be reflected in the skill.

Do not use when preparing a skill for public release; use skill-generalizer for that.

Workflow