How do I install the Eat Template Builder skill?

Run npx skillmds@latest add lennith/eat-template-builder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Eat Template Builder safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Eat Template Builder?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Eat Template Builder free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Eat Template Builder?

Lennith (@lennith) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Eat Template Builder by lennith — Agent Skill

Name: Eat Template Builder
Rating: 4.2 (5 reviews)
Author: Lennith

Eat Template Builder

Scaffold and build EasyAgentTeam template bundles from a reusable workspace, with required plan alignment before generation, Markdown Mermaid workflow confirmation before final workflow output, and built-in check/publish commands through the local template bundle guard runtime. Use when the user wants to create or update an EasyAgentTeam template workspace, define reusable agents and workflow templates, import skills into a template bundle, validate a bundle, or publish it to the EasyAgentTeam backend.

Lennith Updated Sep 22, 2026

File contents

EasyAgentTeam Template Builder

Start With A Workspace Copy

Create a fresh workspace copy with scripts/init_eat_workspace.py <target-dir>.
Work inside that copied workspace, not inside the skill folder.
Keep the generated layout intact:
- .agent-tools/
- agents/
- roles/
- skills/
- bundles/
- reports/
- workspace/

Plan-First Rule

Do not write the final bundle or run check/publish until planning is aligned with the user.

Clarify and lock:

goal and scope
reusable agent responsibilities
skills to import
IDs and naming rules
project and workflow shape
deliverables and evidence files

If a workflow is involved, present a Markdown Mermaid flowchart and get explicit user confirmation before generating the final workflow template, workflow run, or bundle.

Read references/planning-checklist.md when details are still fuzzy.

Working Contract

Follow the generated workspace contract in AGENTS.md and keep the six-step evidence flow closed:

goal
roles
agents
project/workflow
bundle
submit

Each step must leave evidence under reports/step-0X-* before moving forward.

Bundle Rules

Keep agent prompts limited to function, usable external tools, and method.
Do not describe EasyAgentTeam runtime internals inside agent prompts.
Keep roles reusable rather than one-off.
Keep workflow task contracts explicit: objective, input, output, constraints, boundary, exception handling, acceptance criteria.
Keep artifacts under workspace/ and make write_set cover them without cross-task overlap.
Keep workflow_run.auto_start false.
An empty local skills/ directory is allowed during planning; local skill import stays skipped until real skill packages are added.

Read references/workspace-contract.md if you need the detailed constraints.

Validation And Publish

Use only these entrypoints inside the copied workspace:

node .agent-tools/scripts/template_bundle_guard.mjs check
node .agent-tools/scripts/template_bundle_guard.mjs publish

publish must remain check-first and must not auto-start runs.

References

references/planning-checklist.md
references/workspace-contract.md

---name: eat-template-builderdescription: Scaffold and build EasyAgentTeam template bundles from a reusable workspace, with required plan alignment before generation, Markdown Mermaid workflow confirmation before final workflow output, and built-in check/publish commands through the local template bundle guard runtime. Use when the user wants to create or update an EasyAgentTeam template workspace, define reusable agents and workflow templates, import skills into a template bundle, validate a bundle, or publish it to the EasyAgentTeam backend.---# EasyAgentTeam Template Builder## Start With A Workspace Copy1. Create a fresh workspace copy with `scripts/init_eat_workspace.py <target-dir>`.2. Work inside that copied workspace, not inside the skill folder.3. Keep the generated layout intact: - `.agent-tools/` - `agents/` - `roles/` - `skills/` - `bundles/` - `reports/` - `workspace/`## Plan-First RuleDo not write the final bundle or run `check`/`publish` until planning is aligned with the user.Clarify and lock:- goal and scope- reusable agent responsibilities- skills to import- IDs and naming rules- project and workflow shape- deliverables and evidence filesIf a workflow is involved, present a Markdown Mermaid flowchart and get explicit user confirmation before generating the final workflow template, workflow run, or bundle.Read `references/planning-checklist.md` when details are still fuzzy.## Working ContractFollow the generated workspace contract in `AGENTS.md` and keep the six-step evidence flow closed:1. `goal`2. `roles`3. `agents`4. `project/workflow`5. `bundle`6. `submit`Each step must leave evidence under `reports/step-0X-*` before moving forward.## Bundle Rules- Keep agent prompts limited to function, usable external tools, and method.- Do not describe EasyAgentTeam runtime internals inside agent prompts.- Keep roles reusable rather than one-off.- Keep workflow task contracts explicit: objective, input, output, constraints, boundary, exception handling, acceptance criteria.- Keep `artifacts` under `workspace/` and make `write_set` cover them without cross-task overlap.- Keep `workflow_run.auto_start` false.- An empty local `skills/` directory is allowed during planning; local skill import stays skipped until real skill packages are added.Read `references/workspace-contract.md` if you need the detailed constraints.## Validation And PublishUse only these entrypoints inside the copied workspace:- `node .agent-tools/scripts/template_bundle_guard.mjs check`- `node .agent-tools/scripts/template_bundle_guard.mjs publish``publish` must remain check-first and must not auto-start runs.## References- `references/planning-checklist.md`- `references/workspace-contract.md`

Frequently asked questions