Back to Details

who-is-this

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

who-is-this

who-is-this

Figure out who a person is and whether their story holds.
Read the 
deepapi
skill first. All search and scraping goes through DeepAPI. Never use built-in search, fetch, or a browser.
查明目标人物身份及其自述是否属实。
请先阅读
deepapi
技能文档。所有搜索与抓取操作均需通过DeepAPI完成，禁止使用内置搜索、获取功能或浏览器。

Seed

Seed

Need a person. A name, handle, URL, or profile screenshot is enough.
If missing, ask once. Do not guess a different person.
Verify identity before going deep. Bio, company, location, and photo must match. If two people share the name, stop and ask.
需要目标人物信息。姓名、账号、URL或个人资料截图均可。
若信息缺失，询问用户一次即可，切勿猜测其他人物。
深入调查前需验证身份。个人简介、所属公司、所在地及照片必须匹配。若存在同名人物，需停止操作并询问用户。

Research

Research

Find their X, LinkedIn, and GitHub first (dedicated endpoints, not 
site:
search). Then run these in parallel:
  1. GitHub activity. 
    POST /v1/scrape/github/profile
    with 
    includeRepos: true
    , plus recent PRs (
    POST /v1/scrape/github/search
    , 
    type: "pulls"
    , 
    query: "author:<username>"
    , 
    sort: "updated"
    ).
  2. Last 10 LinkedIn posts. 
    POST /v1/scrape/linkedin/posts
    , 
    maxItems: 10
    . Also scrape the LinkedIn profile if you have the slug.
  3. Deep research. 
    POST /v1/research/deep
    on who they are, what they have actually done, and whether the public story holds.
  4. 50 newest X posts. 
    POST /v1/scrape/twitter/search
    with the handle, 
    sort: "latest"
    , 
    maxItems: 50
    . Also pull 
    POST /v1/scrape/twitter/user
    .
Follow DeepAPI polling. If a platform is missing or private, say so. Do not invent a profile.
首先查找目标人物的X、LinkedIn及GitHub账号（使用专属接口，而非
site:
搜索）。然后并行执行以下操作：
  1. GitHub活动：调用
    POST /v1/scrape/github/profile
    接口，设置
    includeRepos: true
    ，同时获取近期PR（调用
    POST /v1/scrape/github/search
    接口，
    type: "pulls"
    ，
    query: "author:<username>"
    ，
    sort: "updated"
    ）。
  2. 最新10条LinkedIn帖子：调用
    POST /v1/scrape/linkedin/posts
    接口，设置
    maxItems: 10
    。若已知slug，同时抓取LinkedIn个人资料。
  3. 深度调研：调用
    POST /v1/research/deep
    接口，调研目标人物身份、实际经历及其公开自述是否属实。
  4. 最新50条X帖子：使用目标人物账号调用
    POST /v1/scrape/twitter/search
    接口，设置
    sort: "latest"
    ，
    maxItems: 50
    。同时调用
    POST /v1/scrape/twitter/user
    接口获取用户信息。
遵循DeepAPI轮询机制。若某平台无相关信息或为私密状态，需如实说明，切勿编造个人资料。

What to extract

What to extract

Scrape wide, report narrow. From everything you pulled, keep only the 3 facts that explain who this person is. Drop the rest — a full CV is a failure, not thoroughness.
Rules:
  • Real track record beats bio. Jobs, products, exits, code, talks.
  • Self-reported numbers stay labeled "their claim". Verified numbers say "verified".
  • Note what they actually post about only if it changes the verdict.
  • Name the honest archetype: builder, marketer, operator, researcher, grifter, investor, recruiter, hobbyist, etc. Pick the one that is true in practice, not the one in their bio.
Ignore congrats, logo spam, paid "king of X" press, and follower-count flexing.
广泛抓取，精简汇报。从所有抓取内容中，仅保留能说明目标人物身份的3个关键事实，其余内容全部舍弃——完整简历并非详尽，而是失败的汇报。
规则：
  • 实际履历优先于个人简介，重点关注工作经历、产品成果、项目退出、代码贡献及演讲内容。
  • 用户自报数据需标注「自述」，已验证数据标注「已核实」。
  • 仅当目标人物的发帖内容会影响结论时，才需提及。
  • 明确真实身份类型：构建者、营销者、运营者、研究者、骗子、投资者、招聘者、爱好者等。需选择符合实际情况的类型，而非个人简介中的表述。
忽略祝贺类内容、logo刷屏、付费「X领域之王」宣传及粉丝数量炫耀。

Output

Output

Hard cap: 100 words after the header line. Plain English. Short sentences. No tables. No sub-bullets. No tweet dumps. No research narration. No "I found" / "I scraped".
markdown
**Full name** — [@handle](https://x.com/handle) · [LinkedIn](url) · [GitHub](url) · [Site](url)

**Who:** One sentence. Where they are and what they do now.

**Track record:** Max 3 bullets. Only what explains who they are. Dates. Label claims vs verified.

**Verdict:** One line. The archetype, whether the story holds, and why.
Example of the right length (fictional):
markdown
**Jane Doe** — [@janedoe](https://x.com/janedoe) · [LinkedIn](https://linkedin.com/in/janedoe) · [GitHub](https://github.com/janedoe)

**Who:** Berlin solo founder of Acme, an open-source Postgres proxy. Writes 90% of the commits herself.

**Track record:**
- 2024–now: Founder, Acme. 2.1K stars (verified), no funding, no revenue (her own post).
- 2019–2024: Backend engineer at Zalando and N26.
- "50K users" is her claim; nothing backs it.

**Verdict:** Solo builder, not a company yet. Real code, honest numbers, one unproven user claim.
Omit a missing profile link instead of faking it.
Follow-ups: answer in 1–3 sentences. Do not re-run the scrape unless the first pass missed that platform.
严格限制：标题行后内容不超过100词。使用简洁英文，短句表达。禁止使用表格、子项目符号、批量帖子内容、调研叙述及「我发现」/「我抓取」这类表述。
markdown
**Full name** — [@handle](https://x.com/handle) · [LinkedIn](url) · [GitHub](url) · [Site](url)

**Who:** One sentence. Where they are and what they do now.

**Track record:** Max 3 bullets. Only what explains who they are. Dates. Label claims vs verified.

**Verdict:** One line. The archetype, whether the story holds, and why.
Example of the right length (fictional):
markdown
**Jane Doe** — [@janedoe](https://x.com/janedoe) · [LinkedIn](https://linkedin.com/in/janedoe) · [GitHub](https://github.com/janedoe)

**Who:** Berlin solo founder of Acme, an open-source Postgres proxy. Writes 90% of the commits herself.

**Track record:**
- 2024–now: Founder, Acme. 2.1K stars (verified), no funding, no revenue (her own post).
- 2019–2024: Backend engineer at Zalando and N26.
- "50K users" is her claim; nothing backs it.

**Verdict:** Solo builder, not a company yet. Real code, honest numbers, one unproven user claim.
若某平台个人资料链接缺失，直接省略，切勿伪造。
后续跟进：用1-3句话回复。除非首次抓取遗漏了某平台，否则无需重新执行抓取操作。