CtrlK
BlogDocsLog inGet started
Tessl Logo

sanity-migration

Plans, implements, and reviews migrations from other CMSes and content systems into Sanity. Use when migrating or replatforming to Sanity from AEM, Adobe Experience Manager, Contentful, Strapi, Webflow, WordPress, Payload, Drupal, Markdown/MDX/frontmatter files, WXR/XML exports, CMS APIs, database dumps, static HTML, or when designing extraction, transformation, Portable Text conversion, asset migration, redirects, validation, and cutover workflows.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, lean orchestration skill that assumes competence, lays out a clear required workflow with validation and stop-checkpoints, and cleanly delegates detail to a verified set of one-level-deep reference files. Its only gap is the absence of a complete executable migration script example inline.

Suggestions

Add one short end-to-end extraction→transform→import→validate script skeleton (e.g., a Node snippet using createOrReplace with deterministic IDs) to lift actionability from concrete commands to copy-paste-ready.

Spell out an explicit validate→fix→re-run feedback loop (e.g., 'run validation, on failure review per-document issue list, fix, re-run import with --replace, re-validate') to make the retry cycle as concrete as the rest of the workflow.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding about what a CMS or migration is; assumes competence ('Treat migration as a content strategy and ETL project, not a blind lift-and-shift') and every section earns its place.

5 / 5

Actionability

Provides concrete commands and identifiers ('createOrReplace', 'createIfNotExists', 'sanity datasets import --replace', 'defineType/defineField/defineArrayMember', the npx install command) and a concrete deliverable list, but includes no full copy-paste migration script example.

4 / 5

Workflow Clarity

Clear required-workflow sequence with 'Stop and Ask' checkpoints and explicit validation requirements (count/sample/reference/redirect checks before cutover, validation summary), though a full inline validate→fix→retry loop is not spelled out.

4 / 5

Progressive Disclosure

Clear overview pointing to real one-level-deep references (general.md first, then verified platform files aem/contentful/strapi/webflow/wordpress/payload/drupal/markdown) with a well-signaled Reference Map and no nested references.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong, comprehensive trigger statement that clearly defines both the skill's scope and when to invoke it, with extensive concrete source-system keywords. It uses correct third-person voice and is highly distinct from generic skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Plans, implements, and reviews migrations', 'extraction, transformation, Portable Text conversion, asset migration, redirects, validation, and cutover workflows') with comprehensive coverage of migration sub-tasks.

5 / 5

Completeness

Explicitly answers both what ('Plans, implements, and reviews migrations... into Sanity') and when via a concrete 'Use when migrating or replatforming...' trigger clause.

5 / 5

Trigger Term Quality

Comprehensive natural terms and synonyms across source systems ('AEM, Adobe Experience Manager, Contentful, Strapi, Webflow, WordPress, Payload, Drupal, Markdown/MDX/frontmatter files, WXR/XML exports, CMS APIs, database dumps, static HTML') that users would actually name.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (CMS-to-Sanity migration) with named source systems and distinct triggers; third-person voice is used correctly with minimal overlap risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
sanity-io/agent-toolkit
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.