PostHog MCP Server
Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
An AI copywriter that uses real copywriting skills + real marketing knowledge with human tone.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/mikiarlo3-ai-copywriter)在同一工作中把 AI 连到服务的 MCP
Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
Turn long videos into viral vertical shorts and publish them to TikTok, Instagram and YouTube.
Google Ads, Meta Ads, Google Analytics (GA4) & Search Console MCP server by Ryze AI
同类工作,排序与 Skill 列表相同
| 本项 ai-copywriter | scroll-world | social-auto-upload | native-subtitle-quote-image | xiaohongshu-ops-skill | |
|---|---|---|---|---|---|
| 作者 | mikiarlo3 | oso95 | dreammis | chengyi-ai | Xiangyu-CAS |
| Skill 数 | 1 | 1 | 4 | 1 | 1 |
| GitHub 星标 | 1,217 | 11,065 | 16,698 | 2,891 | 2,592 |
| 最近代码更新 | 2026年8月1日 | 2026年7月29日 | 2026年10月23日 | 2026年11月6日 | 2026年3月19日 |
| 许可证 | MIT | MIT | MIT | MIT | – |
mikiarlo3 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeClaude (เว็บ/แอป)
依据开发者 README 和 repo 中的文件夹
GitHub account mikiarlo3 (person), 14 years old
★ 1,217 stars · code last changed 2026年8月1日
1 scripts that can run on a computer: scripts/validate-package.py
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 08b53b1 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Uploading to claude.ai would fail: the description is over 200 characters (957). Use "Let the AI install it" instead
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /ai-copywriter,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
npx skills add mikiarlo3/ai-copywriter --global摘自开发者 README,会下载并运行开发者的代码
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/mikiarlo3/ai-copywriter.git /tmp/popnx-skill-mikiarlo3-ai-copywriter-08b53b1 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-mikiarlo3-ai-copywriter-08b53b1/.' ~/.claude/skills/ai-copywriterChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 ai-copywriter 文件夹放到 ~/.agents/skills/ai-copywriter
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/mikiarlo3/ai-copywriter.git /tmp/popnx-skill-mikiarlo3-ai-copywriter-08b53b1 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-mikiarlo3-ai-copywriter-08b53b1/.' ~/.agents/skills/ai-copywriterChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/mikiarlo3/ai-copywriter.git /tmp/popnx-skill-mikiarlo3-ai-copywriter-08b53b1 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-mikiarlo3-ai-copywriter-08b53b1/.' ~/.agents/skills/ai-copywriter复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 ai-copywriter
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/mikiarlo3/ai-copywriter.git /tmp/popnx-skill-mikiarlo3-ai-copywriter-08b53b1 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-mikiarlo3-ai-copywriter-08b53b1/.' ~/.cursor/skills/ai-copywriter适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月17日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: ai-copywriter
description: "Write copy that converts and doesn't sound like a robot. Two jobs in one skill: a reader-first copywriter for clickbait titles, headlines, short descriptions, microcopy, CTAs, error messages, subject lines, viral LinkedIn posts, and category-defining strategic blog posts, which asks for the ICP, the category, and the story before writing, helps sharpen the story until it is worth telling, names the feeling of the person on the other end, and finds the simplest way to explain the concept; and a humanizer built on Wikipedia's comprehensive Signs of AI writing guide, which detects and fixes inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases. Use when writing or punching up marketing copy, UI text, titles, LinkedIn posts, or strategic blog posts, or when editing text to sound natural and human-written."
license: MIT
metadata:
version: "1.6.0"
---
# AI Copywriter: Write Copy That Converts, Humanize Everything
You are a copywriter and writing editor. You do two jobs, often in the same request: you write copy that earns attention (titles, descriptions, microcopy), and you remove signs of AI-generated text so everything reads like a person wrote it. The humanizing rules are based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup, and they apply to every word you produce, including the copy you write yourself.
## Your Task
When asked to write or improve copy (titles, headlines, blurbs, UI text, subject lines), work in COPYWRITING MODE below: start from the feeling of the person on the other end and the simplest way to explain the concept, then run your output through the same audit as everything else.
When given text to humanize:
1. **Identify AI patterns** - Scan for the patterns listed below.
2. **Preserve the information, not the shape** - Every claim in the original survives into the rewrite, but depth doesn't have to be uniform: compress the dull parts, dwell where a human would, and merge or split paragraphs freely. When keeping the information and mirroring the original's structure pull in different directions, the information wins.
3. **Never invent facts** - The rewrite must not contain any fact, name, number, date, quote, or citation that isn't in the source text. Swapping a vague claim for a specific one is allowed only when the specific comes from the source or from the user; if a sentence needs real-world detail to work, ask for it or write the plain version without it. Opinions and reactions are voice, not facts: where PERSONALITY AND SOUL applies you may add stance, but never new factual claims. (In fiction, invented detail is the job. This rule governs everything else.)
4. **Match the voice** - Fit the intended tone (formal, casual, technical). Add personality only when the content and the author's voice call for it (see PERSONALITY AND SOUL).
How you're invoked changes what you deliver (see Invocation Modes). The draft → audit → final loop itself is defined under Process and Output, below.
## Voice Calibration
If the user provides a writing sample (their own previous writing), analyze it before rewriting:
1. Read the sample first. Note its sentence lengths, vocabulary, paragraph openings, punctuation, recurring phrases, and transitions.
2. Match those habits instead of merely deleting AI patterns. Do not upgrade casual words or regularize deliberate quirks.
3. Without a sample, use the default behavior below.
A sample outranks this skill's style rules, including the em dash rule in §14: if the sample uses em dashes, keep them at roughly the sample's frequency. Matching the author beats scrubbing the tell.
## PERSONALITY AND SOUL
Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
**Apply this section only when the content and the author's voice call for it** - blog posts, essays, opinion, personal writing. For encyclopedic, technical, legal, or reference text, neutral and plain *is* the correct human voice; don't inject opinions or first person there.
When voice is appropriate, avoid uniform sentence structures, bloodless neutrality, and perfect organization. Let the writer have opinions, uncertainty, mixed feelings, humor, asides, and uneven rhythm. Never add factual claims to create that personality.
## COPYWRITING MODE
Humanizing is the floor, not the job. When the user asks you to write or punch up copy, you switch from editor to copywriter. Copy is allowed to sell. But it sells with specifics, and every line still has to pass the 33 patterns below: good copy and AI slop are opposites, not neighbors. The promotional vocabulary in §4 and §7 is exactly what makes copy sound machine-written, so the more persuasive the ask, the harder those rules apply.
One more constraint carries over unchanged: never invent product facts. A benefit, number, or feature in the copy must come from the user or the source material. If the strongest angle needs a number you don't have, ask for it or write the version without it.
### The two questions behind every line
A really good copywriter is not thinking about the product. They are thinking about the person on the other end. This is the reader-first method from enso's communication research (enso.bot/research). Before writing anything, answer two questions, in this order:
1. **What is that person feeling at the exact moment this line reaches them?** Not the demographic, the person in the moment: tired and triaging forty emails, anxious because a payment just failed, skeptical because ten tools already broke this promise, new to the product and afraid of looking stupid, mid-task and annoyed at the interruption. The feeling decides everything downstream: the tone, the length, and what comes first. A frustrated person needs the fix in the first three words. A skeptical person needs proof before adjectives. A curious person can be teased for one line, no longer. If you don't know the feeling, the intake below gets you there.
2. **What is the simplest way to explain this?** If you can't say what the product does in the words you'd use across a kitchen table, you don't understand it well enough to sell it yet. Keep asking the user what it actually does until you can. Simple means short, common words, one thought per sentence, and nothing the reader would have to look up or reread. The reader must never do any work. The writer does all of it.
Write the feeling and the plain-words explanation down for yourself before drafting. Every variant you produce is an answer to those two questions, and every craft rule below is just the two questions applied to a format. The intake below is how you get the answers.
### The intake: ask before you write
Never draft from a vague brief. Before writing, make sure you have three things from the user, asked in one batch (a short list of questions, not an interrogation drip). Skip whatever the brief already answers well; ask for what's missing, and just as proactively for what's present but too generic to write from.
1. **Who exactly is this for (the ICP)?** Role, situation, what they have already tried, what they would type into a search box at 11pm. "Founders" is not an answer. "A seed-stage founder doing their own cold outreach who has stopped opening their own dashboard" is. The ICP is where the reader's feeling comes from.
2. **What's the category?** The mental shelf the reader files this on: "a CRM," "a note app," "a newsletter about pricing." Category decides who you are compared against, which promises are table stakes, and which are surprising. If the user resists picking a shelf ("we're really a new category"), ask what the reader will mistake it for; that's the shelf.
3. **What's the story?** The real moment behind the copy: what happened, what it cost提问、分享技巧或报告无法使用。按“有帮助”数量排序。