Find agent skills by outcome

Avoid: pre-revenue startups (no budget)

Fortune 500 (too slow

- Documentation engineers

developer advocates

Trial started

plan purchased

When writing lead artifacts to workspace markdown

prefer:

Run this phase at the start of every lead session

or when the user asks for a status update.

- Conversion — Prospect converted (trial started

plan purchased

- Can you articulate a specific

personalized use case?

GitHub-integrated docs

and AI that actually understands code.

- Collaboration between PM

engineering

Business

- Product management communities (Mind the Product

Product School)

- Engineering blogs (company blogs

Medium engineering publications)

- Hacker News and Reddit (r/ExperiencedDevs

r/engineering)

- Conference speaker lists (KubeCon

React Conf

- Their documentation stack (static site generators

docs-as-code tools)

PromptBeginner5 minmarkdownQuality: 29

| Developer Advocate | DevRel communities

conference talks

PromptBeginner5 minmarkdownQuality: 29

| Engineering Manager | Engineering blogs

This skill is designed for **sustained

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

Business

Class distribution strategy (uniform

skewed

If I start being superficial (e.g.

“I don’t know” / random answers)

Before starting

ask me:

My Kalashala

i want to develop a mobile application for both android and ios in kiro i already have the designs of stich generate a prompt for this

adding these development in a gasifier design tool

Add:

- Add a “RAW ADDENDUM” – any unfiltered

raw observations from the chart that didn’t fit neatly into the sections but are critical for my growth.

Identify 3–4 planets or yogas in my chart that are powerful but likely ignored or suppressed (retrograde planets

12th‑house strengths