> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwenwork.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Skills Management

> Manage organization skills from the Admin Console.

<style
  dangerouslySetInnerHTML={{ __html: `
/* qwenwork-navigation-tabs-override */
#adoc-layout { --topbar-height: var(--topbar-row1-height) !important; }
#navbar[data-has-tabs="true"] > div:has(.nav-tabs) { display: none !important; }
` }}
/>

## 1. What you can do

A skill gives Qwen Work a repeatable method, knowledge set, or workflow for a specific task. Admins can:

- control whether members can browse the public skill marketplace, upload personal skills, or submit skills to the organization;
- create and maintain organization-owned skills;
- control whether an organization skill is visible to members; and
- review skills submitted by members.

Changes made by a team admin affect the entire organization, not only their own team.

## 2. Configure skill access

The top of the page contains three organization-wide settings.

### Public marketplace visibility

- On: Members can see and browse the public skill marketplace.
- Off: The public marketplace entry is hidden. Public skills that are already installed are not automatically removed.

### Allow personal skill uploads

- On: Members can upload their own skills in their personal space.
- Off: Members cannot add new personal uploads. Whether existing resources remain usable depends on their current member-side status.

### Allow members to add skills to Organization skills

- On: Members can submit skills to the organization. New submissions appear under **Skill reviews**.
- Off: Members cannot create new organization submissions. Existing review records remain available.

After changing a setting, wait for the **Settings updated** confirmation.

## 3. Create an organization skill

1. Open **Organization skills**.
2. Select **Add skill**.
3. Enter the skill information.
4. Upload an icon and skill ZIP package when needed.
5. Set the supported clients and team visibility.
6. Select **Create**.

### Field reference

| Field             | Required    | Guidance                                                                                                                   |
| ----------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------- |
| Skill name        | Yes         | Technical identifier using lowercase letters, numbers, and hyphens only; maximum 64 characters, for example `sales-report` |
| Chinese name      | No          | Name shown in the Chinese interface                                                                                        |
| Author            | No          | If empty, the current admin is recorded                                                                                    |
| Version           | No          | Use a clear version such as `1.0.0`                                                                                        |
| Description       | No          | Explain the purpose, required input, and intended scenario                                                                 |
| Icon              | No          | Image file up to 2 MB                                                                                                      |
| Supported clients | Yes         | Choose where members can discover the skill                                                                                |
| Team visibility   | No          | When on, the skill is shown in the team's marketplace                                                                      |
| Skill ZIP package | Recommended | ZIP only, up to 10 MB                                                                                                      |

The skill name cannot be changed after creation. To use a different technical identifier, create a new skill.

## 4. Prepare a skill package

The package should contain one top-level folder matching the skill name, with a `SKILL.md` file inside:

```text
sales-report/
├── SKILL.md
├── scripts/
└── references/
```

Before uploading, verify that:

- the top-level folder matches the **Skill name** exactly;
- `{skill-name}/SKILL.md` exists;
- unrelated system files such as `.DS_Store` and `__MACOSX` are removed;
- file paths do not contain unsafe segments such as `..`; and
- the ZIP file is no larger than 10 MB.

You can create a record without a package, but members will not receive complete skill content. Upload a valid package before making the skill team-visible.

## 5. Find and review skills

1. Search by skill name under **Organization skills**.
2. Review the name, description, package status, supported clients, status, team visibility, and last update time.
3. Use pagination to view more skills.

**Uploaded** means a ZIP package is available. **Not uploaded** means there is no downloadable skill package.

## 6. Edit a skill

1. Find the skill.
2. Select **Edit**.
3. Change the Chinese name, author, version, description, icon, supported clients, or team visibility.
4. To replace the package, choose a new ZIP file.
5. Select **Save changes**.

If you do not choose a new file, the existing package is retained.

## 7. Control team visibility

Use **Team visible** in the list:

- On: The skill appears in the team's marketplace.
- Off: The skill is hidden from the team's marketplace. Members who already installed it are not affected.

This setting applies to one organization skill and does not control public marketplace visibility.

## 8. Download or remove a skill

### Download a package

1. Find a skill marked **Uploaded**.
2. Select **Download**.
3. Save the ZIP file.

### Remove a skill

1. Select **Remove** for the skill.
2. Verify the skill name.
3. Confirm removal.

The Admin console does not currently provide a restore action. Download and retain the package before removal.

## 9. Review member submissions

1. Open **Skill reviews**.
2. Filter by **Pending**, **Approved**, **Rejected**, **Cancelled**, or **All**.
3. Select **Details** and review the name, description, author, version, supported clients, and package.
4. For a pending submission:
   - select **Approve** to publish it immediately to Organization skills; or
   - select **Reject**, enter a reason, and return it to the submitter.
5. Confirm that the submission status has updated.

Before approval, verify that:

- the name and purpose are clear and do not conflict with an existing skill;
- the package comes from a trusted source and contains no sensitive or unauthorized content;
- supported clients and organization visibility follow company policy; and
- the description gives members enough information to use the skill.

## 10. Troubleshooting

### Create is unavailable

Check that the skill name is not empty and contains no uppercase letters, underscores, spaces, or other unsupported characters.

### Package upload fails

Confirm that the file is a ZIP under 10 MB, then check the folder structure and `SKILL.md`.

### The skill exists but members cannot see it

Check:

- whether **Team visible** is on;
- whether supported clients include the client used by the member; and
- whether the member is in the correct organization workspace.

### Member submissions are missing

Confirm that **Allow members to add skills to Organization skills** is on and that the member completed submission. Select **All** to check whether the submission was already processed or cancelled.

---

[Previous: Credits](/enterprise/credits) · [Back to overview](/enterprise/admin-overview) · [Next: Kits](/enterprise/kits)