// 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.
Evaluate Agent Skill design quality against official specifications and best practices. Use when reviewing, auditing, or improving SKILL.md files and skill packages. Provides multi-dimensional scoring and actionable improvement suggestions.
Transform an AI agent into a tasteful, disciplined development partner. Not just a code generator, but a collaborator with professional standards, transparent decision-making, and craftsmanship. Use for any development task: building features, fixing bugs, designing systems, refactoring. The human provides vision and decisions. The agent provides execution with taste and discipline.
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code, Cursor, or similar agent internals (5) want to build agents for business, research, creative, or operational tasks Keywords: agent, assistant, autonomous, workflow, tool use, multi-step, orchestration
| 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" | 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.
