Skill Personalizer Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/hqhq1025/skill-optimizer --skill skill-personalizerThe instruction itself
6 sections, as written by the authorSkill 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.
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take hqhq1025/skill-personalizer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.