How do I install the Customize skill?

Run npx skillmds@latest add xuzhougeng/customize in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Customize safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Customize?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Customize free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Customize?

xuzhougeng (@xuzhougeng) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Customize by xuzhougeng — Agent Skill

Name: Customize
Rating: 4.2 (5 reviews)
Author: xuzhougeng

Customize

Create a Wisp specialist or author a project-local skill using the tools Wisp actually exposes. Use when the user wants a custom Agent persona, a restricted specialist loadout, a new skill, or changes to an existing project-local skill.

xuzhougeng 3df94e0 2.9 KB Updated Sep 9, 2026

File contents

Customize Wisp

Wisp exposes customization through explicit tools and Settings UI. Python has no control-plane SDK. Never invent profile, connector, or skill CRUD methods.

Create a specialist

Use save_specialist only when it is advertised in the current session.

Ask what single job the specialist owns and what it must not do.
Draft a display name, one-line description, and concise instructions that extend Wisp's base prompt.
Decide whether to inherit project skills/connectors or use explicit whitelists. Use exact installed skill names returned by search_skills. Include connector names only when the user supplied or confirmed them.
Show the complete proposal and obtain confirmation before creating or updating it.
To edit an existing specialist, call configure with action=get and key specialists, then save_specialist with that id. Omit id to create. Builtin instruction text cannot be replaced.
Call save_specialist with name and instructions; add description, model_id, skills, or connectors only when intentionally chosen.
Report the returned specialist id. Deletion, icons, and color still live under Settings → Specialists.

Omit skills and connectors to inherit project settings. An empty list is an explicit zero-access whitelist and is not equivalent to omission.

Author or update a skill

Load skill-creator. For a project-local skill, edit files under:

.wisp/skills/<skill-name>/SKILL.md

Use read, write, and edit. search_skills and use_skill are discovery and loading tools, not mutation tools. If a newly created project skill is not visible immediately, refresh or reopen the project so Wisp rebuilds its skill index.

For a user-wide skill, create the folder in the project first, validate it, then ask the user to install that folder through Settings → Skills. Wisp copies installed skills to its user skill directory; there is no Agent-side publish or delete interface.

Custom appearance

For a user stylesheet (hide the lead bar, restyle chat, override tokens), load custom-theme. Write CSS that uses documented tokens, then apply it with configure set custom_css or ask the user to import the file under Settings → Appearance.

Boundaries

Do not modify Wisp's SQLite store directly.
Do not use python, shell, or run_in_context to bypass Settings or tool authorization.
Do not promise conversation identity switching; the user selects specialists through Wisp's UI.
Do not claim connector enumeration when no connector-management tool is advertised.

---name: customizedescription: Create a Wisp specialist or author a project-local skill using the tools Wisp actually exposes. Use when the user wants a custom Agent persona, a restricted specialist loadout, a new skill, or changes to an existing project-local skill.--- # Customize Wisp Wisp exposes customization through explicit tools and Settings UI. Python has no control-plane SDK. Never invent profile, connector, or skill CRUD methods. ## Create a specialist Use `save_specialist` only when it is advertised in the current session. 1. Ask what single job the specialist owns and what it must not do. 2. Draft a display name, one-line description, and concise instructions that extend Wisp's base prompt. 3. Decide whether to inherit project skills/connectors or use explicit whitelists. Use exact installed skill names returned by `search_skills`. Include connector names only when the user supplied or confirmed them. 4. Show the complete proposal and obtain confirmation before creating or updating it. 5. To edit an existing specialist, call `configure` with `action=get` and key `specialists`, then `save_specialist` with that `id`. Omit `id` to create. Builtin instruction text cannot be replaced. 6. Call `save_specialist` with `name` and `instructions`; add `description`, `model_id`, `skills`, or `connectors` only when intentionally chosen. 7. Report the returned specialist id. Deletion, icons, and color still live under **Settings → Specialists**. Omit `skills` and `connectors` to inherit project settings. An empty list is an explicit zero-access whitelist and is not equivalent to omission. ## Author or update a skill Load `skill-creator`. For a project-local skill, edit files under: ```text .wisp/skills/<skill-name>/SKILL.md ``` Use `read`, `write`, and `edit`. `search_skills` and `use_skill` are discovery and loading tools, not mutation tools. If a newly created project skill is not visible immediately, refresh or reopen the project so Wisp rebuilds its skill index. For a user-wide skill, create the folder in the project first, validate it, then ask the user to install that folder through **Settings → Skills**. Wisp copies installed skills to its user skill directory; there is no Agent-side publish or delete interface. ## Custom appearance For a user stylesheet (hide the lead bar, restyle chat, override tokens), load `custom-theme`. Write CSS that uses documented tokens, then apply it with `configure` `set custom_css` or ask the user to import the file under **Settings → Appearance**. ## Boundaries - Do not modify Wisp's SQLite store directly. - Do not use `python`, `shell`, or `run_in_context` to bypass Settings or tool authorization. - Do not promise conversation identity switching; the user selects specialists through Wisp's UI. - Do not claim connector enumeration when no connector-management tool is advertised.

Frequently asked questions