JiuwenSwarm is an intelligent AI Agent built on openJiuwen. It extends the powerful capabilities of large language models directly to your fingertips through various communication apps you use daily.
Skills
Concepts
What is a skill?
Definition:
A Skill is a module that extends JiuwenSwarm with specific capabilities. You can think of it as an installable, manageable, reusable capability package.
Like apps on a phone extend device capabilities, skills extend the agent’s capability boundaries.

Skill directory and SKILL.md (typical layout)
Each skill is usually a folder that contains at least SKILL.md (definition: purpose, steps, constraints); optionally references/ (reference docs), scripts/ (helpers), and more. This section stays conceptual—see How to customize skills for folder layout and YAML frontmatter details.
Why skills are needed:
| Scenario | Without skills | With skills |
|---|---|---|
| Create a GitCode PR | You manually call multiple APIs, manage branches, and write commit messages | One sentence like “open a PR” can trigger a full automated flow |
| Build a PPT | You manually guide content, structure, and export step-by-step | After loading a PPT skill, generate a full deck directly |
| Handle PR review comments | You manually read comments, edit code, and reply one by one | The skill can fetch comments, patch changes, and reply on the platform |
How skills relate to agent and chat:
┌───────────────────────────────────────────────────────┐
│ Agent │
│ │
│ Base capabilities: chat, file ops, web search, code │
│ │
│ ┌───────────────────────────────────────────────┐ │
│ │ Skills layer │ │
│ │ │ │
│ │ ┌───────────┐ ┌───────────┐ ┌─────────────┐ │ │
│ │ │ gitcode-pr│ │pptx-craft ││gitcode-pr-fix│ │ │
│ │ │ Git ops │ │ PPT build │ │PR review fix│ │ │
│ │ └───────────┘ └───────────┘ └─────────────┘ │ │
│ │ │ │
│ │ Installable / removable / extendable │ │
│ └───────────────────────────────────────────────┘ │
│ │
└───────────────────────────────────────────────────────┘
User request → agent identifies need → load matched skill → execute workflow → return result
Skill sources:
JiuwenSwarm supports multiple sources:
| Source | Description | Characteristics |
|---|---|---|
| Built-in skills | Core skills shipped with the product; installed under Skill Marketplace → Built-in | Matches the product release |
| SkillNet | A general AI skill management and connection platform (open-source skill registry) | Anonymous usage allowed; configuring a GitHub token improves API quota and stability |
| ClawHub | Skill “app store” in the JiuwenSwarm ecosystem (enterprise skill registry) | Requires a CLI token; https://clawhub.ai/skills |
| SwarmSkills | Team/cluster skill registry, searched under Skill Marketplace → SwarmSkills online search | No extra configuration needed |
| Local import | User-authored skill files | Fully customizable; ideal for development/debug |
Security notice: Skills may involve file modification, command execution, or external service calls. Always check source and description first; prefer trusted sources.
Operation Guide
Skill installation
Whether skills come from built-in packages, SkillNet, ClawHub, or a local folder, installation and activation are done in the web UI under Skills. The Skills page has four top tabs: My Skills, Skill Marketplace, Skill Graph, and Skill Index. Online installation happens in Skill Marketplace, while installed skills are managed under My Skills. The sections below list prerequisites and paths by source.
Built-in skills
Built-in skills are skill resources packaged with JiuwenSwarm.
Install
Left sidebar → Skills → Skill Marketplace → Built-in, find the target skill and click Install.

Install from SkillNet
SkillNet is based on GitHub-hosted skill repositories.
Prerequisites:
- GitHub token is recommended to improve API quota and stability.
- Token path: GitHub → Settings → Developer settings → Personal access tokens → Generate new token.
Steps:
(Optional) Configure GitHub token
Open left sidebar → Configuration → Other → Third-party service configuration, then fill in
github_token(optional; improves GitHub API quota and stability).
Or set it in
~/.jiuwenswarm/config/.env:GITHUB_TOKEN=ghp_your_token_here(The Configuration page writes to this same
.env; the token is read from theGITHUB_TOKENenvironment variable.)Install
Install from the web UI:
Left sidebar → Skills → Skill Marketplace → Skills online search, click Source management in the top-right, choose SkillNet, then type a keyword in the search box and click Install to the right of the target skill.
Confirm success
After installation, confirm the new skill appears in Skills → My Skills.
Install from ClawHub
ClawHub URL: https://clawhub.ai/skills
Prerequisites:
- First-time use requires ClawHub token configuration.
- Create the token from your account settings on ClawHub.
Steps:
Get ClawHub token
Visit https://clawhub.ai/skills, sign in, open Settings in the top-right corner, and create a token.
Configure token in the web UI and complete installation
Left sidebar → Skills → Source management in the top-right → choose ClawHub.
On first use, fill in the CLI token obtained from the ClawHub platform and save it:
Once configured, go to Skill Marketplace → Skills online search, search for the target skill, and click Install:

Import local skills
Best for:
- self-developed skills under debugging
- skill bundles shared by others
- customizations of existing skills
Steps:
Prepare skill files
Make sure folder includes
SKILL.md:my-skill/ ├── SKILL.md # required ├── references/ # optional └── scripts/ # optionalLocal import (web UI)
Left sidebar → Skills → Import local skill in the top-right, enter the server-side local skill path (a
SKILL.mdfile or a skill directory) in the dialog, then confirm.
Manual copy (optional)
Copy skill folder into:
C:\Users\<username>\.jiuwenswarm\service_default\agent_default\agent\jiuwenclaw_workspace\skills\Verify
After installation, confirm the new skill appears in Skills → My Skills.
Skill management page
The Skills management page is the main place to manage and browse all skills. Open it from Skills in the left sidebar. The page has four top tabs, with Source management, Refresh, and Import local skill in the top-right.
| Tab | Function |
|---|---|
| My Skills | Browse and search installed skills, filter by "All / Enabled / Disabled", toggle skills on/off, and open details |
| Skill Marketplace | Install new skills; contains three sub-pages: Built-in, SwarmSkills online search, and Skills online search (SkillNet / ClawHub) |
| Skill Graph | Visualize capability relationships among installed skills; see Symphony |
| Skill Index | Build a local skill retrieval index and find matching skills by task need; see Symphony |

What the page shows
In the My Skills list, each entry shows:
| Field | Description |
|---|---|
| Skill name | Unique id, e.g. gitcode-pr, weather |
| Description | Short description of what the skill does |
| Source | Where the skill came from, e.g. local, built-in, skillnet, clawhub |
| Status | Current state, e.g. installed / not installed |
| Enable toggle | Controls whether the skill can be loaded in chat |
View skill experience
In the list, use View skill experience to browse evolution entries for that skill, one record at a time.
Each entry typically includes:
- Type: the content category, such as usage instructions, examples, or troubleshooting
- Improvement target: the Skill area the experience improves, such as the description, body, or scripts
- Created at: when the experience record was generated
- Experience content: the concrete improvement guidance
How to see data: When a skill already has saved evolution experience, View skill experience becomes available in the skill list. If there is no data yet, that skill has no saved evolution records. Records can be generated manually with
/evolve <skill_name> [user_query], or automatically in failure/correction scenarios after enabling Auto-detect evolution signals under Self-Evolution Configuration. See Configuration and Skill self-evolution.
Why it helps: Skill experience reflects self-evolution and improvements from real use, so you can judge ongoing usefulness and maintainers get actionable input.
Skill graph and skill index
The Skill Graph and Skill Index tabs are part of Symphony. The skill index helps the agent find candidate skills from a large installed-skill set, while the skill graph uses can_feed relationships to show whether skills can connect. For multi-skill orchestration, graph building, graph reading, and chat usage, see Symphony: Skill Orchestration and Dispatch.
Source management
Source management selects the online skill source used by Skill Marketplace → Skills online search and completes the related credential configuration.
Path: left sidebar → Skills → Source management in the top-right.
| Action | Description |
|---|---|
| Choose SkillNet | Skills online search retrieves from SkillNet (open-source skill registry); the dialog includes network and GitHub API rate-limit tips—if it fails frequently, go to the configuration page and fill in github_token |
| Choose ClawHub | Skills online search retrieves from ClawHub (enterprise skill registry); on first use, fill in and save the CLI token in the dialog |

Tip: Built-in skills (Skill Marketplace → Built-in) and SwarmSkills online search do not depend on source management and can be used directly. Switching the source does not affect already installed skills.
Post-install management
After installing skills, you can inspect, verify, and uninstall.
View installed skills
Method 1: Web UI
Left sidebar → Skills → My Skills to browse installed skills, where you can filter by "All / Enabled / Disabled" or search by name, description, and tags (same layout as the “skill list and search” screenshot above; no duplicate figure here).
Method 2: Chat
List my installed skills.
The agent lists installed skill names, sources, versions, and related info.
Method 3: File path
C:\Users\<username>\.jiuwenswarm\service_default\agent_default\agent\jiuwenclaw_workspace\skills\
Each subfolder is one skill.
View skill details
There are two common ways: in chat or open the detail page from the Skills UI.
Method 1: In chat
Ask the agent to show a skill’s details, for example:
Show details for gitcode-pr skill.
The agent summarizes key fields in the conversation (similar to the screenshot below).

Method 2: From the web UI
Path: left sidebar → Skills → My Skills → click the target skill to open its detail page.

Details include:
- Source / version / author: where the skill came from (local / built-in / skillnet / clawhub, etc.) and version info
- Description: what the skill does
- Enable toggle and uninstall button: in the top-right of the detail page
- Allowed tools: the tools the skill may call (shows "Unrestricted" when not declared)
- Content preview: the full
SKILL.mddefinition
Uninstall skill
The uninstall entry is on the skill detail page:
- In the My Skills list, click the target skill to open its detail page.
- Click the Uninstall button in the top-right of the detail page and confirm.

After uninstall:
- Skill files are removed from the
skillsdirectory - Chat no longer auto-loads the skill
- Past execution results are unaffected
Verify whether a skill is active
Checks:
- Confirm skill appears in installed list.
- Try prompt likely to trigger it.
- Check
logsfor load records.
Common states:
| State | Meaning | Suggestion |
|---|---|---|
| Installed and active | Works normally | No action |
| Installed but not loaded | Runtime may need restart | Restart and retry |
| Install failed | Token/network/source issue | Check error and config |
| Outdated version | Features may be limited | Update to latest |
Usage Guide
How to use skills in chat
Installed skills can be triggered automatically or manually.
Auto trigger
Agent detects intent and loads matching skill.
Example:
User: Help me open a PR on GitCode.
Agent: [Auto-loads gitcode-pr]
Sure, I will create the PR...
Explicit trigger
User names the skill directly.
Example:
User: Use pptx-craft to create a product introduction PPT.
Agent: [Loads pptx-craft]
Sure, I will create the PPT...
How to write prompts that trigger skills more reliably
Recommended prompts:
| Recommended prompt | Why |
|---|---|
| "Open a GitCode PR for me" | Platform + action clearly stated |
| "Use pptx-craft for a tech sharing PPT" | Skill name + task type |
| "Do deep research on AI industry trends" | Matches deep-research patterns |
| "Handle review comments on PR #123" | PR review task maps to review-fix skill |
Not recommended:
| Prompt | Issue |
|---|---|
| "Fix that thing for me" | Too vague |
| "Make a doc" | Type not specified |
| "Submit code" | Platform not specified |
Key fields in skill details
Before using a skill, check:
| Field | Why it matters |
|---|---|
| Source | Trust evaluation |
| Description | Usage fit |
| Allowed tools | What operations it can perform |
| Version | Whether it is up to date |
Example query:
Show gitcode-pr details and SKILL.md content.
Multi-skill tasks: Skill Symphony
When a task needs several skills to work together, such as "recognize text from an image, translate it, write copy, and send an email," Skill Symphony can first produce a skill chain and then wait for confirmation before execution. For setup, prompt examples, and how to read the orchestration result, see Symphony: Skill Orchestration and Dispatch.
Practical examples
Example 1: Weather query (SkillNet)
Scenario:
The user wants a quick weather summary and short-term forecast for a city.
Skill acquisition (reproducible, from SkillNet):
- Open left sidebar → Skills → Skill Marketplace → Skills online search (choose SkillNet in Source management in the top-right).
- Search for
weatherin the search box. - Click install, then confirm
weatherappears in your My Skills list. - If search rate is limited, fill in
github_tokenunder Configuration → Other → Third-party service configuration and retry.
Prerequisites (for stable reproduction):
weatherskill is installed (using the SkillNet steps above)- Network can reach public weather services (such as wttr.in / Open-Meteo)
User input (example):
Please use the weather skill to check today's weather
and the next three days for Beijing.
Execution flow (expected):
- The agent detects and loads
weather - It requests real-time and forecast weather data
- It summarizes readable output (temperature, condition, wind/precipitation)
Expected output (example):
Beijing weather:
- Today: Cloudy, 16~28°C
- Tomorrow: Sunny, 18~30°C
- Day after tomorrow: Light rain, 19~26°C
(includes feels-like temperature and precipitation probability)
Why this case is stably reproducible:
- Fixed skill source (SkillNet)
- Simple and explicit input template (city + time range)
- No extra business account or complex local setup required
Example 2: PDF processing (SkillNet)
Scenario:
You need to process PDF files quickly (for example merge files, split pages, or extract text) and get directly usable outputs.
Skill acquisition (reproducible, from SkillNet):
- Open left sidebar → Skills → Skill Marketplace → Skills online search (choose SkillNet in Source management in the top-right).
- Search for
pdfin the search box. - Click install and confirm it appears in your My Skills list.
- If search is limited, fill in
github_tokenon the configuration page first, then install.
Prerequisites (for stable reproduction):
pdfskill is installed (using SkillNet steps above)- Prepare 2 accessible PDF files (for example
a.pdfandb.pdf)
User input (example):
Please use the pdf skill to merge `a.pdf` and `b.pdf` into `merged.pdf`,
and also provide a text summary for the first two pages.
Execution flow (expected):
- The agent detects and loads
pdf - It locates input PDF files and performs merge
- It extracts/summarizes text from specified pages
- It returns output file path and summary
Expected output (example):
Done:
1) Merged file generated: `merged.pdf`
2) Extracted text summary from pages 1-2:
- Page 1: ...
- Page 2: ...
Advanced and Troubleshooting
Common issues and precautions
Common issues
Issue 1: Installation fails
| Possible cause | Resolution |
|---|---|
| Missing/invalid token | Check github_token / ClawHub CLI token config |
| Network issue | Check connection and retry |
| Online source unreachable | Verify the runtime can reach GitHub (SkillNet) or the ClawHub service |
| Skill not found | Verify skill name |
Issue 2: Skill not visible after install
| Possible cause | Resolution |
|---|---|
| Service not restarted | Restart JiuwenSwarm |
| Wrong install path | Verify skill file path |
| Missing SKILL.md | Ensure skill folder has SKILL.md |
Issue 3: Skill visible but not triggered
| Possible cause | Resolution |
|---|---|
| Prompt mismatch | Use clearer prompts |
| Skill not enabled | Check status |
| Tool permission limits | Check permission config |
Issue 4: Output does not match expectation
| Possible cause | Resolution |
|---|---|
| Skill version outdated | Update skill |
| Input incomplete | Provide required parameters |
| Skill config mismatch | Read SKILL.md usage details |
Issue 5: Token / permission / source trust
| Issue type | Resolution |
|---|---|
| Invalid GitHub token | Regenerate token with proper permissions |
| Expired ClawHub token | Refresh token from platform |
| Untrusted source | Inspect source and details before use |
Precautions
Prefer trusted sources
- SkillNet and built-in catalogs are relatively centralized—still read descriptions before installing
- For online sources such as ClawHub, verify author and source trust
Read documentation first
- Check
SKILL.mdbefore running a skill - Confirm scenario fit
- Check
Token handling for external services
- GitCode-related skills require
GITCODE_TOKEN - Other skills may require platform-specific tokens
- GitCode-related skills require
Check operation scope for file/command skills
- Review allowed tools
- Confirm no sensitive files are unintentionally affected
How to customize skills
As an advanced topic, you can create or modify skills.
Build a new skill
Basic folder layout:
my-custom-skill/
├── SKILL.md # Skill definition (required)
├── references/ # Reference docs (optional)
│ └── api-reference.md
└── scripts/ # Helper scripts (optional)
└── helper.py
Core SKILL.md content:
You can let JiuwenSwarm help you generate it. YAML frontmatter between the first --- and second --- declares metadata; Markdown after the second --- is the skill body—the instructions the Agent follows. Example:
---
name: my-custom-skill
version: 1.0.0
author: your-name
description: Demo skill that shows how to write a custom Agent skill
tags: [demo, tools]
allowed_tools: [webSearch, readFile]
---
# My custom skill
When this skill is selected, follow the instructions below.
## When to use
- …
## Steps
1. …
2. …
Frontmatter field reference
| Field | Required? | Description |
|---|---|---|
name |
Strongly recommended | Unique skill id; prefer kebab-case; if omitted, some setups infer from folder name |
description |
Strongly recommended | One-line purpose; pipeline validation usually requires it; avoid < and > |
version / author |
Optional | Version and author |
tags |
Optional | YAML list or comma-separated string |
allowed_tools |
Optional | Related tool names (comma-separated string also allowed); actual invocation depends on agent tool config and permissions |
Screenshots: Loading a custom skill folder into the product matches the Import local skill screenshot under Import local skills; generic install UI matches Built-in skills.
Modify an existing skill
Modify an existing skill through JiuwenSwarm
Talk to JiuwenSwarm directly, for example: "Help me optimize the xxx skill and add xxx capability."
Example: Optimize the weather skill by adding UV index display
Before optimization
The output only includes basic items such as temperature, wind speed, precipitation probability, and clothing advice.

Through chat with JiuwenSwarm: "Optimize the weather skill and add UV intensity display", the skill is updated

After optimization
When you call it again, the output includes not only temperature and wind speed, but also UV intensity.
