Source profileQuality 65/100

xuzhougeng/wisp-science/skills/customize/SKILL.md

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.

Source repository stars
560
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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

Best for

  • Use when the user wants a custom Agent persona, a restricted specialist loadout, a new skill, or changes to an existing project-local skill.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/xuzhougeng/wisp-science --skill "skills/customize"
Safe inspection promptEditorial

Inspect the Agent Skill "customize" from https://github.com/xuzhougeng/wisp-science/blob/95d2c13d1665d46a388b5bdc998dcce0d5ec2eee/skills/customize/SKILL.md at commit 95d2c13d1665d46a388b5bdc998dcce0d5ec2eee. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Create a specialist

    Use savespecialist 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 thatDecide whether to inherit project skills/connectors or use explicit
  2. 02

    Author or update a skill

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

    Load skill-creator. For a project-local skill, edit files under:Use read, write, and edit. searchskills and useskill 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 s…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…
  3. 03

    Boundaries

    Do not modify Wisp's SQLite store directly.

    Do not modify Wisp's SQLite store directly.Do not use python, shell, or runincontext to bypass Settings or toolDo not promise conversation identity switching; the user selects specialists

Permission review

Static risk signals and limitations

Writes files

medium · line 40

The documentation asks the agent to create, modify, or delete local files.

For a user-wide skill, create the folder in the project first, validate it, then

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score65/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars560SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
xuzhougeng/wisp-science
Skill path
skills/customize/SKILL.md
Commit
95d2c13d1665d46a388b5bdc998dcce0d5ec2eee
License
AGPL-3.0
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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.

  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 it.
  5. Call save_specialist with name and instructions; add description, model_id, skills, or connectors only when intentionally chosen.
  6. 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, 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.