How do I install the Ezorm Write YAML Mongo skill?

Run npx skillmds@latest add tomevault-io/ezorm-write-yaml-mongo 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 Ezorm Write YAML Mongo safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ezorm Write YAML Mongo?

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 Ezorm Write YAML Mongo free to use?

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

Who published Ezorm Write YAML Mongo?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ezorm Write YAML Mongo by tomevault-io

Name: Ezorm Write YAML Mongo
Author: tomevault-io

Ezorm Write YAML Mongo

Write ezorm YAML schema files for this repo (mongo only). Use when asked to define or update ezorm YAML for mongo collections, fields, indexes, flags, embeds, or relations; output YAML only (no Go code). Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Ezorm Write Yaml

Scope

Write ezorm YAML schemas from user requirements for mongo and emit YAML only. Read these files when schema details or examples are needed:

doc/schema/yaml.md
doc/schema/yaml_mongo.md
e2e/mongo/*.yaml If the local references/ or assets/ directories are missing, run: scripts/init.sh (or scripts/init.sh --force to refresh). Validate with scripts/validate.sh.

Workflow

Restate the domain model in simple entities and relationships. Ask one clarification only if critical (missing entities, relationship direction, or required constraints).
Choose representation:
- Embedded structure: define a separate entity with embed: true and reference it with list<EmbedType> or EmbedType fields.
- Separate collection: define separate entities and connect via ID fields.
Map fields:
- Use mongo field types from doc/schema/yaml_mongo.md.
- Add flags like index, unique, sort, nullable as needed.
- Use attrs with bsonTag/jsonTag only when a specific storage name is requested.
Set collection metadata:
- Always include table and dbname.
- Default table to snake_case of the entity name.
- Default dbname to default unless the user provides one.
Add constraints:
- Use indexes, uniques, primary as required.
Output only YAML (no Go code, no prose). Use --- to separate multiple entities.

Output Rules

Emit a valid YAML schema file (or multiple YAML documents) and nothing else.
Keep names consistent with user domain language.
Prefer minimal fields; do not invent behavior.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: ezorm-write-yaml-mongodescription: Write ezorm YAML schema files for this repo (mongo only). Use when asked to define or update ezorm YAML for mongo collections, fields, indexes, flags, embeds, or relations; output YAML only (no Go code). Use when this capability is needed.---# Ezorm Write Yaml## ScopeWrite ezorm YAML schemas from user requirements for mongo and emit YAML only.Read these files when schema details or examples are needed:- `doc/schema/yaml.md`- `doc/schema/yaml_mongo.md`- `e2e/mongo/*.yaml`If the local `references/` or `assets/` directories are missing, run:`scripts/init.sh` (or `scripts/init.sh --force` to refresh).Validate with `scripts/validate.sh`.## Workflow1. Restate the domain model in simple entities and relationships. Ask one clarification only if critical (missing entities, relationship direction, or required constraints).2. Choose representation: - Embedded structure: define a separate entity with `embed: true` and reference it with `list<EmbedType>` or `EmbedType` fields. - Separate collection: define separate entities and connect via ID fields.3. Map fields: - Use mongo field types from `doc/schema/yaml_mongo.md`. - Add `flags` like `index`, `unique`, `sort`, `nullable` as needed. - Use `attrs` with `bsonTag`/`jsonTag` only when a specific storage name is requested.4. Set collection metadata: - Always include `table` and `dbname`. - Default `table` to snake_case of the entity name. - Default `dbname` to `default` unless the user provides one.5. Add constraints: - Use `indexes`, `uniques`, `primary` as required.6. Output only YAML (no Go code, no prose). Use `---` to separate multiple entities.## Output Rules- Emit a valid YAML schema file (or multiple YAML documents) and nothing else.- Keep names consistent with user domain language.- Prefer minimal fields; do not invent behavior.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/ezbuy) — claim your Tome and manage your conversions.

Frequently asked questions