Find agent skills by outcome

| Xquik docs | docs.xquik.com | Limits

pricing

| API spec | explore MCP tool or docs.xquik.com/api-reference/overview | Endpoint parameters

response shapes |

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

subscription tiers

X Twitter Scraper

Your knowledge of the Xquik API may be outdated. Prefer retrieval from docs — fetch the latest at do...

pricing

description: X (Twitter) data platform skill for AI coding agents. 122 REST API endpoints

2 MCP tools

2. Gather Requirements: Identify and list all necessary requirements

including functional and non-functional aspects.

- APIs and Interfaces: List APIs and interfaces

including usage and examples.

- Scope: Define the scope

including what is included and excluded.

prd-and-technical-documentation-generator

For multi-step tasks

state a brief plan:

- Match existing style

even if you'd do it differently.

- If you notice unrelated dead code

mention it - don't delete it.

- Don't improve adjacent code

comments

Ask yourself: Would a senior engineer say this is overcomplicated? If yes

simplify.

- 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.

Tradeoff: These guidelines bias toward caution over speed. For trivial tasks

use judgment.

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

reviewing

karpathy-guidelines

- Interview type: [e.g.

HR screening / Technical / C-level / panel]