Skill Personalizer
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.
MCP get_skill({ skillId: "skill-personalizer-579bf8ae" })Use this skill with your agent
Create a free account and connect via MCP
# 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 1. Inspect the target skill, installed copies, local memories, and real session evidence when available. 2. Run the audit checks in [audit-rubric.md](references/audit-rubric.md) when quality, trigger fit, or retention is unclear. 3. Identify the user's recurring phrasing, expected autonomy level, tools, directories, and verification habits. 4. Compare the skill's trigger conditions against real user requests that should or should not load it. 5. Edit only the target skill and bundled resources needed for personalization. 6. Add concrete local defaults, preferred commands, safety boundaries, and verification steps. 7. Preserve useful upstream behavior; document any intentional local divergence. 8. 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](references/audit-rubric.md) for the diagnostic pass inherited from the original optimizer. Read [personalization-rubric.md](references/personalization-rubric.md) for local defaults, session evidence, and validation scenarios.
Related Skills
More skills in Personal Productivity
Academic Cv Builder
Format CVs for academic positions with publications, grants, and teaching
Act Informed: First understand together with the human, then do
Interactive, input-tool powered, task refinement workflow: interrogates scope, deliverables, constraints before carrying out the task; Requires the Joyride extension.
Add Multiple Attendees to a Calendar Event
Add a list of attendees to an existing Google Calendar event and send notifications.
AgentMail — Agent-Owned Email Inboxes
Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-owned email addresses (e.g. hermes-agent@agentmail.to).
Agent Mail Automation via Rube MCP
Automate Agent Mail tasks via Rube MCP (Composio). Always search tools first for current schemas.
Airtable
Airtable REST API via curl. Records CRUD, filters, upserts.
Explore Other Categories
Skills from other categories with shared topics
Skill Generalizer
Use when turning local, private, or personal Agent Skills into publishable skills for GitHub, marketplaces, teams, or public sharing, especially when private paths, personal habits, credentials, internal hosts, or user-specific context must be removed.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Add New Opc Skill
Checklist and automation guide for adding a new skill to the OPC Skills project. Ensures all required files, metadata, logos, and listings are created before release. Use when adding a new skill, publishing a skill, or preparing a skill for release.