Strawberry can list Sanity projects and datasets, run queries, retrieve an exact document, and submit supported document mutations. That gives content teams a way to investigate the real source content first, identify the specific records that need attention, and prepare a constrained change rather than operating from a copied export.
It works well for content audits, taxonomy cleanup, structured migrations, and editorial checks where the document IDs and fields must stay visible all the way through review.
01
Find the affected documents before proposing a fix.
Content operations become risky when a change is described only by title.
Strawberry can query the selected dataset, retrieve the exact document, and show the fields that support the recommendation, so reviewers can distinguish a broad pattern from a one-off exception.
02
Audit structured content without flattening the model.
A CMS audit should preserve the relationship between a field, its document type, and the editorial rule it violates. Use Sanity queries to identify the pattern, then let Strawberry summarize the result in a way that a content owner can act on.
03
Make a mutation narrow enough to inspect.
Sanity supports document mutations, but the useful unit of review is a bounded proposed change. Strawberry can retrieve the current document, outline the target fields, and present the patch in context before a content owner decides whether it should be applied.
04
Turn your editorial check into a reusable CMS skill.
A Sanity skill can define the dataset, query constraints, acceptance criteria, and review format for an audit your team repeats. Pair it with a routine to prepare a weekly exception list, while keeping mutations as an explicit human-reviewed step.
Sanity Strawberry