self-awareness
Wisp-science's actual agent tool surface and runtime boundaries. Load this when deciding which Wisp tool can perform a task, checking whether Python can reach agent or desktop capabilities, choosing between interactive analysis and persisted Runs, or answering questions about delegation, images, skills, memory, artifacts, lineage, credentials, session history, and other self-introspection capabilities.
Profile →npx skills add xuzhougeng/wisp-science --skill self-awareness --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Self-awareness — Wisp's actual capabilities Use only tools advertised in the current conversation. Wisp exposes agent and desktop capabilities as explicit tools; do not assume that an SDK documented by another application also exists here. Some tools are conditional on the desktop session, project settings, execution context, or capability grants. If a tool is not advertised, treat it as unavailable. ## Python and R boundary Use `python` for persistent Python analysis and `r` for persistent R analysis. Their variables and imports persist per project and execution context. Pass a `context_id` such as `local`, `ssh:<alias>`, or `wsl:<distro>` when the work must run somewhere other than the default local context. The Python worker initializes an ordinary namespace with common standard-library modules and any available convenience packages. It does **not** inject a Wisp control-plane object. Code executed with `python` therefore cannot directly call the agent model, spawn Agents, submit or monitor Runs, inspect Wisp credentials, or query internal project/session metadata. Leave the Python cell and call the corresponding Wisp tool instead. ## Capability reference | Need | Wisp interfa
- Python and R boundary
- Capability reference
- Choosing the right execution path
What does the self-awareness skill do?
Wisp-science's actual agent tool surface and runtime boundaries. Load this when deciding which Wisp tool can perform a task, checking whether Python can reach agent or desktop capabilities, choosing between interactive analysis and persisted Runs, or answering questions about delegation, images, skills, memory, artifacts, lineage, credentials, session history, and other self-introspection capabilities.
How do I install it?
Run `npx skills add xuzhougeng/wisp-science --skill self-awareness --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From xuzhougeng/wisp-science, a repository with 895 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.