Sanity Best Practices

What it does

The source directs broad Sanity development work to selected topic references instead of loading every guide. It spans GROQ, TypeGen, rich text, images, localization, Functions and infrastructure configuration, with global guidance on document identity and relationships.

Best for

Developers maintaining a Sanity-backed product who need the right specialized reference for a concrete implementation decision.

Tradeoffs and requirements

The breadth of the entrypoint should not be confused with complete coverage of every integration. Hosted assets and services can carry costs. It contains context-specific identity rules that may differ for ordinary document creation and deterministic migration workflows.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/sanity-io/agent-toolkit/tree/3ed3a143f8d3413faa7790ac0b2274fd3a8a6320/skills/sanity-best-practices --skill sanity-best-practices

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

No configured text patterns matched. Unmatched or concealed behavior can still exist.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

85/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

41/100

41

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Identify whether the task concerns data modeling, querying, Studio or delivery. Inspect the existing project and only the matching references, then make the smallest change compatible with its content model.

How to judge the result

Validate schema and generated types, exercise representative queries and check the actual editing or preview flow. Confirm asset handling, document relationships and expected costs before treating a local demonstration as production-ready.