Token导航 LogoToken导航

Agent Skill · 开发

spam-bot-detection-avoidance(避免垃圾邮件机器人检测)

spam-bot-detection-avoidance 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

spam-bot-detection-avoidance 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有未通过项,按安装量在开发类的 21,746 个 Skill 里排第 21,271。

总安装 192周安装 8GitHub Stars 12下载 64核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:spam-bot-detection-avoidance(避免垃圾邮件机器人检测)
来源仓库:https://github.com/louisblythe/sales-skills
仓库路径:skills/spam-bot-detection-avoidance
安装命令:
npx skills add https://github.com/louisblythe/sales-skills --skill spam-bot-detection-avoidance
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/louisblythe/sales-skills --skill spam-bot-detection-avoidance

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

spam-bot-detection-avoidance 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。

通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/spam-bot-detection-avoidance

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

spam-bot-detection-avoidance 怎么安装?

在终端执行 npx skills add https://github.com/louisblythe/sales-skills --skill spam-bot-detection-avoi…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

spam-bot-detection-avoidance 支持哪些 AI 工具?

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

spam-bot-detection-avoidance 需要什么权限?

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

spam-bot-detection-avoidance 是免费的吗?

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

spam-bot-detection-avoidance 用的人多吗?

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

spam-bot-detection-avoidance 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

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

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
spam-bot-detection-avoidance

避免垃圾邮件机器人检测 · 本页

19212只读未明确未通过

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

SKILL.md 原文

Spam/Bot Detection Avoidance

You are an expert in message deliverability for sales automation. Your goal is to help developers create systems that maintain high deliverability while scaling outreach.

Understanding Filtering Systems

Email Spam Filters

What they look for:
- Known spam patterns/phrases
- Sender reputation
- Engagement rates
- Authentication (SPF, DKIM, DMARC)
- Link/image ratios
- HTML quality
- Sending volume patterns

SMS/Carrier Filtering

What triggers filtering:
- Message velocity (too many too fast)
- Identical messages to many recipients
- URL shorteners
- Known spam keywords
- Unregistered sender IDs
- Pattern recognition
- Complaint rates

Email Deliverability

Content Best Practices

DO:
- Write like a human (not a template)
- Use plain text or minimal HTML
- Personalize genuinely
- Include clear sender identity
- Balance text/link ratio
- Use full URLs (not shortened)
- Include unsubscribe option

DON'T:
- Use ALL CAPS
- Multiple exclamation marks!!!
- Spam trigger words excessively
- Image-heavy emails
- Attach files in cold outreach
- Use misleading subject lines
- Hide unsubscribe

Spam Trigger Words

High risk (avoid):
- FREE, FREE!!!
- Act now, Limited time
- Congratulations, You've won
- 100% guaranteed
- No obligation
- Click here, Click below
- Urgent, Important

Moderate risk (use sparingly):
- Discount, Sale, Deal
- Buy, Order, Purchase
- Cash, Money, Income
- Amazing, Incredible
- Opportunity

Subject Line Guidelines

Good:
- "Question about [Company]'s [process]"
- "Following up on [topic]"
- "[Name], quick thought"
- "Idea for [specific challenge]"

Bad:
- "URGENT: Open immediately"
- "You won't believe this offer"
- "Re: Your inquiry" (when no prior contact)
- "[NAME] - TIME SENSITIVE!!!"

Sending Patterns

Warm-up new domains:
Week 1: 20-50 emails/day
Week 2: 50-100 emails/day
Week 3: 100-200 emails/day
Week 4+: Gradually increase

Maintain:
- Consistent daily volume
- No sudden spikes
- Send during business hours
- Mix of recipients (not all cold)

Technical Setup

Required:
- SPF record configured
- DKIM signing enabled
- DMARC policy set
- Custom tracking domain
- Dedicated IP (for volume)

Monitor:
- Bounce rates (<2% target)
- Spam complaints (<0.1%)
- Open rates (benchmark)
- Blacklist status

SMS Deliverability

Number Registration

For business SMS:
- Register 10DLC (US)
- Get proper throughput
- Complete carrier registration
- Maintain good standing

For high volume:
- Use toll-free numbers
- Consider short codes
- Register with carriers

Content Guidelines

DO:
- Identify yourself clearly
- Keep messages concise
- Use natural language
- Vary message content
- Include opt-out method
- Respect quiet hours

DON'T:
- Send identical messages en masse
- Use URL shorteners (bit.ly, etc.)
- Include loan/financial offers
- Send late night (after 9pm)
- Spam emoji 🎉🔥💰
- Use ALL CAPS

Velocity Management

Per number limits:
- New numbers: 1-2 msgs/minute
- Established: 3-5 msgs/minute
- Short codes: Higher volume

Spacing:
- Add random delays (15-60 sec)
- Don't send in bursts
- Spread across time windows

Carrier-Specific Patterns

Carriers filter differently:

AT&T:
- Strict on URL shorteners
- Watches for duplicate content
- Reviews high-volume senders

T-Mobile:
- Aggressive pattern matching
- Requires registration
- Monitors complaint rates

Verizon:
- URL verification
- Content filtering
- Volume thresholds

Message Variation Strategies

Template Spinning

Instead of one message to 1000 people:

Template with variations:
"Hi [First_Name],

[Opener_Variation]

[Value_Prop_Variation]

[CTA_Variation]

[Signature_Variation]"

Combinations create hundreds of unique messages.

Variable Elements

Openers:
- "I noticed [Company] is [observation]."
- "Saw that [Company] recently [event]."
- "Your [role] caught my attention because..."
- "Quick question about [topic]..."

Value props:
- "We help [similar companies] [outcome]."
- "Most [role]s struggle with [problem]. We fix that."
- "Thought of you when [trigger]."

CTAs:
- "Worth a quick chat?"
- "Open to learning more?"
- "Would it make sense to connect?"
- "Interested in seeing how it works?"

Natural Variation

Add human elements:
- Minor typos (occasionally, subtly)
- Varying punctuation
- Different greetings (Hi/Hey/Hello)
- Varying sign-offs
- Different spacing patterns
- Time-of-day references

Engagement Best Practices

Maintain Positive Signals

Email:
- High open rates (aim 20%+)
- Low bounce rates (<2%)
- Few spam reports (<0.1%)
- Replies (good engagement signal)

SMS:
- Response rate
- Low opt-out rate
- No carrier complaints
- Engaged conversations

Handle Negative Signals

Immediately:
- Remove hard bounces
- Honor opt-outs
- Stop messaging non-responders
- Reduce volume if metrics drop

Proactively:
- Clean lists regularly
- Verify emails before sending
- Validate phone numbers
- Remove disengaged contacts

Compliance Integration

Required Elements

Email:
- Physical address
- Unsubscribe link
- Company identification
- Honest subject lines

SMS:
- Business identification
- Opt-out instructions (STOP)
- Consent documentation
- Time restrictions

Consent Management

Track:
- How consent was obtained
- When consent was given
- What they consented to
- Opt-out requests

Respect:
- Opt-out immediately (<24 hours)
- Don't re-add opted-out contacts
- Segment by consent type
- Honor channel preferences

Monitoring & Recovery

Key Metrics to Track

Email:
- Delivery rate (>95% target)
- Inbox placement rate
- Bounce rate (<2%)
- Spam complaint rate (<0.1%)
- Blacklist status

SMS:
- Delivery rate (>97% target)
- Carrier filtering rate
- Opt-out rate
- Response rate

Recovery from Issues

If deliverability drops:

1. Stop sending immediately
2. Identify the cause
3. Fix the issue
4. Clean your list
5. Warm up again slowly
6. Monitor closely

If blacklisted:
1. Identify which blacklist
2. Determine the cause
3. Fix underlying issue
4. Request delisting
5. Prevent recurrence

平台分布

Codex

34.31%
按下载量换算22

Claude

29.78%
按下载量换算19

Cursor

19.44%
按下载量换算12

Gemini CLI

8.66%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills