metamedium

Metamedium: Content vs Form Reframing

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "metamedium" with this command: npx skills add october-academy/agent-plugins/october-academy-agent-plugins-metamedium

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 vague. 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:

  • 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

FieldDetail
Alternative form...
New properties...
Minimum test...
Statusexploring / 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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

sync

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

ship

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

interview-spec

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

deploy

No summary provided by upstream source.

Repository SourceNeeds Review