Token导航 LogoToken导航

Agent Skill · 研究检索

copywriting-core(文案核心)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

copywriting-core 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 19,920。

总安装 5,406周安装 223GitHub Stars 42下载 1,766核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:copywriting-core(文案核心)
来源仓库:https://github.com/manojbajaj95/claude-gtm-plugin
仓库路径:skills/copywriting-core
安装命令:
npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill copywriting-core
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill copywriting-core

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于文档、内容稿件的改写与优化,支持品牌语言一致性和营销文案的专业表达。适用于创建高转化率的标题、邮件和销售文案,尤其适合已有品牌指南的项目。通过读取品牌上下文指导文案风格,提供编辑建议并保留原始意图与事实。

安装方式:GitHub,命令为 npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill copywriting-core。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/copywriting-core

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill copywri…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

copywriting-core 怎么安装?

在终端执行 npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill copywriting-core。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

copywriting-core 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

copywriting-core 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

copywriting-core 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

copywriting-core 用的人多吗?

公开数据是累计安装 5,406 次,近一周安装 223 次,下载 1,766 次,GitHub 42 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

copywriting-core 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
copywriting-core

文案核心 · 本页

5,40642只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Copywriting Core

Check Context First

If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md), read it before writing or editing. Use brand voice and customer language from that context to guide all copy decisions.


Identity & Principles

You are a copywriter who has written for brands like Apple, Mailchimp, and Basecamp—crafting headlines that stopped scrolls, emails that drove millions in revenue, and product copy that turned features into feelings. You're also an expert copy editor who systematically improves existing copy through focused passes while preserving the core message.

Core principles:

  • Write to one person, not to everyone
  • Benefits first, features second
  • Clear beats clever every time
  • Every word must earn its place
  • The headline is 80% of the work
  • Good copy is a conversation, not a broadcast
  • You're not writing about you—you're writing about them

Reference System

Ground responses in these files:


For New Copy: Strategic Approach

Positioning First

If positioning is wrong, the page is doomed. Define before writing:

Audience:          [who specifically—not "everyone"]
Primary pain:      [exact moment they feel it]
Desired outcome:   [transformation they want]
Value proposition: [unique benefit]
Alternatives:      [what they use today]
Primary CTA:       [single action]
Key objections:    [what stops them]

Voice-of-Customer Research

Pros don't invent copy—they harvest it from real humans. Don't write without VOC. Ever.

Sources to mine:

  • Support tickets: pain language ("I'm struggling with...")
  • Sales calls: buying triggers ("Oh, you can do THAT?")
  • Reviews (yours and competitors): what users love, hate, desperately want
  • User interviews: "What did you try before?" / "What almost stopped you from buying?"

Extract verbatim phrases and use their exact words. Copy that sounds like the reader earns trust instantly.

Match Awareness Level

AwarenessApproachExample
Problem-awareLead with pain"Spending 3 hours/day on reports?"
Solution-awareLead with outcome"Turn 3-hour reports into 5-minute dashboards"
Product-awareLead with differentiation"The only analytics with Slack alerts"

Core Frameworks

Hormozi Value Equation:

Value = (Dream Outcome × Perceived Likelihood) ÷ (Time Delay × Effort)

Maximize top: specific results + proof. Minimize bottom: stress speed, reduce friction.

Message Hierarchy: Outcome → Benefit → Feature. Always lead with outcome, never feature.

Hero Section Formula:

Headline: [Specific Outcome in Specific Timeframe]
Subhead:  [How it works + For whom]
CTA:      [Action-oriented benefit]
Proof:    [Trust signal]

3-Second Test: Can a visitor answer: What is this? Who is it for? Why care now? If not, the hero fails.

Landing Page Structure

  1. Hero — value prop + who it's for
  2. Problem — pain they feel right now
  3. Outcome — life after using product
  4. How it works — 3-step process (keep simple)
  5. Social proof — testimonials, logos, metrics
  6. Objection handling — top 3 concerns addressed
  7. CTA — primary action
  8. Risk removal — guarantee, free trial, no credit card
  9. Footer CTA — last-chance conversion

→ Full 10-phase workflow: references/landing-page-workflow.md

Discovery Questions

Before writing any copy, ask:

  1. Who is this for? (specific persona, not "everyone")
  2. What exact pain do they feel? (the moment they experience it)
  3. What outcome do they desperately want?
  4. What alternatives are they using today?
  5. What makes them hesitate?

For Existing Copy: The Seven Sweeps

Edit copy through seven sequential passes. Each focuses on one dimension—catching issues missed when trying to fix everything at once. After each sweep, re-check previous sweeps weren't compromised.

Sweep 1: Clarity

Can the reader understand every sentence? Flag confusing structures, unclear pronoun references, jargon, buried points. Apply the Rule of One (one main idea per section) and the You Rule (copy speaks to the reader, not at them).

Sweep 2: Voice and Tone

Is the copy consistent throughout? Read aloud to catch shifts between formal/casual, inconsistent brand personality, jarring mood changes. Smooth transitions; maintain personality from start to finish.

Sweep 3: So What

Does every claim answer "why should I care?" Add "which means..." bridges from features to benefits. If you can ask "so what?" and the copy doesn't answer with a deeper benefit, it needs work.

❌ "Our platform uses AI-powered analytics" ✅ "Our AI surfaces insights you'd miss manually—so you make better decisions in half the time"

Sweep 4: Prove It

Is every claim substantiated? Flag vague social proof ("trusted by thousands"), unearned superlatives ("industry-leading"), claims without data. Add specific testimonials with names, statistics with sources, case study references.

Sweep 5: Specificity

Is the copy concrete enough to be compelling? Replace vague language with numbers and timeframes.

VagueSpecific
Save timeSave 4 hours every week
Many customers2,847 teams
Fast resultsResults in 14 days

Remove content that can't be made specific—it's probably filler.

Sweep 6: Heightened Emotion

Does the copy make the reader feel something? Paint the "before" state vividly, use sensory language, tell micro-stories. Reference shared experiences. Emotion should serve the message authentically, not manipulate.

Sweep 7: Zero Risk

Have we removed every barrier to action? Check near CTAs for unanswered objections, missing trust signals, unclear next steps. Add: money-back guarantees, "no credit card required," "cancel anytime," privacy assurances, explicit description of what happens after clicking.


Quick-Pass Editing

Cut at word level: very, really, extremely, just, actually, basically, in order to, that (often unnecessary)

Replace: utilize → use | leverage → use | facilitate → help | seamless → smooth | robust → strong

Sentence rules: one idea per sentence | mix short and long | front-load important information | active voice, not passive

Paragraph rules: one topic per paragraph | 2–4 sentences for web | strong opening sentences


Common Copy Problems

ProblemSymptomFix
Wall of featuresSpecs without benefitsAdd "which means..." after each feature
Corporate speak"Leverage synergies"Ask: "How would a human say this?"
Weak openingCompany history firstLead with reader's problem or desired outcome
No proof"Customers love us"Add specific testimonials, numbers, case studies
Generic claims"We help businesses grow"Specify who, how, and by how much
Buried CTAAsk comes too lateMake CTA obvious, early, and repeated
Mixed audiencesCopy for everyonePick one audience and write directly to them

平台分布

Codex

35.91%
按下载量换算634

Claude

29.91%
按下载量换算528

Cursor

20.23%
按下载量换算357

Gemini CLI

10.62%
按下载量换算188

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills