ZCode AI Agent Team

⬅️ Coming from Step 3

Step 3 · Plans and Models prepared your everyday model → this guide installs specialist agents so different models can work as a team.

⚡ In a hurry? The quickstart version of this guide lives in the one-page quickstart.

🌟 Goal: install a team of AI agents that work by professional role, so "production, review, and verification" are handled by separate roles. Role specialization works better when you have several models with different capabilities. Allow about 5–10 minutes.

About this pack

The agent team is an independent toolkit shared free and open-source (MIT) by its author — not a built-in feature of the Laifaxin product. The pack itself has no fee; any cost comes from the model services or plans you use. It is sharing only — no teaching, no Q&A — how far you get depends on your model setup and hands-on practice. For installation and usage issues, use the "Troubleshooting" section below, or ask your AI to read the repository and generate troubleshooting suggestions (a self-service path, not a guarantee of resolution).

What It Is

A basic workflow asks one model to do everything from start to finish. An AI agent team assigns production, review, execution checks, and final acceptance to separate specialist roles.

It becomes more professional through defined roles and acceptance criteria, and more intelligent through task routing and model matching—not because installation changes the underlying models.

Why Multiple Models

Different models are strong at different kinds of work. Matching models to roles is more effective than forcing one model to handle every task.

Model strength	Best suited to	Example roles
Strong reasoning	Architecture, difficult problems, complex planning	coder-gpt, seoer
Fast and economical	Routine checks and frequent lightweight work	verifier, tijian, shencha-final
Image understanding	Screenshots, pages, and visual review	shencha-ui, frontend
Long context	Large repositories, long briefs, distributed evidence	coder-kimi
Strong writing	SEO, outreach, and social content	writer-pro, outreach, sheyun

The GitHub repository also compares the practical results of single-model and multi-model setups. Beginners do not need many providers on day one: two or three models with different strengths are enough to improve the separation of production, review, and visual work (this is an optional upgrade, not a prerequisite for installing the team). For each provider's Base URL and API format, see the provider cheat sheet in Step 3.

Recommended setup

The team still works with one model. If you completed Step 3 with two or three models from different capability groups or providers, you can better separate production from review while covering reasoning, speed, and image input.

What You Get

The package is currently named Foreign Trade AI Team and includes 22 roles. Releases update continuously and roles will be added over time, so treat the repository's current README as the source of truth.

Group	Roles	Main work
🛠️ Engineering	coder, coder-gpt, coder-ds, coder-kimi, frontend	Differentiated routing across four coders, isolated parallel worktrees; front-end implementation and prototype modes plus UI microcopy
✍️ Content	writer, writer-pro	A-E content modes, success definitions, and controlled double-draft blind testing
📊 Audience insight	dongcha	Discover audiences, pain points, and topic seeds from a product; proposes only
📊 Diagrams	mermaid	Turn business logic into business flowcharts (single code block, sanitized, set reconciliation)
📱 Social	sheyun	S1 single posts, S2 batches, S3 weekly operations, S4 pure strategy
📣 WeChat official accounts	gonghao	G1 single posts, G2 series, G3 weekly operations, G4 pure strategy; Chinese long-form plus platform compliance
🌐 SEO / trade	seoer, huoke, outreach, jiankong	SERP planning, lead evidence grading, outreach copy, and safety monitoring
🔍 Review	shencha, shencha-content, shencha-ui, verifier, shencha-final, tijian	Editorial content gate, engineering and visual review, runtime verification, final review, and website checks
🏠 Repository	github	Strictly read-only GitHub health check: no Bash / Write / Edit, only reports and drafts

Acceptance outcomes are standardized as PASS / BLOCK / INCONCLUSIVE. INCONCLUSIVE means core evidence is missing and the work must not be delivered; SEND_BLOCKED means the content may be finalized but must not be sent.

Creating one agent manually requires a name, model, tools, system prompt, and options such as injecting AGENTS.md. This package predefines the roles and boundaries, so beginners do not need to create all 22 agents one by one.

Before Installation

Confirm the following:

• You completed ZCode Steps 1–3;
• ZCode is version 3.10.2 or later;
• at least one enabled model can complete a normal conversation;
• Git is installed;
• Python 3.9 or later is installed;
• Windows users also have PowerShell 5.1 or later.

If you do not know whether Git or Python is installed, continue. ZCode will check the prerequisites first and report anything missing.

1. Send the Install Prompt

Installation takes only a single sentence, and you don't even need to check the version number — the AI will read the repository README on its own to grab the current version's installation prompt and execute it under its security protocol:

(Prompt in Chinese to match the Chinese guide. Copy it unchanged.)

请在 ZCode 中安装或安全更新这个智能体包：repo=https://github.com/tony-apan/zcode_skills。
先实际读取当前 README 的「3 步自动安装」，获取唯一主提示词及其要求的安装协议，使用其中指定的固定 tag；无法读取、内容不完整或版本指向不一致时停止并报告，不凭记忆补写，也不自行改用 main。
执行前说明来源、目标版本、安装位置、拟修改内容和已有配置冲突；保留协议要求的确认，涉及删除或覆盖现有配置时先征得我同意。完成后汇报实际版本、岗位数量、模型分配及未完成项。

The AI follows the repository's security protocol

This instruction asks ZCode to read the upstream installation instructions; it does not authorize arbitrary actions. Before executing, the AI should state the target release, installation location, proposed changes, and any existing configuration conflicts; it stops if retrieval fails, and asks for your confirmation before deleting or overwriting existing configuration. This guide avoids pinning a release number to reduce version drift — changes to repository entry points, installation protocols, or the ZCode interface may still require updates here.

Installation instructions come from the upstream repository. Stop and verify unexpected source redirects, credential requests, or actions outside the agent-team installation scope. A README reference alone is not approval.

2. Send It to ZCode

Return to ZCode, create a new conversation, and send the complete prompt.

ZCode will work through this sequence:

1. check the system, Git, and Python;
2. fetch a fixed release;
3. identify configured model capabilities;
4. assign models to specialist roles;
5. preview the installation;
6. install and report roles, models, and capability fallbacks.

If ZCode reports missing Git, Python, or a usable model, address that item and retry. If it finds an existing role or local modification, read the conflict and proposed handling before continuing instead of repeatedly overwriting the installation.

3. Start a New Session

After installation finishes, create another new ZCode conversation. Agents are normally loaded when a session starts, so the old conversation may not show them immediately.

You do not need to reinstall ZCode or add each role manually.

4. Check the Roles

Open:

Lower-left gear → Settings → Agents

Check three things:

1. the specialist roles appear in the installed list;
2. each role shows its assigned model;
3. the toggle on the right is enabled.

The screenshot shows 22 installed roles assigned across GLM, DeepSeek, GPT, Kimi, and Gemini models. The total at the top may also include agents you created yourself, so use the installed list and installation report when checking the result.

Start Using the Team

Beginner Prompt

Copy this for the first task:

I have installed the AI agent team. First decide which specialist roles this task needs and give me a short collaboration plan that explains each role. Use different roles for production and review when practical. Then execute the plan and summarize the result.

My task: describe your task here.

The main agent can route the task to suitable roles. You can also name a workflow directly.

Coding Workflow

Ask coder to implement this fix, shencha to perform a static engineering review, verifier to run execution checks, and shencha-final to complete the final acceptance review.

Parallel Coding Comparison

Ask coder-gpt and coder-ds to implement two options in isolation on the same fixed baseline, each in its own worktree; neither may read the other's output. Then compare them against the same acceptance criteria. coder-ds uses MODE=PARALLEL_ALTERNATIVE.

Content Workflow

Ask seoer to create an evidence-based topic brief, writer to produce the draft, shencha-content to check facts, search intent, and conversion flow, and shencha-final to complete the final acceptance review.

Content Review

shencha-content accepts a review profile and tier, so the bar changes with the content type:

Ask shencha-content to review this professional article with review_profiles=[editorial,seo] review_tier=STANDARD.

Ask shencha-content to review this landing page with review_profiles=[conversion] review_tier=STANDARD.

Use review_tier=HIGH_RISK for high factual risk. Only STANDARD or HIGH_RISK reviews that return PASS produce publication_decision=GO; QUICK is always NO_GO.

B2B Workflow

Ask huoke to identify and verify target companies, then ask outreach to produce market-appropriate outreach copy with evidence grades and recommended next steps.

outreach creates outreach content; it does not mean the message has already been sent. Use the relevant sending tool and confirmation step when you are ready to send.

Demand Insight

Ask dongcha to use L1 PUBLIC_EVIDENCE to analyze this product material and public customer discussion, expand audiences, pain points, and topic seeds, and output the three pools plus handoffs to seoer, writer, and huoke; propose only, do not grant.

Diagram Workflow

Here is my business description. Ask mermaid to turn the complete process into a flowchart, with decision branches and manual steps clearly marked.

Repository Health Check

Ask github to run a read-only health check on this repository and output a graded issue list plus a README rewrite draft, without modifying anything locally or remotely.

Model Assignment

The recommended adaptive installation reads a sanitized model capability inventory and assigns models to roles. It uses details such as model name, context capability, and image-input support, so you do not need to select a model for every role manually.

You can update the mapping later:

1. add or enable a model in ZCode Model Settings;
2. return to the repository README and copy the update prompt for the current release;
3. explicitly ask ZCode to remap the models;
4. create a new session and check the role list again.

“More intelligent” means task routing, model matching, role specialization, and staged acceptance checks. It does not mean the package retrains or changes the underlying models.

Can One Model Work?

Yes. All 22 roles can still be installed with one model, and their responsibilities and workflow remain available.

However, several benefits become weaker:

• parallel alternatives lack real model diversity;
• production and review may share the same reasoning habits;
• visual roles may not have image-input capability;
• long-context and high-frequency lightweight tasks cannot be separated by capability and cost.

Beginners do not need many providers on day one. Start with the built-in model from Step 3, then add a strong-reasoning or vision model when a real task needs it.

Troubleshooting

Roles Are Missing

Create a new ZCode session, then check Settings → Agents. If the roles are still absent, return to the installation conversation and confirm whether it actually reported completion or stopped at a prerequisite or conflict check.

A Model Is Unavailable

If a role reports that its model or provider is unavailable:

1. confirm that the provider is enabled under Model Settings;
2. test the model in a normal new task;
3. use the current repository README's update prompt to remap the roles.

The Count Is Different

Releases update continuously and roles will be added over time, so treat the repository's current README as the source of truth. The total at the top may also include agents you created yourself, so compare the installation report and installed list instead.

What If Installation Fails

Check two things first, then let the AI continue:

1. Account allowance — enough for the built-in plan or third-party balance;
2. Network — a proxy or an unstable connection can cause failures.

Once those are ruled out, send this sentence to the AI in the same session; you do not need to start over:

请从刚才停止的地方继续安装。

Install the Laifaxin Skill Too

If you will also use Laifaxin for prospecting, you install a second skill. Recommended order:

A recommended order, not a hard dependency

Either can be installed first. The agent team is an enhancement — it lets different models specialize by role; the Laifaxin skill alone runs the complete outreach workflow. The order above is just more convenient.

The Laifaxin skill is installed in step 1 of the B2B inquiry workflow, which has the full prompt.

📋 Installation Pitfalls

Pitfall	Consequence	How to avoid
🔴 Installing from memory without reading the current repository README	You install an old version or mismatched roles, and errors are hard to trace	Use this guide's instruction so ZCode actually reads the current README and reports the fixed tag it selects; stop if retrieval fails or version references conflict
🔴 Treating an error as "broken" and giving up	Wasted effort, when it is usually quota or network	Keep the raw error in the install report, check quota and network, then have the AI resume install per Install failed
🟡 Installing one role at a time	It gets messy and duplicates appear	Send the full install prompt once and let ZCode report the install and model assignment together
🟢 Assuming the agent team is required	You get stuck on this step	It is an enhancement, not a hard requirement; the Laifaxin skill alone can run the full workflow

Completion Check

• You instructed ZCode to read the repository README's current prompt and complete installation;
• ZCode reported a completed installation with this release's role list and model assignment (roles keep growing — the report is the source of truth);
• you created a new session to load the roles;
• the installed roles and their models appear under Settings → Agents;
• a simple task completed a production → review → verification/final-check workflow.

Once every item above passes, continue with the Laifaxin skill install (see "Install the Laifaxin Skill Too" below) or start outreach from Connect Account.

📚 Further Reading

• 📚 Configure ZCode Plans and Models: go back here if your models are not set up yet
• 📚 AI Learning Path: place ZCode in a longer learning track
• 📚 Laifaxin B2B Inquiry System: start real outreach once the team is installed
• 👉 Foreign Trade AI Team on GitHub: the only source for the install prompt and role descriptions

🎉 You Have Completed the Four-Step ZCode Beginner Path

The agent team is neither Step 5 nor a hard requirement; the Laifaxin skill alone can run the full outreach workflow. To start finding prospects, continue with 📄 Build a B2B Inquiry Workflow.