Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

languagelanguage 搜索

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

847

周安装

36

GitHub Stars

37

下载量

297
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill language

简介

用于辅助测试设计、自动化测试和用例整理,支持回归验证。

  • 适合编写单元测试、端到端测试或根据失败日志定位问题。language 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 使用时应确认项目测试框架、运行命令和夹具数据,避免误改逻辑。
  • 涉及浏览器或外部服务时,需区分本地模拟、测试环境与生产环境。
  • 安装方式:通过 npx 从 GitHub 仓库添加技能。

SKILL.md

Customer Language Mastery

Research how your customers actually talk, then use their exact language across Product and Marketing to create instant resonance.

The Core Principle

First Law of Customer Physics: A customer at rest will remain at rest unless you provide a motivating, attention-grabbing force.

Language is that force. Your words must bypass the customer's natural filters by creating resonance — the "OH YEAH! THAT'S FOR ME!" reaction.

If your language is bland or tries to appeal to everyone, it exerts no gravitational force and gets ignored.

Where Customer Language Applies

DomainExamples
Product UIButton labels, error messages, empty states, onboarding
Feature NamingWhat you call features determines if users understand them
DocumentationGuides, tooltips, help text
Settings/OptionsHow you frame choices affects decisions
NotificationsPush, email, in-app alerts
MarketingLanding pages, emails, ads, social

Conversation Starter

Use AskUserQuestion to gather context:

  1. Who is your target audience? (job title, industry, experience level)
  2. What problem does your product solve?
  3. What copy needs work? (Product UI, landing page, feature naming, etc.)
  4. Do you have existing customer conversations? (support tickets, reviews, interviews)

Part 1: Sales Safari — Finding Watering Holes

A watering hole is anywhere your target audience gathers to discuss problems, share advice, or seek help.

Watering Hole Keywords

Combine audience terms with these keywords to find communities:

CategoryKeywords
Communityforum, community, group, mailing list, chat, Discord, Slack
Help-Seekinghelp, problems, advice, questions, FAQs, support
Learningtutorial, resources, guide, best practices, how to
Evaluationreviews, comparison, best, vs, alternative
Discussiondiscussions, sharing, experiences, stories
SocialTwitter/X chat, Facebook Group, subreddit, LinkedIn Group

Search Patterns

[audience term] + forum
[audience term] + community
[audience term] + "I'm struggling with"
[audience term] + "how do you handle"
[audience term] + site:reddit.com
[audience term] + site:news.ycombinator.com
[problem] + "anyone else"
[problem] + "is it just me"

Platform-Specific Searches

PlatformSearch Pattern
Redditsite:reddit.com [audience] [problem]
Hacker Newssite:news.ycombinator.com [topic]
Stack Overflowsite:stackoverflow.com [technology] [problem]
Product Huntsite:producthunt.com [category] discussions
G2/Capterrasite:g2.com [competitor] reviews
Twitter/X[problem] filter:replies min_faves:10

Part 2: Extracting Customer Language

Once you find watering holes, extract these language patterns:

1. Pain Language

Words and phrases expressing frustration, anxiety, powerlessness, or uncertainty.

Listen for:

  • "I hate when..."
  • "It drives me crazy that..."
  • "I'm so frustrated with..."
  • "Why can't I just..."
  • "I've tried everything but..."
  • "I'm worried about..."
  • "I don't know how to..."

Extract: The exact phrases, not your interpretation.

2. Desire Language

Words expressing what they want but don't have.

Listen for:

  • "I wish..."
  • "If only..."
  • "I just want to..."
  • "It would be amazing if..."
  • "My dream is..."

3. Jargon & Insider Terms

Every audience has vocabulary that signals belonging.

Types of jargon:

  • Technical terms they use (not textbook definitions)
  • Abbreviations unique to their world
  • Slang that identifies insiders
  • Phrases that have specific meaning in context

Why it matters: Using insider language creates instant trust. Wrong language signals "outsider."

4. Recommendation Patterns

How do they give each other advice?

Listen for:

  • "You should try..."
  • "What worked for me was..."
  • "Read this..."
  • "Check out..."
  • "Think about it this way..."

Use these structures in your copy to feel like peer advice, not sales pitch.


Part 3: Language Extraction Template

When researching, fill this out:

## Language Research: [Audience]

### Watering Holes Found
- [Platform]: [Community name] - [Why relevant]
- [Platform]: [Community name] - [Why relevant]

### Pain Phrases (Exact Quotes)
| Quote | Emotion | Frequency |
|-------|---------|-----------|
| "[exact quote]" | frustrated/anxious/desperate | common/rare |

### Desire Phrases (Exact Quotes)
| Quote | What They Want |
|-------|----------------|
| "[exact quote]" | [interpretation] |

### Insider Jargon
| Term | What It Means to Them |
|------|----------------------|
| [term] | [contextual meaning] |

### Recommendation Patterns
- "[How they give advice]"
- "[Structure they use]"

### Words They NEVER Use
- [terms that signal outsider]

Part 4: Worldview Resonance

Effective language expresses a worldview — shared beliefs and values.

Take a Stand

Polarizing language attracts the right people and repels the wrong ones.

Weak (appeals to everyone, resonates with no one):

"A better way to manage projects"

Strong (takes a stand):

"Project management for teams who hate project management"

Worldview Crossover

Find the overlap between YOUR worldview and your CUSTOMER'S worldview:

Your Beliefs          Customer's Beliefs
     \                    /
      \                  /
       \                /
        [CROSSOVER ZONE]
        This is where your
        messaging lives

Positioning Through Language

Audience TypeLanguage Signals
Professional/Enterprise"controls", "governance", "compliance", "scalable"
Startup/Indie"ship fast", "no bloat", "just works", "for builders"
Creative"beautiful", "craft", "artisan", "curated"
Technical"API-first", "extensible", "open source", "self-hosted"
Budget-conscious"affordable", "free tier", "no hidden fees", "transparent"

Part 5: The "OH YEAH!" Test

Before shipping any copy, run this test:

Does your language...

Criterion✓/✗
Use words your customers actually use?
Express a worldview they share?
Address a pain they've expressed (in their words)?
Feel like advice from a peer, not a pitch?
Repel people who aren't your customer?
Make the right person say "That's for me!"?

Red Flags

  • ❌ Afraid of offending anyone → too weak
  • ❌ Using industry jargon they don't use → outsider signal
  • ❌ Describing features, not outcomes → no resonance
  • ❌ Corporate-speak when audience is casual → tone mismatch
  • ❌ Casual when audience is professional → credibility loss

Part 6: Application Examples

Product UI

Before (generic):

Error: Invalid input

After (using customer language):

Hmm, that doesn't look right. Double-check the format?

Before (feature-focused):

Enable notifications

After (outcome-focused, using desire language):

Never miss an update from your team

Feature Naming

Before (technical):

Automated Workflow Engine

After (using customer problem language):

"Set it and forget it" automation

Empty States

Before (bland):

No projects yet

After (using desire language):

Ready to ship something? Create your first project.

Error Messages

Before (blame user):

Invalid email address

After (helpful, peer tone):

That email looks incomplete — missing something after the @?

Landing Page Headline

Before (feature-focused):

All-in-one project management platform

After (pain language + worldview):

Finally, project management that doesn't feel like a second job

Output Format

When applying this skill, deliver:

## Customer Language Analysis

### Research Summary
- **Watering holes searched:** [list]
- **Quotes extracted:** [count]
- **Key insight:** [one sentence]

### Language Patterns Discovered

**Pain phrases:**
- "[exact quote]" → Use for: [where to apply]

**Desire phrases:**
- "[exact quote]" → Use for: [where to apply]

**Insider jargon:**
- [term]: [meaning] → Use for: [where to apply]

### Recommended Copy Changes

| Location | Before | After | Why |
|----------|--------|-------|-----|
| [UI element/page] | [current] | [recommended] | [language pattern used] |

### "OH YEAH!" Test Results
[Run the test on recommended copy]

When to Use This vs Other Skills

Use language when...Use other skills when...
Researching how customers talkNeed emotional trigger words (power-words)
Writing product UI copyNeed full landing page (landing-page-builder)
Naming featuresNeed brand names (namer agent)
Improving resonanceNeed SEO optimization (seo-audit)
Extracting voice of customerNeed to find communities (customer-discovery)

What This Skill Does NOT Do

  • Replace user research interviews
  • Guarantee conversion (testing required)
  • Provide word lists (see power-words for that)
  • Write full marketing campaigns

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.42%
按下载量换算105

Claude

32.87%
按下载量换算98

Cursor

17.87%
按下载量换算53

Gemini CLI

9.58%
按下载量换算28

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills