How do I install the API Media Types Vendor Content Types skill?

Run npx skillmds@latest add deangrant/api-media-types-vendor-content-types in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is API Media Types Vendor Content Types safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with API Media Types Vendor Content Types?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is API Media Types Vendor Content Types free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published API Media Types Vendor Content Types?

deangrant (@deangrant) published this skill. Their other Agent Skills are listed on their SkillMD profile.

API Media Types Vendor Content Types by deangrant

Name: API Media Types Vendor Content Types
Author: deangrant

API Media Types Vendor Content Types

Choose and document HTTP media types including vendor trees (vnd), structured suffixes (+json), and MIME versioning. Use when minting custom types or reviewing Content-Type versioning schemes.

deangrant ad573db 4 files · 2.4 KB Updated Sep 17, 2026

File contents

Media Types and Vendor Content Types

Use this skill when selecting media type identifiers beyond plain JSON.

1. Structure (RFC 6838)

type/subtype; parameters — case-insensitive names. Trees: standards, vendor vnd., personal prs., unregistered x. (discouraged).

Structured suffix: +json / +xml so generic parsers still work.

Example: application/vnd.api+json; version=2

2. Guidance

Prefer standard types; mint vnd.* sparingly when semantics truly differ.
Prefer OpenAPI/JSON Schema for structure over media-type explosion.
Versioning: subtype version or ; version= — pick one convention.
JSON:API allows only ext and profile params — others → 415.
Always set Content-Type; X-Content-Type-Options: nosniff; Vary: Accept when format varies.

3. Quick checklist

Document request/response types.
Accurate Content-Type; nosniff.
406/415 behavior defined.
Consistent MIME versioning scheme if used.
OpenAPI lists allowed types.

See reference.md and examples.md.

Frequently asked questions