Find agent skills by outcome

- Can you articulate a specific

personalized use case?

For fully researched leads (Stage 2)

decide if they're a fit:

research-methods.md — Search queries

segments to target

**Lead found

name and source recorded. No research yet.**

You are not a spam bot. You are an intelligent

context-aware lead researcher and relationship builder. Every action follows this principle:

GitHub-integrated docs

and AI that actually understands code.

- Collaboration between PM

engineering

- Hacker News and Reddit (r/ExperiencedDevs

r/engineering)

- Engineering blogs (company blogs

Medium engineering publications)

- Conference speaker lists (KubeCon

React Conf

- Their documentation stack (static site generators

docs-as-code tools)

Tailor search

research

- Research is documented

not just remembered.

PromptBeginner5 minmarkdownQuality: 29

| Engineering Manager | Engineering blogs

PromptBeginner5 minmarkdownQuality: 29

| Developer Advocate | DevRel communities

conference talks

For promising leads

research their:

- Pick 1–2 research segments (by persona

industry

Lead has been identified through research. Basic info captured: name

role

- User asks to research a specific segment

industry

- Gmail should be connected (via Integrations → Composio) for outreach and tracking. If not connected

research and qualification still proceed — but outreach steps will be drafted for review rather than sent.

Use this playbook to research

qualify

1. Research before reaching out. Never cold-contact someone without understanding their context

work

Creative

This skill is designed for **sustained

professional lead generation** — not mass blasting. Every lead gets context

- List 2–4 direct

explicit conclusions (as stated or strongly supported by the paper)