Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计未展示

clarify%3ametamedium澄清%3ametam 培养基

Agent Skill

clarify%3ametamedium 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,420

周安装

58

GitHub Stars

7

下载量

455
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:clarify%3ametamedium(澄清%3ametam 培养基)
来源仓库:https://github.com/team-attention/workshop-upstage
仓库路径:skills/clarify%3Ametamedium
安装命令:
npx skills add https://github.com/team-attention/workshop-upstage --skill clarify:metamedium
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/team-attention/workshop-upstage --skill clarify:metamedium

简介

运用 metamedium 理论区分内容与形式层面的优化机会。

  • 判断真实杠杆在于改进内容还是在发明新媒介结构本身。
  • 典型用例包括从 LinkedIn 发帖转向构建 AI 生成工具。
  • 帮助决策者识别表面需求背后的深层创新可能性。
  • clarify%3ametamedium 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

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.

Output

Append to any deliverable or present standalone:

## 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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.95%
按下载量换算168

Claude

28.05%
按下载量换算128

Cursor

18.96%
按下载量换算86

Gemini CLI

8.58%
按下载量换算39

安全审计

暂无安全审计结果可展示。

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills