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

lead-hand-skill主导手技

Agent Skill

lead-hand-skill 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

745

周安装

32

GitHub Stars

17,127

下载量

261
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/rightnow-ai/openfang --skill lead-hand-skill

简介

用于查找、检索和筛选相关信息。lead-hand-skill 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 适合根据关键词或任务场景快速定位候选结果。
  • 可辅助内容调研、资料收集和线索整理工作。
  • 安装前建议确认是否支持联网及文件读写权限。
  • 注意维护状态,避免依赖已弃用的接口或服务。

SKILL.md

Lead Generation Expert Knowledge

Ideal Customer Profile (ICP) Construction

A good ICP answers these questions:

  1. Industry: What vertical does your ideal customer operate in?
  2. Company size: How many employees? What revenue range?
  3. Geography: Where are they located?
  4. Technology: What tech stack do they use?
  5. Budget signals: Are they funded? Growing? Hiring?
  6. Decision-maker: Who has buying authority? (title, seniority)
  7. Pain points: What problems does your product solve for them?

Company Size Categories

CategoryEmployeesTypical BudgetSales Cycle
Startup1-50$1K-$25K/yr1-4 weeks
SMB50-500$25K-$250K/yr1-3 months
Enterprise500+$250K+/yr3-12 months

Web Research Techniques for Lead Discovery

Search Query Patterns

# Find companies in a vertical
"[industry] companies" site:crunchbase.com
"top [industry] startups [year]"
"[industry] companies [city/region]"

# Find decision-makers
"[title]" "[company]" site:linkedin.com
"[company] team" OR "[company] about us" OR "[company] leadership"

# Growth signals (high-intent leads)
"[company] hiring [role]" — indicates budget and growth
"[company] series [A/B/C]" — recently funded
"[company] expansion" OR "[company] new office"
"[company] product launch [year]"

# Technology signals
"[company] uses [technology]" OR "[company] built with [technology]"
site:stackshare.io "[company]"
site:builtwith.com "[company]"

Source Quality Ranking

  1. Company website (About/Team pages) — most reliable for personnel
  2. Crunchbase — funding, company details, leadership
  3. LinkedIn (public profiles) — titles, tenure, connections
  4. Press releases — announcements, partnerships, funding
  5. Job boards — hiring signals, tech stack requirements
  6. Industry directories — comprehensive company lists
  7. News articles — recent activity, reputation
  8. Social media — engagement, company culture

Lead Enrichment Patterns

Basic Enrichment (always available)

  • Full name (first + last)
  • Job title
  • Company name
  • Company website URL

Standard Enrichment

  • Company employee count (from About page, Crunchbase, or LinkedIn)
  • Company industry classification
  • Company founding year
  • Technology stack (from job postings, StackShare, BuiltWith)
  • Social profiles (LinkedIn URL, Twitter handle)
  • Company description (from meta tags or About page)

Deep Enrichment

  • Recent funding rounds (amount, investors, date)
  • Recent news mentions (last 90 days)
  • Key competitors
  • Estimated revenue range
  • Recent job postings (growth signals)
  • Company blog/content activity (engagement level)
  • Executive team changes

Email Pattern Discovery

Common corporate email formats (try in order):

  1. firstname@company.com (most common for small companies)
  2. firstname.lastname@company.com (most common for larger companies)
  3. first_initial+lastname@company.com (e.g., jsmith@)
  4. firstname+last_initial@company.com (e.g., johns@)

Note: NEVER send unsolicited emails. Email patterns are for reference only.


Lead Scoring Framework

Scoring Rubric (0-100)

ICP Match (30 points max):
  Industry match:     +10
  Company size match: +5
  Geography match:    +5
  Role/title match:   +10

Growth Signals (20 points max):
  Recent funding:     +8
  Actively hiring:    +6
  Product launch:     +3
  Press coverage:     +3

Enrichment Quality (20 points max):
  Email found:        +5
  LinkedIn found:     +5
  Full company data:  +5
  Tech stack known:   +5

Recency (15 points max):
  Active this month:  +15
  Active this quarter:+10
  Active this year:   +5
  No recent activity: +0

Accessibility (15 points max):
  Direct contact:     +15
  Company contact:    +10
  Social only:        +5
  No contact info:    +0

Score Interpretation

ScoreGradeAction
80-100AHot lead — prioritize outreach
60-79BWarm lead — nurture
40-59CCool lead — enrich further
0-39DCold lead — deprioritize

Deduplication Strategies

Matching Algorithm

  1. Exact match: Normalize company name (lowercase, strip Inc/LLC/Ltd) + person name
  2. Fuzzy match: Levenshtein distance < 2 on company name + same person
  3. Domain match: Same company website domain = same company
  4. Cross-source merge: Same person at same company from different sources → merge enrichment data

Normalization Rules

Company name:
  - Strip legal suffixes: Inc, LLC, Ltd, Corp, Co, GmbH, AG, SA
  - Lowercase
  - Remove "The" prefix
  - Collapse whitespace

Person name:
  - Lowercase
  - Remove middle names/initials
  - Handle "Bob" = "Robert", "Mike" = "Michael" (common nicknames)

Output Format Templates

CSV Format

Name,Title,Company,Company URL,LinkedIn,Industry,Size,Score,Discovered,Notes
"Jane Smith","VP Engineering","Acme Corp","https://acme.com","https://linkedin.com/in/janesmith","SaaS","SMB (120 employees)",85,"2025-01-15","Series B funded, hiring 5 engineers"

JSON Format

[
  {
    "name": "Jane Smith",
    "title": "VP Engineering",
    "company": "Acme Corp",
    "company_url": "https://acme.com",
    "linkedin": "https://linkedin.com/in/janesmith",
    "industry": "SaaS",
    "company_size": "SMB",
    "employee_count": 120,
    "score": 85,
    "discovered": "2025-01-15",
    "enrichment": {
      "funding": "Series B, $15M",
      "hiring": true,
      "tech_stack": ["React", "Python", "AWS"],
      "recent_news": "Launched enterprise plan Q4 2024"
    },
    "notes": "Strong ICP match, actively growing"
  }
]

Markdown Table Format

| # | Name | Title | Company | Score | Key Signal |
|---|------|-------|---------|-------|------------|
| 1 | Jane Smith | VP Engineering | Acme Corp | 85 | Series B funded, hiring |
| 2 | John Doe | CTO | Beta Inc | 72 | Product launch Q1 2025 |

Compliance & Ethics

DO

  • Use only publicly available information
  • Respect robots.txt and rate limits
  • Include data provenance (where each piece of info came from)
  • Allow users to export and delete their lead data
  • Clearly mark confidence levels on enriched data

DO NOT

  • Scrape behind login walls or paywalls
  • Fabricate any lead data (even "likely" email addresses without evidence)
  • Store sensitive personal data (SSN, financial info, health data)
  • Send unsolicited communications on behalf of the user
  • Bypass anti-scraping measures (CAPTCHAs, rate limits)
  • Collect data on individuals who have opted out of data collection

Data Retention

  • Keep lead data in local files only — never exfiltrate
  • Mark stale leads (>90 days without activity) for review
  • Provide clear data export in all supported formats

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

34.71%
按下载量换算91

Claude

33.74%
按下载量换算88

Cursor

18.14%
按下载量换算47

Gemini CLI

9.23%
按下载量换算24

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills