About · Install & Use
AI Soul & Skill Install Guide
This guide focuses on two things: how common AI Agents usually install Skills, and how AISoulHub AI Souls can be installed and used across different tools.
1. Understand the Package
AISoulHub usually provides a zip package, but installation differs by content type and AI Agent. A practical split is: AI Soul packages that can often be imported or copied directly, and Skill packages that fit better into Skills, project knowledge, or agent instructions.
AI Soul Package
This is closer to a full character or long-term companion setup. Common paths are uploading the zip directly, importing the extracted package, or copying the core instructions into the target tool. OpenClaw / XClaw, Claude Code, ChatGPT clients, and Hermes Agent usually support one of these paths.
Skill Package
This is closer to a capability, workflow, or persona-material package. It works best in tools with Skill support, or after being split into project knowledge, system prompts, or workflow instructions. Persona Skills and Soul-building Skills both fall into this category.
Common AI Agent Install Paths
| Agent | Typical install path | Notes |
|---|---|---|
| Claude Code | Skill marketplace / `npx skills add` / direct in-chat AI Soul install | Good for both Skills and direct AI Soul ZIP installs in chat. |
| OpenAI GPT (Codex CLI / ChatGPT clients) | `npx skills add` / upload ZIP / paste instructions / project files | Codex CLI leans toward Skills, while ChatGPT-style clients lean toward projects and conversation imports, but both live in the OpenAI GPT ecosystem. |
| OpenClaw / XClaw | In-chat install / CLI / marketplace / ZIP import / create from file | One of the best targets for direct AI Soul packages and already fits the SkillHub / ClawHub ecosystem well. |
| Hermes Agent | In-chat install / CLI install / paste `hermes-instructions.md` | Supports both Skill installation and Hermes-targeted AI Soul instruction text. |
| Cursor / Copilot / Cline / Roo / Trae | Manual copy / Rules / project knowledge | This group is better for Skills or for splitting an AI Soul into project rules rather than direct in-chat Soul installs. |
2. Use Skills
Persona Skills and Soul-building Skills are both Skills at heart: the former leans toward persona materials and expression style, while the latter is more of a workflow for improving or rewriting AI Souls. From the user's perspective, they install in nearly the same way.
Common Skill install methods
| Method | Typical agents | Notes |
|---|---|---|
| Marketplace / in-chat install | Claude Code / OpenClaw / Hermes Agent | Best for users already comfortable with Skill ecosystems; search and install directly. |
| CLI install | Codex CLI / Claude Code / OpenClaw / Hermes Agent | Examples include `npx skills add`, `clawhub install`, and `skillhub_install install_skill`. |
| Manual copy into a skills directory | Claude Code / Codex CLI / Cursor / Copilot / Cline / Roo / Trae | Good for generic Skill packages or when the target tool does not expose a marketplace. |
| Split into project knowledge / rules / system prompts | Cursor / Copilot / Cline / Roo / Trae / ChatGPT clients | If the tool does not support structured Skills, open `SKILL.md` and migrate the steps, boundaries, and output format manually. |
- Persona Skills should be treated as a capability pack with persona materials, thinking style, and boundaries, not as the real person.
- Soul-building Skills are better used to rewrite, evaluate, and improve AI Soul source files rather than as standalone chat personas.
- If the tool supports Skills, install it as a Skill first; otherwise migrate the triggers, steps, output format, and boundaries from `SKILL.md`.
3. Use AI Souls
- Confirm the viewing version on the detail page and prefer the latest reviewed version.
- Download the ZIP that matches your tool. If you only want a quick test, pick the most convenient one and start there.
- Open README or IMPORT_GUIDE, then copy the system prompt, identity, boundaries, and memory policy as instructed.
- Test the style in the detail-page trial chat or a temporary conversation before long-term use.
2.1 Send the ZIP to the Agent directly
This is the fastest path, especially for tools such as OpenClaw / XClaw, Claude, ChatGPT clients, and Hermes Agent that already understand packaged Markdown instructions. Upload the zip, then say something like “install this AI Soul and start using it.”
Send the downloaded package to OpenClaw and ask it to install the Soul into the current Agent.
Click / double-click the image to enlarge it
Hermes Agent can take the Hermes-targeted package directly, inspect the instructions, and continue initialization.
Click / double-click the image to enlarge it
Claude-style clients can read the package and begin using the character setup in the conversation.
Click / double-click the image to enlarge it
If the client supports file uploads, this is straightforward; otherwise, unzip and copy the core Markdown files.
Click / double-click the image to enlarge it
Import an AI Soul package directly through a QClaw chat flow, useful for users who prefer command-like setup in conversation.
Click / double-click the image to enlarge it
A WorkBuddy conversational installation example, from install prompt to import confirmation.
Click / double-click the image to enlarge it
2.2 Use built-in file import or text-description flows in AI Agents
Some AI Agents provide built-in import flows. For example, in QClaw with an OpenClaw core, you can go through “Create Agent → Custom creation → Create from file / import package” to import an AI Soul package directly. Other AI Agents are easier to initialize through descriptive instructions rather than package install; in that case, download the Hermes-targeted package, extract `hermes-instructions.md`, and paste it into the appropriate initialization field.
Create a new Agent, choose custom creation, and import the package downloaded from AISoulHub.
Click / double-click the image to enlarge it
In hosts that prefer descriptive initialization, you can paste the dedicated instruction file directly during setup.
Click / double-click the image to enlarge it
2.3 AI Soul usage examples
These are not installation steps, but real usage examples after import. They help show what an AI Soul usually looks like once it is successfully installed in different agents.
A real OpenClaw-side experience.
Click / double-click the image to enlarge it
A Hermes-side usage example, closer to terminal-style long-running interaction.
Click / double-click the image to enlarge it
A real usage example inside Claude.
Click / double-click the image to enlarge it
In client-style tools, the Soul is often kept as a project, a conversation, or a custom assistant.
Click / double-click the image to enlarge it
A QClaw usage example showing how the imported AI Soul carries its persona and task style into real conversation.
Click / double-click the image to enlarge it
A WorkBuddy usage example showing the AI Soul acting as a long-running assistant after installation.
Click / double-click the image to enlarge it
4. Troubleshooting
- Not sure which file to read first? Start with README.md, then IMPORT_GUIDE.md.
- If the style feels off, check whether identity, boundaries, examples, and use cases were copied together.
- If your tool cannot upload zip files, unzip the package and copy the core markdown files.
- If instructions conflict after import, keep the package boundaries, safety constraints, and use cases first, then adapt filenames to your tool format.
- If you find a content issue, report it on the detail page or send feedback.
5. Official References
Import paths can change as each tool evolves. AISoulHub packages keep universal Markdown source files and add target-specific notes; if details differ, follow the target tool's official documentation.