菜单
Create platform-native content that resonates with each community's culture. Use when adapting technical content for WeChat, Hacker News, Reddit, Medium, Twitter/X, Dev.to, or LinkedIn. Transforms generic writing into content that feels written BY that community, not AT them.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/shareAI-lab/lab-skills --skill media-writer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Reconstruct and report long-running or multi-turn research, architecture questions, reviews, decisions, completion results, and status as a clear, self-contained brief. Use when a reader must re-enter earlier context, understand the real question and its relationships, distinguish verified facts from judgment and open evidence, or make a decision without reconstructing the work log. Quote the relevant original user wording before substantive analysis, keep one coherent main line, use spatial diagrams when relationships matter, and finish with an explicit decision boundary and practical next step.
Recover and review local human-AI conversations from Claude Code, Codex, opencode, Grok Build, and Cursor. Use when the user wants to revisit, search, extract, summarize, or compare work across Agent session stores, time ranges, projects, or named conversations. Follow the user's requested output; question clustering, problem-space mapping, artifact review, drift analysis, and insights are optional lenses.
Deeply research technical architecture, source code, mechanisms, SDKs, frameworks, project comparisons, and system-design options across repositories, history, official docs, issues, discussions, and high-quality community signals. Use when the user asks for deep research, source-level understanding, architecture comparison, mechanism satisfaction, or evidence for designing a system. Always map the question and obtain confirmation before beginning substantive research; skip for simple factual lookups or straightforward implementation tasks.
基于 SOC 职业分类
| name | media-writer |
| description | Create platform-native content that resonates with each community's culture. Use when adapting technical content for WeChat, Hacker News, Reddit, Medium, Twitter/X, Dev.to, or LinkedIn. Transforms generic writing into content that feels written BY that community, not AT them. |
Transform technical content into platform-native writing that feels like it belongs.
Every platform is a culture, not a format.
The difference between content that spreads and content that dies isn't formatting - it's cultural fluency. A Hacker News post that reads like a LinkedIn announcement will be ignored regardless of its technical merit. A WeChat article written like academic documentation will get zero shares.
Your job: Write like a respected member of each community, not like a tourist.
Before writing for any platform, understand:
CRITICAL: The same insight packaged differently can get 0 engagement or 10,000. The insight doesn't change. The cultural packaging does.
Identify target platform from user input, then load ONLY that guide:
| User says... | Platform | Load | Do NOT Load |
|---|---|---|---|
| "WeChat", "WeChat Official Account" | references/wechat.md | All others | |
| "HN", "Hacker News" | Hacker News | references/hackernews.md | All others |
| "Reddit", "r/", "subreddit" | references/reddit.md | All others | |
| "Medium" | Medium | references/medium.md | All others |
| "Twitter", "X", "thread" | Twitter/X | references/twitter.md | All others |
| "Dev.to", "dev.to" | Dev.to | references/devto.md | All others |
| "LinkedIn", "LI" | references/linkedin.md | All others |
MANDATORY: Read the corresponding platform guide completely before writing. Each guide contains the cultural context and anti-patterns specific to that platform.
These kill content on ANY platform:
Expert content writers understand:
When creating platform-specific content:
Remember: The goal isn't to "post content on Platform X." The goal is to become a valuable voice in that community.