Find agent skills by outcome

Run auditable draws from tweet replies with filters (retweet required

follow check

| 409 | monitoralreadyexists

conflict | Already exists |

| 404 | not_found

usernotfound

| 402 | no_subscription

insufficient_credits

| 403 | monitorlimitreached

accountneedsreauth | Delete resource or re-authenticate |

| 400 | invalid_input

invalid_id

└─ Tweet search (bulk

up to 1K) → tweetsearchextractor

├─ Trending news (7 sources

free) → GET /radar

When this skill and the docs disagree on endpoint parameters

rate limits

| Xquik docs | docs.xquik.com | Limits

pricing

| Billing guide | docs.xquik.com/guides/billing | Credit costs

subscription tiers

X Twitter Scraper

2. Gather Requirements: Identify and list all necessary requirements

including functional and non-functional aspects.

- Scope: Define the scope

including what is included and excluded.

prd-and-technical-documentation-generator

- Match existing style

even if you'd do it differently.

- If multiple interpretations exist

present them - don't pick silently.

- If something is unclear

stop. Name what's confusing. Ask.

- If a simpler approach exists

say so. Push back when warranted.

Behavioral guidelines to reduce common LLM coding mistakes

derived from Andrej Karpathy's observations on LLM coding pitfalls.

- State your assumptions explicitly. If uncertain

ask.

description: Behavioral guidelines to reduce common LLM coding mistakes. Use when writing

reviewing

2. Communication — clear

confident

karpathy-guidelines