Hire an AI China network engineer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A list of facts it has and gaps it needs before any command is safe.
• Pre-checks, including what to save, what to test in a lab and who must approve.
• Draft commands for your vendor, marked as drafts to verify on your exact model.
• Commands that read the state of the device, to prove the change worked.
• A written rollback with the exact commands to undo each step.
• MLPS 2.0 network notes when they apply, and a short troubleshooting list.

How it does the job well

• Refer a compliance decision to a qualified assessor, and a live outage to the user's on-call engineer or the vendor.
• State the vendor and OS version before touching anything. VRP, Comware V7, RGOS, and StoneOS differ in syntax, defaults, and feature availability between releases. A command that is valid on S5720 VRP V200R019 is not guaranteed on V200R022. Ask, or inspect display version / show version first.
• Never configure without a rollback plan. Every change ships with the exact commands to revert it: undo, no, or the saved pre-change config. For StoneOS, capture show configuration before the change window and diff after — that is the rollback artifact.
• Persist explicitly. VRP: save. Comware: save force. RGOS: write. StoneOS: config persists, but document the change. Forgetting the save step is the single most common production incident in this ecosystem.
• Do not run disruptive commands casually. debug, packet capture, interface resets, routing process clears, and HA failovers require a maintenance window and someone who can answer the phone. Same discipline as any vendor, no exceptions for "it's just a Chinese box."
• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: You must add a VLAN, route, NAT rule or firewall rule on Huawei, H3C, Ruijie or Hillstone gear.

• Facts and gaps. Each device with its vendor, model and version, and the facts still missing.
• Change summary. What changes, why, which devices it touches and the main risk.
• Pre-checks. The config backup, lab test, change window, approver and on-call person needed before any command.
• Draft commands. Commands in your vendor's style, marked as drafts, with a way to check the feature is supported.
• Verify. Read-only commands for each device and what a good result looks like.
• Rollback. The exact commands to undo each step, and the save step for your vendor.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Kent Beck and Margaret Hamilton would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Identify the stack. It confirms which of Huawei VRP, H3C Comware, Ruijie RGOS or Hillstone StoneOS each device runs, and the model and version.
• Check what is missing. It lists facts it needs, such as version, topology and current config. It does not guess any of them.
• Write pre-checks. It adds saving the current config, a lab test, a change window and an owner sign-off before any change.
• Draft the change. It writes the commands in your vendor's style and labels them drafts. If a feature depends on the model, it gives a command to check support.
• Prove the result. It adds read-only commands that show the state, and checks the route table and the live traffic path separately.
• Write the way back. It writes the exact commands to undo each step, and the save step each vendor needs.
• Add MLPS notes. If your network is assessed, it checks zones, deny-by-default policy, log shipping, time sync and device hardening.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id engineering-china-network-engineer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/engineering-china-network-engineer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The vendor, model and software version of each device. The output of "display version" or "show version" works.
• What must change and why, in plain words.
• A topology note, such as which switch connects to which firewall and the ISP links.
• Your current relevant config with passwords, keys and community strings removed.
• Your change window and who approves and answers the phone (optional).
• Your MLPS level, if the network is assessed (optional).

Helpful context (optional)

• The output of the version command for each device.
• A topology drawing or a list of links.
• Your last known good config backup.

Tools and access

• Claude, ChatGPT or Gemini: Any of them can write the plan. Attach the topology and the config with secrets removed.
• A lab unit or a vendor simulator: You can test the draft commands where an error cannot take down a live network.

Functions and deliverables

• China network engineer: Get a change plan for Huawei, H3C, Ruijie or Hillstone gear with pre-checks, exact commands, checks, rollback and MLPS 2.0 network notes.
  • A list of facts it has and gaps it needs before any command is safe.
  • Pre-checks, including what to save, what to test in a lab and who must approve.
  • Draft commands for your vendor, marked as drafts to verify on your exact model.
  • Commands that read the state of the device, to prove the change worked.
  • A written rollback with the exact commands to undo each step.
  • MLPS 2.0 network notes when they apply, and a short troubleshooting list.
  Source: Michael Sitarzewski and Agency Agents contributors.
• Release day rollback planner: Plan a safe release before you ship. Paste what you are releasing and where it runs. Get checks, steps, a rollback plan and a way to confirm it worked.
  • A risk rating with the reason
  • A pre-release checklist
  • Steps with pause points
  • Undo signs and steps, and a post-release check
• Prompt change manager: Set up prompt versioning, tests and rollback for AI features already live. Get a prompt registry, eval plan and safe deploy steps for your team.
  • Prompt registry design
  • Versioning rules
  • Evaluation pipeline plan
  • A/B test and rollback process
  Source: Alireza Rezvani.
• Pre-launch ad checker: Share your ad, audience and approved facts. Get located issues, fixes, human checks and a custom score before launch.
  • A version-bound list of observed problems and the smallest fixes
  • The buyer argument checked against the supplied facts and proof
  • A clear list of media, destination, tracking or spec checks still needed
  • A scoped verdict and observed/eligible coverage
  • An internal editing score, with any post-fix score marked provisional
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.
• Kent Beck: Plan a software change using Kent Beck’s recorded approach. List the cases, take small steps and keep code tidying separate from new behaviour.
  • Your problem worked on the way Kent Beck would: their questions, their method, their push-back
  • The answer or the work, in Kent Beck's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Margaret Hamilton: Review a system failure plan using Margaret Hamilton’s recorded approach. Check handoffs, priorities, warnings and what happens when people make mistakes.
  • Your problem worked on the way Margaret Hamilton would: their questions, their method, their push-back
  • The answer or the work, in Margaret Hamilton's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You must add a VLAN, route, NAT rule or firewall rule on Huawei, H3C, Ruijie or Hillstone gear.
• Your team knows Cisco and needs the same job translated to a domestic vendor.
• You are preparing a network for a level 2 or level 3 MLPS assessment.
• A permitted flow still fails, and you want a short list of what to check first.

Limits to check before starting

• You run Cisco, Juniper or another non-Chinese vendor. Use the Network engineer.
• Your network is down right now. Call your on-call engineer or vendor support. This agent cannot see your devices.
• You want a full security or compliance audit, or an assessor's sign-off. Use the Compliance Auditor agent. This agent covers the network part only.
• You plan to paste commands onto live equipment with no lab test, change window or owner approval.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. Or paste SKILL.md into a new chat, then paste references/source-agent.md after it.
• Remove passwords, keys and SNMP community strings from anything you paste.
• Give the vendor, model and software version for every device, then describe the change and your topology.
• Your AI asks once for anything missing. Without a version it gives no commands and asks you to run "display version" or "show version".
• Read the pre-checks and rollback first. Run the draft commands in a lab or test unit before any live device.
• Run changes yourself in the approved window, with someone on call. Keep the before and after output as proof.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/engineering-china-network-engineer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.