Skill
The Skill page lets you find, install, and manage reusable task methods and workflows, and provide suitable Skills to Agents.
Applies to: users who reuse or maintain task methods.
Entry: Capability Center → Skill.
Search keywords: Skill, Skills, Skill marketplace, workflows, import, versions, sharing.
Find and select a Skill
A Skill describes "when to do it, how to do it, and to what standard" for a type of task, and is suited to reusing analysis workflows, operating methods, and output standards. Read its purpose and prerequisites first, and then decide whether it fits the current task.
Skills provide methods, an Agent carries out tasks, MCP provides tool connections, and a knowledge base provides searchable materials. To maintain the background and conventions of a space over the long term, use Space Memory.
- AE System Skills: Methods preset by the platform. You can't edit or delete them directly. To adjust one, copy it as a personal version.
- Company Skills: Methods shared within the company, maintained by admins with company resource management permissions.
- Personal Skills: Methods that you create, copy, or receive by accepting a share, maintained by you.
Search for Skills on the list page and filter them by source and category, or sort them by likes, calls, downloads, or newest. Click a card to open the details and view the description, Skill Content, and attached files. You can like Skills to help your team discover high-quality content.
If you're new, browse the system Skills first, and then choose company or personal Skills as your tasks require. To browse all capability types, go to the Capability Center. For specific usage, continue reading below.
Use Skills in Agents, workspaces, and conversations
Enabling a Skill, configuring a Skill for an Agent, adding it to a space's public capabilities, and using it in a conversation each serve a different purpose. Creating or downloading a Skill doesn't complete these settings automatically.
Enable available methods. Check the toggle on the Skill page. For system and company Skills, the toggle only adjusts the current user's usage preference and doesn't disable the Skill for other members. For personal Skills, the toggle manages your own version.
Let an Agent reuse a method. Associate the Skill in the Agent's capability configuration. A configured Skill is a required capability of that Agent, not a temporary choice that can be removed freely in a conversation. For how to create and configure Agents, see Agent.
Provide public capabilities for a workspace. A member with permission to set space capabilities selects the Skills. Personal Skills can't be added to the public capabilities of a shared space; select system or company Skills instead. For space roles, capability scope, and operations, see Create a space. Space management permissions are not the same as edit permissions for company Skills.
Use in a specific conversation. Go to the target space and conversation, and first confirm the current Agent and the available Skills. In a regular conversation, you can adjust the automatic usage preference for Skills, or select Skills for the current message. When you use a configured Agent, you can add available Skills but can't remove the Agent's required ones. Before sending, check the capability selection for the current message. For details, see Conversations.
A Skill being available doesn't mean that every conversation runs all of its steps, and it doesn't automatically grant permissions for data, tools, or external services. If the method depends on tools or business materials, you still need to configure the corresponding MCP and knowledge base and complete the necessary authorization.
Create or import a Skill
Go to the Skill page and click the create entry. Regular members can create personal Skills. Admins with company resource management permissions, including Agent Admin and System Admin, can create company Skills.
- Select the personal or company scope. The personal scope suits validating a method first, and the company scope suits maintaining methods for team reuse.
- Select the content source. You can edit directly, or upload a single
.mdfile or a.zip/.skillpackage that includes attached files. - Check the name, description, and version. The name uses lowercase English letters and digits separated by single hyphens, with a maximum of 48 characters, for example
weekly-analysis. You can put a Chinese name in the display name. The description should explain the applicable scenarios, and the body should include the prerequisites, steps, and expected results. The version usesmajor.minor, for example1.0. - Check the preview and create. After importing, check the body, version, and file list, resolve any name conflicts or format prompts, and then submit. After the Skill is created, check its enabled status and configure it for Agents, spaces, or conversations as needed.
File organization. A single Markdown file suits methods that only have instruction text. When you need supporting materials, use a .zip or .skill package in ZIP format: put SKILL.md in the root directory, optionally with references/ (reference notes), assets/ (templates and materials), and scripts/ (scripts). You can also wrap everything in a single top-level folder, but avoid nesting further levels of directories.
The package can't exceed 5 MB, SKILL.md can't exceed 1 MiB, and the body can't be empty. The version in the imported file is used to prefill the version. If you're told that the version format is invalid, fix it before submitting. You can't use v1.0, 1.0.0, or versions with leading zeros.
Uploading a script doesn't mean that the script runs automatically. Actual execution still depends on the execution environment, tools, and authorization available to the conversation. Some operations on personal Skills require an available personal sandbox.
Maintain content and versions
Edit permissions. You edit and delete your own personal Skills, company Skills are maintained by admins with company resource management permissions, and system Skills can't be edited or deleted directly. Being able to browse, use, or configure a Skill for a space doesn't mean that you have permission to modify its content.
Modify content. Update the name, description, or instruction body from the edit entry. View and maintain the references, assets, and scripts attached files in the details. If you need to customize a system or company Skill but don't have edit permission, copy it as a personal version first.
Content changes require a version bump. If you modify anything in SKILL.md other than the version number, including the name, description, and body, you need to enter a new version strictly higher than the current one when you save, for example 1.0 → 1.1. Changing only the version number without changing the content can't create an empty history version. Changes to the display name, icon, category, or attached files don't count as a body version bump.
View history and differences. The details of personal and company Skills provide Version History, where you can view the content of each version and compare its changes with the previous version. System Skills don't provide the same version history entry, and version comparison isn't a one-click rollback.
Check completeness before replacing with a file package. A new package replaces the content rather than only appending files, so old references/, assets/, and other content missing from the new package may be removed. Package all the attached files you want to keep, and enter a new version as prompted. Uploading only an .md file doesn't import the complete set of attached files.
Confirm the impact before deleting. Deleting removes the Skill together with its history and source files; it doesn't just hide the Skill from the current view. First confirm whether it's still used by Agents, spaces, or conversations. If you only want to stop using it temporarily, adjust its enabled status or the conversation preferences instead.
Share and publish to the company
Copy as a personal version. System or company Skills can be copied as personal Skills, which suits adjusting a method without modifying the shared original. After copying, check the name, body, and attached files. The copy is maintained independently and doesn't automatically follow updates to the original.
Share with colleagues. Share a Skill that you created with members of the same company. After the recipient accepts the invitation, they get an independent personal copy. Sharing isn't co-editing the same Skill.
From the share entry of a personal Skill, select members of the same company and send the invitation. The recipient handles the invitation on the sharing page of Approval & Sharing and, after accepting, checks their personal Skill list. Sharing and accepting require the corresponding personal sandbox to be available. Later changes to a copy aren't synced to others automatically.
Publish to the company. To let company members reuse your personal Skill, select Submit to Company for it, fill in the form, and submit. Check the Pending, Approved, Rejected, or Cancelled status in Approval & Sharing. Approvers can view the submitted content and approve or reject it, and applicants can cancel requests that are still waiting.
After approval, the company copy still needs to be published, which is complete when a usable result appears in the company Skill list. The original personal Skill doesn't become a company Skill directly, and further changes to the personal version don't automatically update the published company version. If the request shows as approved but there's still no usable result in the company list, refresh to confirm, and then contact an admin to check the publishing status instead of submitting repeatedly.
After a company Skill is published, you still need to configure it for an Agent or for workspace public capabilities according to its actual use. It doesn't automatically replace the configuration of every conversation.
Download, external installation, and FAQ
Download file. Download from a Skill card or the details. ZIP is downloaded by default, and you can also choose the .zip or .skill format. What you get is a file package. It doesn't mean that the Skill is installed in an external client, and it isn't automatically configured for Agents or workspaces on the platform.
Install in an external client. If the details provide an Add to client entry, follow the guide to complete installation. Before manual installation, confirm that the target client supports Skills and the corresponding file structure. Dependent tools, execution environments, and authorization still need to be prepared in the target environment. A successful download alone doesn't mean that the method can run.
- Can't find a Skill in the list: Clear the search and filters, and check the system, company, and personal sources and your current identity. Public capabilities of shared spaces don't accept personal Skills. To share a Skill for reuse, publish it to the company first.
- Enabled, but not used in the conversation: Check the current space, the Agent's configuration, the conversation's automatic usage preference, and the selection for the current message, and then confirm that the task matches the description and that the dependencies are available. Don't treat "downloaded" as Configured. For details, see Conversations.
- Upload failed or content missing: Check the format, the package size,
SKILL.mdin the root directory, a non-empty body, and whether the attached files are packaged. Fix the name and version as the preview prompts. - Version conflict when saving: Refresh and view the current content, version, and others' changes, merge the content you need to keep, and enter a higher version. Don't repeatedly overwrite with an old version.
- No edit, share, or company creation entry: First confirm the resource source, owner, company resource management permissions, and sandbox status. System Skills are read-only, and company management permissions are separate from space management permissions.