This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium).

MITAuto-check passed

Install Metamedium

skills CLI
$ npx skills add team-attention/plugins-for-claude-natives --skill metamedium -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install team-attention/plugins-for-claude-natives metamedium --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/team-attention/plugins-for-claude-natives.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/clarify/skills/metamedium .claude/skills/metamedium && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
metamedium
GitHub stars
827
Token cost
~1.4k tokens
SKILL.md length
550 words
Files
2 (incl. references)
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium).

  • Works in 3 steps: Identify and Label → Surface the Fork → Branch
  • Strategizing and the key question is whether to optimize content (what)
  • SKILL.md covers Core Concept, When to Use, Protocol and The Metamedium Question, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Metamedium is an agent skill from team-attention/plugins-for-claude-natives. This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium). Trigger on "내용 vs 형식", "content vs form", "metamedium", "형식을 바꿔볼까", "새로운 포맷", "관점 전환", "perspective shift", "다른 방법 없을까", "같은 방식이 안 먹혀", "diminishing returns". Applies Alan Kay's metamedium concept to surface form-level alternatives. For requirement clarification use vague; for strategy blind spots use unknown.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/alan-kay-quotes.md`).

The repository describes itself as: Claude Code plugins for power users. The licence is MIT.

When your agent uses it

  • Strategizing and the key question is whether to optimize content (what)
  • Change form (how/medium)
  • Content vs form
  • Perspective shift

Example prompts

  • “내용 vs 형식”
  • “content vs form”
  • “metamedium”
  • “/metamedium”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Identify and Label
  2. Surface the Fork
  3. Branch

What it can do on your machine

Read from SKILL.md and the folder at commit fd9c207. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Metamedium loads about 1.4k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 122 tokens; SKILL.md has 550 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~122
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from team-attention/plugins-for-claude-natives at commit fd9c207, republished under its MIT licence (© team-attention). 550 words, ~1,418 tokens.

Download SKILL.mdSave it as .claude/skills/metamedium/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
metamedium
description
This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium). Trigger on "내용 vs 형식", "content vs form", "metamedium", "형식을 바꿔볼까", "새로운 포맷", "관점 전환", "perspective shift", "다른 방법 없을까", "같은 방식이 안 먹혀", "diminishing returns". Applies Alan Kay's metamedium concept to surface form-level alternatives. For requirement clarification use vague; for strategy blind spots use unknown.

Metamedium: Content vs Form Lens

Distinguish content (what is being said/built) from form (the medium/structure it's delivered through) to surface whether the real leverage is in optimizing content or inventing a new form. Based on Alan Kay's metamedium concept.

"A change of perspective is worth 80 IQ points." — Alan Kay

Core Concept

Most people only change content — what they say, write, or build. The real leverage comes from changing form — the medium, format, or structure itself.

Content (what)Form (how/medium)
ExampleWriting a LinkedIn postBuilding a tool that generates posts from client work
ExampleWriting unit tests manuallyBuilding a test generator from type signatures
ExampleGiving a workshopInventing a format where attendees co-create artifacts
LeverageLinear — each piece is one outputExponential — each new form enables infinite content

When to Use

  • Planning a project and unsure whether to optimize the output or the process
  • Stuck optimizing content with diminishing returns
  • Building something and want to check if form-level change would yield more leverage
  • Evaluating whether "more of the same" or "something structurally different" is the right move

For requirement clarification, use the vague skill. For strategy blind spot analysis, use the unknown skill.

Protocol

ALWAYS use the AskUserQuestion tool for the fork question in Phase 2 — never ask content/form choices in plain text.

Phase 1: Identify and Label

Read the user's current work, plan, or task. Classify each component as content or form:

[CONTENT] Writing a blog post about AI consulting
[FORM]    Building a pipeline that turns consulting retros into blog posts
[CONTENT] Deploying a new API endpoint
[FORM]    Building a codegen that auto-generates endpoints from schemas
[CONTENT] Fixing a flaky test
[FORM]    Building a test infrastructure that prevents flaky tests by design

Present the labeling to the user as a brief diagnosis.

Phase 2: Surface the Fork

Use AskUserQuestion to present the content/form choice:

questions:
  - question: "This is currently [CONTENT/FORM]-level work. Where should effort go?"
    header: "Level"
    options:
      - label: "Proceed with content"
        description: "Optimize within the current form — faster, lower risk"
      - label: "Explore form change"
        description: "What if the medium/structure itself changed? Higher leverage"
      - label: "Content now, note form"
        description: "Do the content work, but flag the form opportunity for later"
    multiSelect: false
Phase 3: Branch

If "Proceed with content": Acknowledge and proceed. Include a Form Opportunity note in the output for future reference.

If "Explore form change": Generate 2-3 form alternatives. For each alternative:

  • What the new form looks like concretely
  • What new properties it would have (automatic, repeatable, scalable, composable)
  • Minimum viable version to test the form

If "Content now, note form": Proceed with content work. Append the form opportunity to the output.

Show full SKILL.md (220 more words)Show less
Output

Append to any deliverable or present standalone:

markdown
## Content/Form Analysis

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

### Form Opportunity
| | Detail |
|---|--------|
| **Alternative form** | [what it would look like] |
| **New properties** | [what it enables that current form doesn't] |
| **Minimum test** | [smallest version to validate] |
| **Status** | [exploring / noted for later / not applicable] |

The Metamedium Question

When stuck or when optimizing yields diminishing returns:

"What new form/medium could make this problem disappear?"

Examples:

  • Stuck writing more posts? → A format that turns client work into posts automatically
  • Test coverage plateauing? → A tool that generates tests from type signatures
  • Onboarding too slow? → A self-guided format where the codebase teaches itself

Tetris Test

Change the blocks. Then you realize the original blocks were mathematically calculated.

To truly understand a form, try to change it. The constraints discovered ARE the form's intelligence. Perspective shifts happen not by thinking harder, but by touching the form itself.

Anti-Patterns

  • Treating all work as content optimization when form change is available
  • Building "better content" when the form is the bottleneck
  • Assuming the current medium/format is fixed and only content can vary
  • Confusing incremental content improvement with form invention

Rules

  1. Always label: Tag work as content or form
  2. Content is fine: Not everything needs form change — but always note the option
  3. Form yields power: New form = new medium = exponential leverage
  4. Code is metamedium: The ability to code means the ability to change form
  5. Touch to understand: Change the form to discover why it was designed that way

Additional Resources

For Alan Kay's original ideas and source quotes, see references/alan-kay-quotes.md.

© team-attention, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/clarify/skills/metamedium of team-attention/plugins-for-claude-natives.

  • SKILL.md
  • references/alan-kay-quotes.md

Open the folder on GitHubat commit fd9c207

More from team-attention/plugins-for-claude-natives

All 16 skills in this repo
  • Gmail

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "check email", "read emails", "send email", "reply to email", "search inbox", or manages Gmail.

    827 GitHub stars~967 tokensUpdated 5 mo ago
    Auto-check passed
  • History Insight

    team-attention/plugins-for-claude-natives

    This skill should be used when user wants to access, capture, or reference Claude Code session history.

    827 GitHub stars~834 tokensUpdated 5 mo ago
    Auto-check passed
  • Session Analyzer

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants…

    827 GitHub stars~1.8k tokensUpdated 5 mo ago
    Auto-check passed
  • Youtube Digest

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "유튜브 정리", "영상 요약", "transcript 번역", "YouTube digest", "영상 퀴즈", or provides a YouTube URL for analysis.

    827 GitHub stars~557 tokensUpdated 5 mo ago
    Auto-check passed
  • Tech Decision

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "기술 의사결정", "뭐 쓸지 고민", "A vs B", "비교 분석", "라이브러리 선택", "아키텍처 결정", "어떤 걸 써야 할지", "트레이드오프", "기술 선택", "구현 방식 고민", or needs deep analysis for technical…

    827 GitHub starsUsed in 2 repos~1.2k tokens
    Auto-check passed
  • Fetch Tweet

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "트윗 가져와", "트윗 번역", "X 게시글 읽어줘", "tweet fetch", "트윗 내용", "트윗 원문", or provides an X/Twitter URL (x.com, twitter.com) and wants to read, translate, or…

    827 GitHub stars~518 tokensUpdated 5 mo ago
    Auto-check passed

Questions about Metamedium

What does Metamedium do?

This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium). Metamedium is an agent skill from team-attention/plugins-for-claude-natives. This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium).

When should I use Metamedium?

Metamedium fits situations like: strategizing and the key question is whether to optimize content (what); change form (how/medium); content vs form; perspective shift.

How do I install Metamedium in Claude Code?

Run `npx skills add team-attention/plugins-for-claude-natives --skill metamedium -a claude-code`. Or copy the skill folder (plugins/clarify/skills/metamedium in team-attention/plugins-for-claude-natives) into .claude/skills/metamedium in your project. Claude Code loads it when a task matches its description.

How do I install Metamedium in Codex?

Run `npx skills add team-attention/plugins-for-claude-natives --skill metamedium -a codex`. Or copy the skill folder (plugins/clarify/skills/metamedium in team-attention/plugins-for-claude-natives) into .agents/skills/metamedium in your project. Codex loads it when a task matches its description.

Can I use Metamedium in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add team-attention/plugins-for-claude-natives --skill metamedium -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/metamedium, .gemini/skills/metamedium, .github/skills/metamedium and .opencode/skills/metamedium in your project.

What does Metamedium need to run?

SKILL.md names no scripts, command-line tools or credentials: Metamedium is instructions for the agent only.

Does Metamedium access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Metamedium safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Metamedium use?

Metamedium is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Metamedium use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 875 tokens, read only when the agent opens those files.

Who maintains Metamedium?

team-attention (a GitHub organization) maintains it in team-attention/plugins-for-claude-natives, which has 827 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on April 20, 2026.

Source: team-attention/plugins-for-claude-natives on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.