Skip to main content

xAgent Skill Management: Create, Test, Publish, and Update

Who This Is For​

This page is for users and administrators who want xAgent to handle recurring work reliably.

What It Is​

A Skill is a reusable work method. It records fixed steps, output requirements, important notes, and quality standards so xAgent does not need to understand the same type of task from scratch each time.

Ordinary users can directly use public Skills prepared by administrators. When permissions allow, they can also create or import personal Skills. Most users do not need to configure a Skill from scratch and can use existing Skills directly, then fine-tune personal Skills after becoming familiar with them. Administrators review stable personal Skills and turn them into public capabilities.

xAgent Skill Management page showing personal and public Skill lists and actions

Visibility Scope​

xAgent currently does not apply complex access restrictions to Skills. Public Skills are visible to all users and are suitable for general, stable work methods that team members can share.

If a Skill has special requirements, applies only to one user, contains personal work habits, targets a specific customer workflow, or should not be visible to other users, install or save it separately in the personal Skill library. A personal Skill is visible only within the current user's scope.

Skill status and scope can be understood as follows:

TypeVisible toAvailable Actions
Draft SkillCurrent userEdit and test, then publish to the personal library after confirmation
Personal SkillCurrent userUse, edit, export, and delete; submit for public library review after it becomes stable
Public SkillAll usersView, reference, and use; ordinary users usually have read-only access, while administrators review and maintain it

Do not put personal habits, temporary paths, private accounts, customer-specific details, or non-public internal processes in public Skills. Keep Skills with special requirements in the personal Skill library.

When to Use It​

Use a Skill when:

  • A task repeats frequently.
  • Each run follows fixed steps and a fixed format.
  • Output quality must remain stable.
  • Multiple Tools must be combined to complete the work.
  • Personal experience should be captured for team reuse.

Common Skills include research organization, report generation, meeting notes, contract review, data analysis, customer support replies, investment research, and document understanding.

To inspect built-in Skills for real task scenarios or suggest improvements, read Built-in Skill Files. The documentation project includes a copy under skills/; submit related suggestions through Share an Idea.

Reading the Page​

Skill Management displays Skill cards. Common information includes:

InformationMeaning
Skill nameDisplay name or identifier of the Skill
DescriptionThe type of task the Skill handles
Editable / read-onlyWhether the current user can modify it
DetailsSkill guidance, usage, and configuration
Download / send / deleteManagement actions for editable Skills

Ordinary users should focus on the name, description, and details. Do not choose a Skill by name alone; confirm that it fits the current task.

Basic Usage​

Use an Existing Skill​

  1. Open Skill Management.
  2. Search for task keywords such as "contract," "report," or "customer support."
  3. Open the Skill details and confirm that its purpose matches the task.
  4. Return to an Agent Session, submit the task, and describe the goal and materials.
  5. To request a specific Skill, say directly that xAgent should follow that Skill's method.

Example:

Use a meeting-notes method to organize the transcript I uploaded. Output decisions, action items, owners, and due dates.

Create or Update a Personal Skill​

This is suitable for users who already understand a fixed workflow and want to fine-tune a personal capability. Before creating or updating a Skill, prepare:

  • The type of task the Skill solves.
  • The materials users must provide.
  • The processing steps.
  • The output format.
  • Situations requiring human confirmation.
  • Content that must not be written into the Skill.

Do not put temporary file paths, account passwords, tokens, verification codes, or one-time customer information in a Skill.

In addition to creating or importing a Skill in Skill Management, you can describe the desired Skill in the main Agent Session. xAgent automatically creates a Skill-building Session, learns the requirements, generates a draft, and publishes it after your confirmation. You can also create a dedicated Skill-building Session directly through an Agent.

To update an existing Skill, identify it in a Skill-update sub-session. xAgent automatically copies the Skill into the Session directory and uses the copy as a draft, modifies it according to your requirements, and publishes the update only after confirmation.

Publish to the Personal Library​

When creating or editing a Skill, the system first generates a draft. A draft is suitable for testing and adjustment and should not be treated as a team-standard capability immediately.

After confirming the draft is usable, select Publish to Personal Library in Skill Management. The Skill then becomes the current user's published personal Skill. Later Agent Sessions can reference it, and the current user can continue editing, exporting, or deleting it.

Submit for Public Library Review​

After a personal Skill has been tested with real tasks and confirmed stable, submit it for public library review. At submission time, the system copies a snapshot of the current published personal Skill for administrator review. Later edits to the personal Skill do not affect the submitted review snapshot.

The recommended flow is:

  1. Create or import a Skill as a draft.
  2. Test it in your own tasks and add examples, boundaries, and quality standards.
  3. Publish it to the personal library and use it as a personal Skill.
  4. After using it for a period of time, submit it for public library review if it is suitable for multiple users.
  5. After administrator approval, it enters the public library and becomes visible to all users.

Administrators should check whether its purpose is general, its description is clear, it contains sensitive information, it depends on a private account or specific external system, and it is suitable for every user to see.

Make a Skill More Effective​

A good Skill usually includes:

ElementDescription
Clear purposeExplain in one sentence which task it handles
Input requirementsState which materials the user must provide
Operating stepsExplain the process in order
Output standardDefine the result format, fields, and quality requirements
Risk guidanceState when to request confirmation or stop
ExampleGive ordinary users a task prompt they can reuse

If a Skill becomes increasingly complex, split it into smaller Skills instead of putting every scenario into one Skill.

Common Scenarios​

Recurring Report​

Use the data visualization report generator method to create this week's business analysis report from sales.csv.

Customer Support Reply​

Follow the customer support workflow to draft a reply based on the customer's question. Do not send it yet.

Contract Review​

Follow the contract review method to read this contract, focusing on payment, delivery, breach, and dispute resolution clauses.

Generate a New Skill Draft​

Turn the fixed work method below into a maintainable Skill draft.

Management Guidance​

  • Public Skills should serve multiple users and avoid personal habits.
  • Write Skill descriptions for users, not only with internal terminology.
  • Common Skills should include clear example tasks.
  • Steps involving external sending, deletion, or account authorization must require confirmation first.
  • Mark expired or unstable Skills clearly so ordinary users do not use them by mistake.
  • Complete sufficient testing in a personal Skill before submitting it to the public library.
  • Do not promise team-wide stable availability before public library approval is complete.

Next Steps​

Last updated on