Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计提醒

post-engagers岗位参与者

Agent Skill

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

总安装

490

周安装

20

GitHub Stars

93

下载量

157
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/extruct-ai/gtm-skills --skill post-engagers

简介

用于查找、检索和筛选相关信息以支持协作或研究需求。

  • 适合根据关键词或任务场景快速定位候选结果。
  • 可辅助识别相关联系人、资源或技术资料。
  • 安装前建议确认权限范围和维护状态。post-engagers 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 注意是否会触发联网、命令执行或文件读写操作。

SKILL.md

LinkedIn Post Engagers

Turn LinkedIn post engagement into a prospecting list. Extract commenters, reactors, and reposters from any LinkedIn post — then enrich and upload to Extruct for outreach.

Related Skills

post-engagers → email-search → email-generation → campaign-sending

This skill produces a people table. The next step (email-search) gets verified emails, then email-generation drafts personalized outreach.

Extruct API Operations

This skill delegates all Extruct API calls to the extruct-api skill.

For all Extruct API operations, read and follow the instructions in skills/extruct-api/SKILL.md.

Table creation, row uploads, and data fetching are handled by the extruct-api skill. This skill focuses on scraping LinkedIn engagers and preparing the data — the extruct-api skill handles the API execution.

Inputs

InputSourceRequired
LinkedIn post URL(s)User providesyes
Engagement types to scrapeUser choice: comments, reactions, reposts (default: all)no
LinkedIn scraping providerUser choice (see provider list below)yes
Existing people table IDExtruct table to append to (or create new)no

LinkedIn Scraping Providers

This skill does not mandate a specific provider. Ask the user which LinkedIn scraping tool they want to use. Below are known options — the user may have others.

ProviderEngagement typesAuthNotes
Anysite MCPComments, reactions, repostsMCP connectionBuilt into Claude Code via MCP. Tools: get_linkedin_post_comments, get_linkedin_post_reactions, get_linkedin_post_reposts
RapidAPI (LinkedIn scrapers)Comments, reactions, repostsX-RapidAPI-Key headerMultiple scrapers available (e.g. Fresh LinkedIn Profile Data, LinkedIn Bulk Data Scraper). Check endpoint docs per scraper
ApifyComments, reactions, repostsAPIFY_API_TOKENActors: curious_coder/linkedin-post-commentors, supreme_coder/linkedin-post-likers. Run via Apify API
PhantombusterComments, reactionsPHANTOMBUSTER_API_KEYPhantoms: "LinkedIn Post Commenters", "LinkedIn Post Likers"
Custom / self-hostedVariesVariesUser may have their own scraping setup

If the user doesn't know where to start:

  • Anysite MCP is the simplest if they have it connected — no extra credentials needed
  • Apify is a good general choice with pay-per-use pricing
  • RapidAPI has multiple scrapers with free tiers

Workflow

Step 1: Collect post URLs and choose provider

  1. Get the LinkedIn post URL(s) from the user. Accept one or multiple.
  2. Ask which engagement types to scrape: comments, reactions, reposts, or all three.
  3. Ask which LinkedIn scraping provider they want to use (see table above).
  4. If the provider requires credentials, confirm they're available.

Extract the activity URN from each post URL. The numeric ID is typically after activity- or ugcPost- in the URL (e.g. activity:7433261939285385217).

Step 2: Scrape engagers

Use the chosen provider to fetch engagement data. The approach varies by provider:

If using Anysite MCP:

  • Comments: mcp__claude_ai_Anysite__get_linkedin_post_comments with urn: "activity:{id}", count: 1500
  • Reactions: mcp__claude_ai_Anysite__get_linkedin_post_reactions with urn: "activity:{id}", count: 1500
  • Reposts: mcp__claude_ai_Anysite__get_linkedin_post_reposts with urn: "activity:{id}", count: 1500

If using another provider:

  • Read or fetch the provider's API documentation
  • Identify the endpoint, input format, and response structure
  • Implement the scraping calls accordingly

For each engager, extract (field names vary by provider):

{
    "full_name": "...",
    "linkedin_url": "...",        # profile URL
    "headline": "...",            # job title / headline
    "engagement_type": "...",     # comment / reaction / repost
    "post_url": "...",            # which post they engaged with
}

If scraping multiple posts, tag each engager with the post_url they engaged with.

Step 3: Deduplicate and classify

  1. Deduplicate by linkedin_url across all posts and engagement types. If someone both commented and reacted, keep both engagement types as a comma-separated value.
  2. Apply the segment classifier to job titles (first match wins):
PriorityPatternSegment
1`founder\co-founder\ceo\owner`Founders / CEOs
2`cto\vp.*eng\head of eng\director.*eng`Engineering Leadership
3`cmo\vp.*market\head of market\director.*market`Marketing Leadership
4`cro\vp.*sales\head of sales\director.*sales\head of revenue`Sales Leadership
5`director\vp\vice president\head of\chief`Directors / VPs / Heads
6`revops\revenue ops\sales ops\growth ops\gtm ops\gtm eng`RevOps / Growth Ops
7`product manag\head of product\product lead`Product
8`data scien\machine learn\ml eng\ai eng\data eng`Data / ML
9`account exec\sdr\bdr\sales dev\business dev\sales rep`Sales ICs
10`market\content\brand\growth\demand gen\copywrite`Marketing / Content
11`sales\commercial\partnerships\revenue`Sales (General)
12`ai\automat\gpt\llm\agent\no.?code`AI / Automation Builders
13`consult\freelanc\advisor\coach\mentor\agenc`Consultants / Agencies
14`engineer\develop\software\fullstack\backend\frontend`Engineering / Product / Data
(no match)Other
  1. Present a segment breakdown to the user before proceeding:
Engager Summary:
- Total unique engagers: N
- Comments: N | Reactions: N | Reposts: N

Segment Breakdown:
  Founders / CEOs:         N (X%)
  Sales Leadership:        N (X%)
  Marketing Leadership:    N (X%)
  ...
  Other:                   N (X%)
  1. Ask the user: "Want to filter to specific segments before uploading? (e.g. only Founders + Leadership)"

Step 4: Upload to Extruct people table

Create a new Extruct generic table or append to an existing one. Delegate to the extruct-api skill.

If creating a new table:

{
  "name": "{user-provided name or 'Post Engagers - {date}'}",
  "kind": "generic",
  "column_configs": [
    {"kind": "input", "name": "Full Name", "key": "full_name"},
    {"kind": "input", "name": "LinkedIn URL", "key": "linkedin_url"},
    {"kind": "input", "name": "Job Title", "key": "job_title"},
    {"kind": "input", "name": "Segment", "key": "segment"},
    {"kind": "input", "name": "Engagement Type", "key": "engagement_type"},
    {"kind": "input", "name": "Source Post", "key": "source_post"},
    {"kind": "input", "name": "Company", "key": "company"},
    {"kind": "input", "name": "Domain", "key": "domain"}
  ]
}

Upload rows in batches of 50 via the extruct-api skill.

If appending to an existing table:

  • Fetch existing rows to deduplicate against current linkedin_url values
  • Upload only new engagers

Step 5: Review and next steps

Present upload summary:

Upload Complete:
- Engagers uploaded: N
- Table: {table_name}
- URL: https://app.extruct.ai/tables/{table_id}

Segment Breakdown (uploaded):
  Founders / CEOs:     N
  Sales Leadership:    N
  ...

Suggest next steps:

  • "Get emails" → run email-search on the people table to enrich with verified emails
  • "Enrich companies" → run list-enrichment to add company data (industry, size, funding)
  • "Draft outreach" → run email-generation after emails are found
  • "Monitor more posts" → re-run with additional post URLs and deduplicate against this table

Tips

  • Multiple posts = richer list. Scrape 3-5 recent posts from the same account to build a larger pool. Engagers across multiple posts are highly engaged — flag them.
  • Repeat engagers are warmer leads. If someone engaged on 2+ posts, note that in the data — they're more likely to respond to outreach.
  • Filter aggressively. Not all engagers are prospects. Use segment filtering to focus on decision makers and skip students, recruiters, etc.
  • Respect rate limits. LinkedIn scraping providers have varying rate limits. Don't hammer the API — space out requests if scraping many posts.

Output

OutputFormatLocation
People tableExtruct generic tablehttps://app.extruct.ai/tables/{table_id}
Engagers CSVCSV backupclaude-code-gtm/csv/input/{campaign}/post_engagers.csv

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

38.36%
按下载量换算60

Claude

29.03%
按下载量换算46

Cursor

18.8%
按下载量换算30

Gemini CLI

10.68%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

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

来源信息

继续浏览同类 Skills