菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/xuzhougeng/wisp-science --skill customize命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Organize multi-step scientific analyses into reproducible, self-contained modules. Use for workflows such as QC→PCA→DEG→GSEA that produce scripts, inputs, figures, tables, and methods. Creates a stable module layout, records exact inputs/parameters/package and database versions in each module README, keeps large data as references instead of copies, and verifies outputs before completion.
Use this skill to drive Wisp Browser Runtime sessions (shared daily Chrome or workspace Chrome) — open pages, read them, click, fill and submit forms, navigate, switch tabs, or scrape content that needs the user's existing cookies and login state. Triggers when the user asks to do something in their browser, log into a site and act inside it, fill out a web form, click through a flow, or extract data from a page that requires being signed in. Tools: browser_setup (check/connect the extension), web_open_tab (open a URL), web_scan (read visible content + actionable elements with ready-made selectors), web_execute_js (click/type/navigate, or a JSON command for tabs/CDP), web_screenshot (see what the tab is showing — layout, charts, canvas, QR codes). Not for the built-in read-only web fetch — this is for interacting with a live browser.
Set up and validate a reproducible Python or R environment on a Wisp execution context. Use for a selected local, WSL, or direct SSH context when installing scientific packages, configuring caches, recording interpreter activation, or producing an environment smoke test. Do not use for scheduler clusters or managed cloud providers that Wisp cannot track yet.
| name | customize |
| description | 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. |
Wisp exposes customization through explicit tools and Settings UI. Python has no control-plane SDK. Never invent profile, connector, or skill CRUD methods.
Use save_specialist only when it is advertised in the current session.
search_skills.
Include connector names only when the user supplied or confirmed them.configure with action=get and
key specialists, then save_specialist with that id. Omit id to
create. Builtin instruction text cannot be replaced.save_specialist with name and instructions; add description,
model_id, skills, or connectors only when intentionally chosen.Omit skills and connectors to inherit project settings. An empty list is an
explicit zero-access whitelist and is not equivalent to omission.
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.
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.
python, shell, or run_in_context to bypass Settings or tool
authorization.