Portable Text Serialization

What it does

This source describes the shared component-mapping pattern used by the Portable Text library family, then directs React, Vue, Svelte, Astro and string-output tasks to their own references. It distinguishes decorator marks from annotations and calls out the structure required for lists and custom blocks.

Best for

Developers adding a Sanity rich-text renderer or debugging missing marks, unknown blocks and inconsistent list output.

Tradeoffs and requirements

Supporting several frameworks does not make their APIs identical. Unknown custom types, unsafe link schemes and raw HTML output need deliberate treatment. A visually correct example may still be inaccessible or mishandle unusual editor-authored content.

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/portable-text-serialization --skill portable-text-serialization

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.

• Network Access — review the source context.

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

Inventory the content types and marks actually stored in the dataset. Select the framework-specific reference and implement explicit renderers with sensible behavior for unsupported content.

How to judge the result

Use fixtures containing nested lists, links, inline objects and absent optional fields. Check semantic HTML, keyboard access and escaping as well as appearance, and confirm that serialization to another format preserves the required information.