Mas Data Model
AUTO-MAS-Project/AUTO-MAS
Define backend data modeling standards for Python services. An agent skill from AUTO-MAS-Project/AUTO-MAS.
Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other…
Install Content Modeling Best Practices
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sanity-io/agent-toolkit content-modeling-best-practices --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sanity-io/agent-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-modeling-best-practices .claude/skills/content-modeling-best-practices && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "content-modeling-best-practices" agent skill from https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practices into .claude/skills/content-modeling-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-modeling-best-practices", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practicesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sanity-io/agent-toolkit content-modeling-best-practices --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sanity-io/agent-toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/content-modeling-best-practices .agents/skills/content-modeling-best-practices && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-modeling-best-practices" agent skill from https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practices into .agents/skills/content-modeling-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-modeling-best-practices", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sanity-io/agent-toolkit content-modeling-best-practices --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sanity-io/agent-toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/content-modeling-best-practices .cursor/skills/content-modeling-best-practices && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-modeling-best-practices" agent skill from https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practices into .cursor/skills/content-modeling-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-modeling-best-practices", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sanity-io/agent-toolkit.git --path skills/content-modeling-best-practices--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sanity-io/agent-toolkit content-modeling-best-practices --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sanity-io/agent-toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/content-modeling-best-practices .gemini/skills/content-modeling-best-practices && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-modeling-best-practices" agent skill from https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practices into .gemini/skills/content-modeling-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-modeling-best-practices", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sanity-io/agent-toolkit content-modeling-best-practicesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sanity-io/agent-toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/content-modeling-best-practices .github/skills/content-modeling-best-practices && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-modeling-best-practices" agent skill from https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practices into .github/skills/content-modeling-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-modeling-best-practices", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sanity-io/agent-toolkit content-modeling-best-practices --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sanity-io/agent-toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/content-modeling-best-practices .opencode/skills/content-modeling-best-practices && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-modeling-best-practices" agent skill from https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practices into .opencode/skills/content-modeling-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-modeling-best-practices", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
content-modeling-best-practices- GitHub stars
- 188
- Used in
- 1 other repo
- Token cost
- ~463 tokens
- SKILL.md length
- 160 words
- Files
- 5 (incl. references)
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other…
- Works in 4 steps: Content is data, not pages — Structure… → Single source of truth — Avoid content… → Future-proof — Design for channels that… → …
- Refactoring content types
- SKILL.md covers When to Apply, Core Principles and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Content Modeling Best Practices is an agent skill from sanity-io/agent-toolkit, published by the product's own GitHub organization. Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.
Its SKILL.md is about 460 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/content-reuse.md`, `references/reference-vs-embedding.md` and `references/separation-of-concerns.md`).
It sits in Databases, covering Content strategy, Database schema design and Refactoring. The repository describes itself as: Collection of resources to help AI agents build better with Sanity. The licence is MIT.
When your agent uses it
- Refactoring content types
- Deciding field shapes
- Debating reusable versus nested content
- Planning omnichannel content models
Example prompts
- “/content-modeling-best-practices”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Content is data, not pages — Structure content for meaning, not presentation
- Single source of truth — Avoid content duplication
- Future-proof — Design for channels that don't exist yet
- Editor-centric — Optimize for the people creating content
What it can do on your machine
Read from SKILL.md and the folder at commit 3fe6c8a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Content Modeling Best Practices loads about 463 tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 160 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sanity-io/agent-toolkit at commit 3fe6c8a, republished under its MIT licence (© sanity-io). 160 words, ~463 tokens.
Download SKILL.mdSave it as
.claude/skills/content-modeling-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- content-modeling-best-practices
- description
- Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.
Content Modeling Best Practices
Principles for designing structured content that's flexible, reusable, and maintainable. These concepts apply to any headless CMS but include Sanity-specific implementation notes.
When to Apply
Reference these guidelines when:
- Starting a new project and designing the content model
- Evaluating whether content should be structured or free-form
- Deciding between references and embedded content
- Planning for multi-channel content delivery
- Refactoring existing content structures
Core Principles
- Content is data, not pages — Structure content for meaning, not presentation
- Single source of truth — Avoid content duplication
- Future-proof — Design for channels that don't exist yet
- Editor-centric — Optimize for the people creating content
References
Start with the reference that matches the modeling decision in front of you, instead of loading every topic at once. See references/ for detailed guidance on specific topics:
references/separation-of-concerns.md— Separating content from presentationreferences/reference-vs-embedding.md— When to use references vs embedded objectsreferences/content-reuse.md— Content reuse patterns and the reuse spectrumreferences/taxonomy-classification.md— Flat, hierarchical, and faceted classification
© sanity-io, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/content-modeling-best-practices of sanity-io/agent-toolkit.
- SKILL.md
- references/content-reuse.md
- references/reference-vs-embedding.md
- references/separation-of-concerns.md
- references/taxonomy-classification.md
Open the folder on GitHubat commit 3fe6c8a
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sanity-io/agent-toolkit, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Content Modeling Best Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Modeling Best Practices this skillsanity-io/agent-toolkit | 188 | 1 repos | ~463 | Automated safety check: Pass | MIT | |
| Mas Data ModelAUTO-MAS-Project/AUTO-MAS | 711 | — | ~1.6k | Automated safety check: Pass | AGPL-3.0 | |
| Memstack Development Migration Plannercwinvestments/memstack | 423 | — | ~3.7k | Automated safety check: Pass | Proprietary | |
| Effect TSmattiacerutti/supernova | 185 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Effect TStellahq/opensession | 394 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Commonmark Conformancejolars/panache | 237 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Memstack Development Migration Planner
cwinvestments/memstack
A skill your agent uses when the user says 'migration', 'schema change', 'database migration', 'alter table', 'add column', 'change type', 'rollback plan', or needs safe database schema evolution…
Effect TS
mattiacerutti/supernova
Write idiomatic Effect v4 TypeScript following official best practices from effect-solutions and the Effect source.
Effect TS
tellahq/opensession
Write idiomatic Effect v4 TypeScript verified against the pinned effect@4.0.0-rc.112 source.
Commonmark Conformance
jolars/panache
Grow Panache's CommonMark spec conformance under Flavor::CommonMark by running every spec.txt example through the shared parser, comparing rendered HTML against the spec's expected HTML…
Databuddy Internal
databuddy-analytics/Databuddy
Work inside the Databuddy monorepo for internal implementation, debugging, review, and refactoring.
More from sanity-io/agent-toolkit
All 8 skills in this repo- Official
Sanity Best Practices
sanity-io/agent-toolkit
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints…
- Official
Portable Text Conversion
sanity-io/agent-toolkit
Convert HTML and Markdown content into Portable Text blocks for Sanity.
- Official
Sanity Migration
sanity-io/agent-toolkit
Plans, implements, and reviews migrations from other CMSes and content systems into Sanity.
- Official
Portable Text Serialization
sanity-io/agent-toolkit
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text.
- Official
SEO Aeo Best Practices
sanity-io/agent-toolkit
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces.
- Official
Sanity Studio Upgrade
sanity-io/agent-toolkit
Produces a tailored Sanity Studio upgrade plan by inspecting the repository's installed versions, config, and source, then reporting only the breaking changes that actually apply.
Related
Categories
Questions about Content Modeling Best Practices
What does Content Modeling Best Practices do?
Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other…. Content Modeling Best Practices is an agent skill from sanity-io/agent-toolkit, published by the product's own GitHub organization. Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes.
When should I use Content Modeling Best Practices?
Content Modeling Best Practices fits situations like: refactoring content types; deciding field shapes; debating reusable versus nested content; planning omnichannel content models.
How do I install Content Modeling Best Practices in Claude Code?
Run `npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a claude-code`. Or copy the skill folder (skills/content-modeling-best-practices in sanity-io/agent-toolkit) into .claude/skills/content-modeling-best-practices in your project. Claude Code loads it when a task matches its description.
How do I install Content Modeling Best Practices in Codex?
Run `npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a codex`. Or copy the skill folder (skills/content-modeling-best-practices in sanity-io/agent-toolkit) into .agents/skills/content-modeling-best-practices in your project. Codex loads it when a task matches its description.
Can I use Content Modeling Best Practices in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sanity-io/agent-toolkit --skill content-modeling-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-modeling-best-practices, .gemini/skills/content-modeling-best-practices, .github/skills/content-modeling-best-practices and .opencode/skills/content-modeling-best-practices in your project.
What does Content Modeling Best Practices need to run?
SKILL.md names no scripts, command-line tools or credentials: Content Modeling Best Practices is instructions for the agent only.
Does Content Modeling Best Practices access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Content Modeling Best Practices safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Content Modeling Best Practices use?
Content Modeling Best Practices is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Content Modeling Best Practices use?
About 463 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.
What are the alternatives to Content Modeling Best Practices?
Skills that share tags, products or a category with Content Modeling Best Practices: Mas Data Model (AUTO-MAS-Project/AUTO-MAS, 711 stars), Memstack Development Migration Planner (cwinvestments/memstack, 423 stars), Effect TS (mattiacerutti/supernova, 185 stars) and Effect TS (tellahq/opensession, 394 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Content Modeling Best Practices?
sanity-io (a GitHub organization, an official publisher) maintains it in sanity-io/agent-toolkit, which has 188 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.
Source: sanity-io/agent-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.