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
- Inspect the target skill, installed copies, local memories, and real session evidence when available.
- Run the audit checks in audit-rubric.md when quality, trigger fit, or retention is unclear.
- Identify the user's recurring phrasing, expected autonomy level, tools, directories, and verification habits.
- Compare the skill's trigger conditions against real user requests that should or should not load it.
- Edit only the target skill and bundled resources needed for personalization.
- Add concrete local defaults, preferred commands, safety boundaries, and verification steps.
- Preserve useful upstream behavior; document any intentional local divergence.
- Validate with realistic prompts and a frontmatter/layout check.
Personalization Rules
- Personal details are allowed only if they improve this user's future execution.
- Do not add brittle fallbacks that hide broken local setup.
- Prefer real local evidence over generic best practices.
- Keep trigger descriptions broad enough to catch the user's natural phrasing.
- If editing an installed third-party skill, avoid changing upstream attribution or license text.
References
Read audit-rubric.md for the diagnostic pass inherited from the original optimizer.
Read personalization-rubric.md for local defaults, session evidence, and validation scenarios.
1---2name: skill-personalizer3description: Use when auditing or adapting newly created, downloaded, forked, installed, or community Agent Skills to the user's tools, habits, directories, session history, and preferred workflows, especially when triggers feel wrong, noisy, or too generic.4---5
6# Skill Personalizer
7
8## Overview
9
10Audit 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.
11
12## When To Use
13
14- A user installs a skill from GitHub or creates one from scratch and wants it to fit their setup.
15- A skill undertriggers, overtriggers, asks unnecessary questions, or misses the user's preferred workflow.
16- A user asks whether an existing skill is good, broken, noisy, too long, conflicting, or worth keeping.
17- Local paths, aliases, memories, CLIs, MCP tools, or repo conventions should be reflected in the skill.
18
19Do not use when preparing a skill for public release; use `skill-generalizer` for that.
20
21## Workflow
22
231. Inspect the target skill, installed copies, local memories, and real session evidence when available.
242. Run the audit checks in [audit-rubric.md](references/audit-rubric.md) when quality, trigger fit, or retention is unclear.
253. Identify the user's recurring phrasing, expected autonomy level, tools, directories, and verification habits.
264. Compare the skill's trigger conditions against real user requests that should or should not load it.
275. Edit only the target skill and bundled resources needed for personalization.
286. Add concrete local defaults, preferred commands, safety boundaries, and verification steps.
297. Preserve useful upstream behavior; document any intentional local divergence.
308. Validate with realistic prompts and a frontmatter/layout check.
31
32## Personalization Rules
33
34- Personal details are allowed only if they improve this user's future execution.
35- Do not add brittle fallbacks that hide broken local setup.
36- Prefer real local evidence over generic best practices.
37- Keep trigger descriptions broad enough to catch the user's natural phrasing.
38- If editing an installed third-party skill, avoid changing upstream attribution or license text.
39
40## References
41
42Read [audit-rubric.md](references/audit-rubric.md) for the diagnostic pass inherited from the original optimizer.
43
44Read [personalization-rubric.md](references/personalization-rubric.md) for local defaults, session evidence, and validation scenarios.
majiayu000