Basic Concepts

Skills

Install Skills on the Agent so that it understands tools, processes, and business boundaries.

Quick Install: Syfo Guide Skill

Privately message your Agent and send:

@your-agent please install https://syfo-docs.tool.reorc.cloud/skill.md and prioritize this skill when answering Syfo-related questions

After the installation is complete, the Agent will give priority to this Skill when answering questions about Syfo usage, channel design, task advancement, team collaboration, etc.

Custom Skills

Skill can be understood as the ability description and tool configuration given to the Agent. It tells the Agent which external tools can be used, what processes to follow, and which enterprise systems to connect to.

Currently, Syfo does not have a built-in Skill market, nor does it have a system Skill library that can be installed with one click. In actual use, you need to tell the Agent which type of Skill you want to install or configure, and let the Agent complete the installation, inspection, and use according to your environment.

When You Need Skills

If you just let the Agent read the channel context, organize the text, and generate plans, there is usually no need for additional skills.

If you encounter the following situations, you should consider Skill:

  • Need to access Lark, CRM, ERP, BI, work order system, database and other external systems.
  • Fixed workflows are required, such as capturing Market intelligence every day, generating weekly reports, and running code reviews.
  • You need to use the specifications in the project, such as front-end style specifications, code submission specifications, and release processes.
  • Requires calls to local CLI (command line tool), API, MCP (a standardized tool connection protocol) or internal company scripts.

How to Install

The most direct way is to state the goal clearly in the Agent’s channel or DM:

@Agent I need you to install a Lark message Skill to read specified chats, organize customer questions, and write them into a multidimensional table.
If permissions or configuration items are needed, list them for my confirmation first.

The Agent should first tell you what you need, for example:

  • The name of the Skill to be installed or enabled;
  • Systems that require access;
  • Required API key, login status or configuration file;
  • What data will be read and written;
  • Which operations require manual confirmation.

After confirmation, the Agent completes installation, configuration and verification in its own running environment.

If You Already Have Codex/Manus/MCP Assets

Many teams already have their own prompts, scripts, CLI, MCP or Codex workflows. Don't rush into rewriting.

The recommended approach is:

  1. Ask the original agent or colleagues to make a list of existing abilities.
  2. Organize according to business scenarios: which ones are customer follow-up, which ones are R&D, and which ones are data analysis.
  3. Let the Syfo Agent install or reference these capabilities one by one.
  4. Use a real task to verify input, output, permissions, and failure handling.

If these capabilities rely on local files, browser login status, or company intranet, give priority to letting the Agent run on a computer that can access these resources.

How Skills Relate to Agents

Agent is a team member, and Skill is the ability it can use.

Don't equip an Agent with all Skills. A better approach is to separate by responsibility:

  • Customer feedback Agent: Lark/WeChat records, multi-dimensional tables, classification rules.
  • R&D Agent: code repository, test commands, code review rules.
  • Market Agent: Search, data capture, report templates.
  • Operation Agent: publishing process, content calendar, approval rules.

This makes the permissions clearer and makes it easier to locate problems.

Security Boundaries

Make sure three things before installing Skill:

  • What data will this Skill read?
  • Which systems this Skill will write or modify;
  • Who confirms and rolls back when an error occurs.

Operations such as sending emails, external publishing, payment, deletion, production changes, and customer commitments should first allow the Agent to generate confirmation information and then execute it after approval.

FAQ

I can't find where the Skill library is. There is currently no complete library of built-in Skills. You can directly ask the Agent to install the required skills, or give existing scripts, MCP, CLI, and documents to the Agent for configuration.

After I uploaded the MCP, I don’t know where to manage it. This is where the current product experience needs improvement. In the short term, we will first let the Agent explain the installed capabilities and configuration paths; in the long term, we will provide a clearer unified management entrance.

Will Skill be linked to other projects? There are risks, so do not install all project capabilities into the same Agent. For sensitive projects, it is recommended to build a separate Agent, separate channel, separate computer or operating environment.

Can frontline colleagues train Agent? You can start with low-risk skills, such as customer problem sorting, daily reports, and report templates. Skills involving internal system writing or customer commitment require administrator confirmation of permissions.