How do I install the Metamedium skill?

Run npx skillmds add october-academy/metamedium 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 Metamedium safe to use?

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

Which AI agents work with Metamedium?

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 Metamedium free to use?

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

Who published Metamedium?

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

Metamedium by october-academy — Agent Skill

Name: Metamedium
Rating: 4.2 (5 reviews)
Author: october-academy

Metamedium

This skill should be used when the key question is whether to optimize content (what) or redesign form (how/medium). Trigger on "내용 vs 형식", "content vs form", "metamedium", "형식을 바꿔볼까", "새로운 포맷", "perspective shift", "diminishing returns". For requirement clarification use interview; for strategy blind spots use unknown.

october-academy 2e4c999 2 files · 2.8 KB Updated Sep 9, 2026

File contents

Metamedium: Content vs Form Reframing

Distinguish content (what is produced) from form (the medium/structure that produces or delivers it) to decide where leverage is highest.

When to Use

Output quality improves slowly despite more effort
Repeatedly producing content inside the same format
Deciding between incremental optimization vs structural redesign

For requirement clarification, use interview. For strategy blind spots, use unknown.

Core Idea

Content optimization is usually linear
Form redesign can be multiplicative

Use this question when stuck:

What new form could make this recurring problem disappear?

Protocol

Phase 1: Label

Classify the user's current activities:

[CONTENT] direct outputs (doc, code change, campaign copy)
[FORM] systems/pipelines/templates/tools enabling repeated outputs

Phase 2: Fork (AskUserQuestion required)

Ask user to choose one path using options (on Codex use request_user_input; with no structured-question tool, offer the same options as a numbered plain-text list):

Proceed with content optimization
Explore form redesign
Content now, track form opportunity

Phase 3: Branch

If content:

Proceed and add a Form Opportunity note

If form:

Propose 2-3 alternative forms
For each: structure, new properties, minimum viable test

If hybrid:

Deliver content outcome plus deferred form backlog item

Phase 4: Output

## Content/Form Analysis

**Current work**: [description]
**Classification**: [CONTENT / FORM]

### Form Opportunity
| Field | Detail |
|-------|--------|
| Alternative form | ... |
| New properties | ... |
| Minimum test | ... |
| Status | exploring / later / rejected |

Rules

Always label current work first
Do not force form redesign when costs exceed leverage
If user stays with content, still preserve at least one form option
Prefer testable form changes over abstract ideation

Additional Resources

references/alan-kay-quotes.md

---name: metamediumdescription: This skill should be used when the key question is whether to optimize content (what) or redesign form (how/medium). Trigger on "내용 vs 형식", "content vs form", "metamedium", "형식을 바꿔볼까", "새로운 포맷", "perspective shift", "diminishing returns". For requirement clarification use interview; for strategy blind spots use unknown.--- # Metamedium: Content vs Form Reframing Distinguish **content** (what is produced) from **form** (the medium/structure that produces or delivers it) to decide where leverage is highest. ## When to Use - Output quality improves slowly despite more effort - Repeatedly producing content inside the same format - Deciding between incremental optimization vs structural redesign For requirement clarification, use **interview**. For strategy blind spots, use **unknown**. ## Core Idea - Content optimization is usually linear - Form redesign can be multiplicative Use this question when stuck: `What new form could make this recurring problem disappear?` ## Protocol ### Phase 1: Label Classify the user's current activities: - `[CONTENT]` direct outputs (doc, code change, campaign copy) - `[FORM]` systems/pipelines/templates/tools enabling repeated outputs ### Phase 2: Fork (AskUserQuestion required) Ask user to choose one path using options (on Codex use `request_user_input`; with no structured-question tool, offer the same options as a numbered plain-text list): - Proceed with content optimization - Explore form redesign - Content now, track form opportunity ### Phase 3: Branch If content: - Proceed and add a `Form Opportunity` note If form: - Propose 2-3 alternative forms - For each: structure, new properties, minimum viable test If hybrid: - Deliver content outcome plus deferred form backlog item ### Phase 4: Output ```markdown ## Content/Form Analysis **Current work**: [description] **Classification**: [CONTENT / FORM] ### Form Opportunity | Field | Detail | |-------|--------| | Alternative form | ... | | New properties | ... | | Minimum test | ... | | Status | exploring / later / rejected | ``` ## Rules 1. Always label current work first 2. Do not force form redesign when costs exceed leverage 3. If user stays with content, still preserve at least one form option 4. Prefer testable form changes over abstract ideation ## Additional Resources - `references/alan-kay-quotes.md`

Frequently asked questions