agentleFS
dotacloverdotaclover/clover-skills/copywriting/SKILL.md

copywriting

Skill0 starsChanged 3 days agoMITView on GitHub

通用对外表达手册。落笔前确定对象、渠道与目标,按商品页、服务页、个人主页、简历、客户沟通、同行交流调整文案;核对品牌brief、事实与授权,区分真实脱敏案例和合成演示资料,禁止虚假业绩与效果承诺。

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use paywalls, popups and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 17 projects that use this

  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 16 projects that use this

  • ukunal91appSkill

    revops

    When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

    Also in 38 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 21 projects that use this

  • timruebenachSkill

    competitor-profiling

    When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitor-alternatives. For sales-specific battle cards, see sales-enablement.

    Also in 25 projects that use this

  • silvainfmSkill

    competitor-alternatives

    When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.

    Also in 33 projects that use this

  • +4 more from Cesarjoquin

The file

Files
SKILL.md

通用表达与对外文案

管怎么说,不管替用户决定品牌、报价、履历或交易渠道。内容创作、设计与开发由本次任务指定的负责人协作,不预设具体团队成员。

0. 四句话定调

  1. 先看人,再说话:客户、同行、招聘方和技术访客需要不同信息。
  2. 具体优于形容:写页面、功能与交付物,不用空泛形容词撑场面。
  3. 可控优于效果:写约定的范围与修改轮次,不承诺排名、客户量、收益或审核结果。
  4. 一致优于漂亮:名称、身份、报价、渠道与交付承诺以用户确认的品牌brief及业务资料为准;冲突交给授权负责人确认。

1. 落笔前确定输入

输入要确认什么
对象对方已有知识、主要疑问与决策条件
渠道用户指定的商品平台、网站、简历、邮件或聊天场景;不默认闲鱼或任何特定渠道
目标了解范围、提交需求、预约沟通或购买,一段话集中一个目标
品牌brief品牌名、主体、代词、语气、禁用表达、联系方式及使用授权
事实资料服务范围、报价来源、交付约定、履历、案例证据及可公开范围

缺少品牌与履历事实就留【待确认】,不从历史项目、个人记忆或示例中补身份。风格可作标明的建议,身份、授权、业绩不能推断。

2. 六个场景

场景目标该说避免
商品页判断是否适合购买交付物、范围、条件、有效报价、排期无证效果承诺、未经核实的站外导流
服务页了解服务与下一步适用对象、范围边界、用户确认的咨询或购买入口擅自指定渠道、隐瞒关键费用
个人主页展示专业能力技术方法、本人贡献、获准公开的项目未授权客户信息、把协作成果全归个人
简历核实经历与岗位匹配真实任职时间、职责、可证成果虚构雇主、夸大职级、把外包写成任职
客户沟通安心并推进下一步先结论和范围,再条件与待确认项催单、绕圈、无依据承诺
同行交流讨论方法与取舍技术事实、限制、经验出处自夸、贬低同行、泄露商业秘密

渠道展示限制、联系方式、价格表和交易入口应按当前平台规则、站点业务资质及用户授权核实;未核实标明,不直接套用历史个人站口径。

3. 同一件事换说法

内容商品页服务页个人主页简历
技术能力用交付物解释说明能力与边界展示技术栈、方法与取舍写职责、方法与可核实成果
报价写有效价格与包含项按用户确认的展示策略无需求不放销售话术通常与岗位无关,不写
经历只写与履约相关事实只写获准公开的背书按授权与保密义务决定按真实履历及投递范围披露

4. 六条底线

  1. 不编业绩:客户名、评价、交付数、成功率、排名、收录、推荐等,必须有证据和公开授权。
  2. 不承诺不可控效果:只写可控动作、文件、范围和已确认安排。
  3. 不默认雇主披露口径:依据真实履历、保密义务和用户授权决定是否点名;匿名不能伪造任职主体。
  4. 不默认个人品牌或组织身份:个人、团队、公司、工作室与职务均按事实和品牌brief使用,不替用户捏造团队或隐藏真实主体。
  5. 价格有来源:读取本次指定的有效报价单或交付约定;路径由实际工作区定位,不假定仓库结构。缺资料留【价格待确认】。
  6. 时间线属实:在职、兼职、外包、自由职业按实际区分;日期不明留待确认,不能用“最近”掩盖冲突。

5. 示例、脱敏与真实案例

类型可用表述条件
真实项目匿名处理本案例基于真实项目,名称与联系方式已匿名处理确有真实来源、授权与匿名处理记录;不得捏造来源
合成演示资料本站为功能与版式演示,名称及数据为合成示例,不代表真实客户或业绩显著标明演示;不伪装成客户案例、交易凭证或证言
获准公开案例本项目展示【本人实际负责部分】证据与公开授权覆盖名称、截图、数据及贡献表述

只有真实资料经过匿名处理才叫脱敏。 不能把“虚构/合成/演示”替换成“脱敏”来暗示不存在的客户来源。演示站的价值在结构、功能和交互,诚实标注不削弱这些价值。

客户问“是否真实案例”时直接回答上述类型;未知则说待核实,不回避、不冒认。只在确实可访问时写“可打开查看”,不能用“真站”混淆真实客户与可运行演示。

6. 数字与事实核对

  • 价格、轮次、数量、周期逐项对应用户提供的有效资料。
  • 有证据且获授权的成果可如实写,禁止虚假业绩、虚构原价和保证结果。
  • 区分用户提供、独立核实和待确认;没有查证不得标“已核实”。
  • 句式例子仅演示表达,不能直接当成用户事实。

7. 风格与替换

见 references/banned-words.md。以语义和上下文审核,不把词表当成法律判定或平台审核保证。删掉空泛形容词时,不得把不确定、失败或未完成改成成功事实。

8. 交稿格式

对象/渠道/目标/品牌brief依据 → 文案正文(注明字段) → 待确认(事实、授权、价格、规则)。

真实材料未齐全的文案标为草稿,不宣称可直接发布。品牌、报价与履历争议交用户指定负责人确认;页面落地交开发负责人;合规问题按适用专业审核流程处理。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.