build-agent
Skill1 starsChanged 50 days agoMITView on GitHub
Builds or changes a Moveo.AI conversational AI agent. Use when the user wants to create an agent from a brief or to write or fix its guidelines, tone or escalation rules. Also use to add intents and workflows, or to train, publish or roll back an agent. Requests such as "make the bot handle refunds" or "hand refunds over to a human" on a Moveo agent also qualify. Also matches Portuguese or Greek requests, such as "criar um agente" or "φτιάξε έναν agent".
9 other projects use a version of this.
Adopted by
Most recently taken up by
- Happy-Technologies-LLC/happy-platform-skillstheir own version, first seen Nov 1, 2026
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- duyet/clickhouse-monitoringtheir own version, first seen Oct 8, 2026
- anayatkhan1/kittheir own version, first seen Jul 27, 2026
- LukeRenton/explore-claude-codetheir own version, first seen Jul 23, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- anthropics/knowledge-work-plugins★ 36ksame name
- LukeRenton/explore-claude-code★ 329same name
- duyet/clickhouse-monitoring★ 303same name
- Agile-V/agile_v_skills★ 54same name
- Happy-Technologies-LLC/happy-platform-skills★ 41same name
- anayatkhan1/kit★ 16same name
- Big-LAORE/Biblioth-que-de-skills★ 1same name
- schift-io/skills★ 1same name
- AgentJDrew/agent-team-factory★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- get-startedSkill
- knowledge-baseSkill
- test-agentSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 2 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
If moveo_whoami did not confirm the account in this conversation, run the get-started skill first.
- Very specific: line 19
Read moveo://schemas/guideline-authoring before you write any guideline text.
- Very specific: line 20
Read moveo://schemas/agent-languages and moveo://schemas/agent-types.
- Very specific: line 21
Call moveo_create_agent with the name, language, agent type and the guidelines distilled from the brief, in one call.
- Very specific: line 23
Call moveo_validate_agent_guidelines and fix what it reports.
- Very specific: line 25
Test the draft with the test-agent skill before you publish.
- Very specific: line 33
Read before you write: moveo_get_agent_guidelines for the playbook, moveo_list_agent_workflows for the flows.
- Very specific: line 42
Call moveo_publish_agent once, and wait for it to return.
- Very specific: line 43
If the new version ends in status: 'failed', fix the content, wait for training, and publish again.
- Distinctive: line 53
If guidelines repeat the knowledge base, answers go stale after documents change.
- Distinctive: line 59
Before each publish, rollback or delete, name the account, the resource and what will change, then wait for an explicit yes.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Build a Moveo.AI agent
If moveo_whoami did not confirm the account in this conversation, run the get-started skill first.
The model
- An agent has one editable draft, version 0, and a list of immutable published versions. Only the draft accepts edits. Customers get the latest published version.
- Guidelines are the natural-language playbook: goal, overview, features, objections, tone, handover rules. The guideline text becomes the agent's runtime prompt.
- A workflow is a dialog plus the intents its nodes reference. Use workflows for flows that must happen exactly the same way every time, such as collecting an order number before a refund. Use guidelines for everything else.
- Training starts on its own after an edit to intents, dialogs, guidelines or tools.
Build a new agent
- Read
moveo://schemas/guideline-authoringbefore you write any guideline text. It gives the purpose and character budget of each field. - Read
moveo://schemas/agent-languagesandmoveo://schemas/agent-types. If the brief does not state the language, ask the user. Thelanguagefield is permanent. - Call
moveo_create_agentwith the name, language, agent type and theguidelinesdistilled from the brief, in one call. - For each flow that must be exact, read
moveo://schemas/workflow-node-typesandmoveo://guides/workflow-authoring, then callmoveo_create_agent_workflow. See references/workflows.md. - Call
moveo_validate_agent_guidelinesand fix what it reports. - Poll
moveo_get_agentuntilstatusisavailable. - Test the draft with the
test-agentskill before you publish. - Publish only after the user agrees. See "Publish" below.
The build_agent_from_brief server prompt runs steps 1 to 8 in one pass. If the user has a complete brief and wants no questions, offer it.
Change an existing agent
- Find the agent in the agents snapshot (see
get-startedfor its uri). If the name is ambiguous, ask. - Read before you write:
moveo_get_agent_guidelinesfor the playbook,moveo_list_agent_workflowsfor the flows. - If the change touches more than one workflow, moves a jump, or changes a handover or a tag, show a plan before the first write. Give the current state, each change as before and after, and the nodes in other workflows that point at what you change (
moveo_get_dialog_references). Make no change until the user agrees to the plan. - Make the smallest edit that does the job.
moveo_update_agent_guidelinesdeep-merges, so send only the fields you change. - Show the user what changed with
moveo_diff_agent_versionsfrom the latest published version to0.
Publish
- Poll
moveo_get_agentuntilstatusisavailable. - Show the diff from the latest published version to
0and get the user's approval. - Call
moveo_publish_agentonce, and wait for it to return. Do not call it again while it runs. - If the new version ends in
status: 'failed', fix the content, wait for training, and publish again. If the user wants the previous behavior back, offermoveo_rollback_agent_to_version.
Failure modes
- Publish during training serves a half-trained agent. Always wait for
status: 'available'. moveo_update_agentedits top-level fields such as name, model, knowledge base and tools. Guideline fields sent to it are wrong. Usemoveo_update_agent_guidelinesfor the playbook.- An edit to a published version fails. Edit the draft, then publish.
- Rollback overwrites the current draft. Diff first. If the draft holds unpublished work, warn the user.
moveo_clone_agentworks only on an agent that was never published.- Deleting an intent leaves dialog nodes that point at a slug that no longer exists. Call
moveo_get_dialog_referencesfirst, then name what will break and wait for the user's yes. - If guidelines repeat the knowledge base, answers go stale after documents change. Put facts in the knowledge base and behavior in the guidelines.
- An agent answers from a knowledge base only with two settings: the knowledge base is attached, and the
search_knowledge_basetool is enabled. Use theknowledge-baseskill for that.
Rules for every Moveo task
- Reply in the user's language. Keep tool arguments, resource names and the product terms environment, agent and knowledge base as the tools expect them.
- Before each publish, rollback or delete, name the account, the resource and what will change, then wait for an explicit yes. This holds even when the user asked for the change in the same message, because a request can name the wrong account or resource.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

