october-academy/metamedium
plugins/clarify/skills/metamedium/SKILL.md
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.
content-media
Updated Jul 11, 2026
$ install --global
skillsauthnpx skillsauth add october-academy/agent-plugins metamediumInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 11, 2026, 7:49 AM158.9s2 files scanned
SKILL.md
- name:
- metamedium
- description:
- 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.
- user-invocable:
- true
- argument-hint:
- [work-or-plan]
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 Opportunitynote
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
Related Skills
october-academy/interview
development
VerifiedTrustedCommunity
This skill should be used when the user's request or requirement is ambiguous and needs an iterative interview to become actionable — vague feature requests ("add notifications"), incomplete bug reports ("the export is broken"), underspecified tasks and migrations ("make it faster", "convert this to TypeScript"), or any build request the user hasn't fully thought through. Trigger on "clarify requirements", "refine requirements", "요구사항 명확히", "요구사항 정리", "요구사항 인터뷰", "인터뷰해줘", "interview me", "ask me questions before building", "make this clearer", "spec this out", "scope this", "/clarify:interview". Turns vague inputs into concrete specs and surfaces considerations the user hasn't thought of. For strategy blind spots use unknown; for content-vs-form reframing use metamedium.
SKILL.mdUpdated Jul 11, 2026
october-academy/blog-humanize-fast
data-ai
VerifiedTrustedCommunity
블로그 초안/최종 원고를 빠르게 보수 윤문하는 병렬 strict 워크플로. humanize-korean --strict의 검증 분리(fidelity, naturalness, 잔존 S1/S2 탐지)는 유지하면서 청크 병렬화로 속도를 줄인다. 트리거: "블로그 최종 윤문", "윤문 빠르게", "blog-humanize-fast", "humanize-korean strict 너무 느려", "병렬 strict 윤문", "AI 티 줄이되 의미는 건드리지 마", "최종 교열 후 윤문". 아닌 것(negative scope): 초안 대필·내용 추가/삭제·사실 수정이 아니다 — 문체·리듬·표현만 의미 불변으로 손본다. 라우팅: 새 글 집필은 blog-prep, 더 깊은 검증·낮은 등급 재검증이 필요하면 humanize-korean --strict, 맞춤법·오탈자만이면 직접 교정으로 보낸다.
SKILL.mdUpdated Jul 7, 2026
october-academy/trend-scout
tools
VerifiedTrustedCommunity
Reddit, HN, GitHub, RSS, npm, Bluesky, Mastodon, 한국 커뮤니티까지 어제~오늘 뜨는 빌더/AI/오픈소스 시그널을 수집하고 Threads 포스트용으로 큐레이션. GitHub는 gh CLI 우선, 없으면 공개 REST API로 폴백. '지금 뜨는 것'을 넓게 스캔해 후보를 뽑는 큐레이션 전용 스킬이다. 특정 주제를 다각도로 파고드는 심층 리서치는 이 스킬이 아니라 deep-research(다중 소스 fact-check 리포트)·last30days(한 주제의 최근 30일 여론) 영역이다. 트리거: '트렌드', '인기글', 'trend scout', '쓰레드 리서치', 'threads 소재', '오늘 뭐 올리지', '콘텐츠 소재', 'reddit 인기글', 'HN 인기글', '깃허브 트렌드', '오픈소스 소재', '해커뉴스', '트렌드 스카우트', 'github trending', 'what is hot on hacker news', 'open source radar', 'reddit trending', 'trending packages', 'daily tech digest', 'tech news today', 'developer trends'. /trend-scout로 실행.
SKILL.mdUpdated Jun 17, 2026
october-academy/cp
tools
VerifiedTrustedCommunity
Commit and push in one step. Use when user says "/cp", "commit and push", "커밋하고 푸시", "커밋 푸시", "변경사항 올려줘", or wants to stage, commit, and push changes in a single action. Optionally accepts a commit message as argument. Not for creating, reviewing, or merging pull requests — commit and push only.
SKILL.mdUpdated Jun 17, 2026