Customize
Open-source, local-first desktop AI research workbench for scientific computing with Python/R, MCP bioinformatics tools, SSH/WSL/GPU runtimes, and OpenAI/Anthropic models.
npx -y skills add xuzhougeng/wisp-science --skill customizeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.5 KB, as published. Nobody here has run it
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. It is
create-only.
- 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 it.
- Call
save_specialistwithnameandinstructions; adddescription,model_id,skills, orconnectorsonly when intentionally chosen. - Report the returned specialist id. Direct the user to Settings → Specialists for edits, deletion, icons, or later loadout changes; no Agent tool performs those mutations.
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.
Boundaries
- Do not modify Wisp's SQLite store directly.
- Do not use
python,shell, orrun_in_contextto 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.