content-types

Enumerate and categorize content types with format constraints and platform fit.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/00PZ/oopz-inc --skill content-types
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: content-types
Source: https://github.com/00PZ/oopz-inc/tree/main/companies/shoshin/skills/content-types
Command: npx skills add https://github.com/00PZ/oopz-inc --skill content-types

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enumerate and standardize the domain of content types used across the pipeline to reduce confusion and accelerate content planning.

Core Features & Use Cases

  • Canonical list of content types with definitions, format constraints, and platform fit.
  • Reference for writers, editors, and repurpose engines to ensure consistent outputs across channels.
  • Use Case: A team aligns on types before drafting content, repurposing, or publishing across X, Instagram, and TikTok.

Quick Start

Create a canonical list of content types and map each type to its platform fit for reference in content pipelines.

Frequently Asked Questions about content-types

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize content types for multi-channel publishing?▼

To standardize content types for multi-channel publishing, enumerate all types across your pipeline and document each type's definition, format constraints, and platform fit to guide consistent cross-channel creation.

What is a content architecture style guide for cross-channel platforms?▼

A content architecture style guide for cross-channel platforms is a canonical list of content types with definitions and format constraints that aligns teams before drafting, repurposing, or publishing across X, Instagram, and TikTok.

How do I map content types to platform fit for a repurpose engine?▼

Map content types to platform fit for a repurpose engine by creating a canonical list that describes each type's definition and format constraints, ensuring consistent outputs when repurposing content across different channels.

Does this content management approach require YAML frontmatter?▼

Yes, this content management approach requires YAML frontmatter that includes a name and a description, while the body provides actionable guidance for writers and the repurpose engine to ensure consistent outputs.

Why do I need content standards for a content pipeline?▼

You need content standards for a content pipeline to reduce confusion and accelerate content planning by providing a canonical reference list of content types with definitions, format constraints, and platform fit for writers and editors.