Find agent skills by outcome

setting_details: A calm lakeside on a misty day in autumn. The shoreline is composed of small rocks

and vibrant autumn foliage grows along the bank. In the distance

framing: The composition is adapted to a 1:1 square format

keeping the main visual weight of the trees on the right

Productivity

| [references/mcp-tools.md](references/mcp-tools.md) | Calling MCP tools (selection rules

workflow patterns

Picture

I want you to act like an extraordinary expert fill with wisdom and the best person in the world when generating picture

Serene Autumn Lakeside Illustration

{

Productivity

| [references/workflows.md](references/workflows.md) | Implementing retry logic

cursor pagination

| [references/extractions.md](references/extractions.md) | Running a bulk extraction (tool types

required params

| [references/pricing.md](references/pricing.md) | User asks about costs

pricing comparison

Data

- Private data: Endpoints returning private data (DMs

bookmarks

Coding & Debugging

| [references/api-endpoints.md](references/api-endpoints.md) | Need endpoint parameters

request/response shapes

- Export formats: `csv`

`xlsx`

Coding & Debugging

- X account credentials: `POST /x/accounts` and `POST /x/accounts/{id}/reauth` transmit X account passwords (and optionally TOTP secrets) to Xquik's servers over HTTPS. Credentials are encrypted at rest and never returned in API responses. The agent MUST confirm with the user before calling these endpoints and MUST NOT log

echo

- MCP isolation: The `xquik` MCP tool processes requests server-side on Xquik's infrastructure. It has no access to the agent's local filesystem

environment variables

- Writes: The agent sends content (tweet text

DM text

5. Never auto-retry credential endpoints. If `POST /x/accounts` or `/reauth` fails

report the error and let the user decide whether to retry.

- Reads: The agent sends query parameters (tweet IDs

usernames

Coding & Debugging

All API calls are sent to `https://xquik.com/api/v1` (REST) or `https://xquik.com/mcp` (MCP). Both are operated by Xquik

the same first-party vendor. Data flow:

4. Never reuse credentials across calls. If re-authentication is needed

ask the user to provide credentials again.

2. Never log or echo credentials. Do not include passwords or TOTP secrets in conversation history

summaries

3. Never store credentials locally. Do not write credentials to files

environment variables

Communication

1. Always confirm before sending. Show the user exactly which fields will be transmitted (username

`POST /x/accounts` and `POST /x/accounts/{id}/reauth` are credential proxy endpoints — the agent collects X account credentials from the user and transmits them to Xquik's servers for session establishment. This is inherent to the product's account connection flow (X does not offer a delegated OAuth scope for write actions like tweeting

DMing

- `POST /x/tweets` — show tweet text

media

All write endpoints modify the user's X account or Xquik resources. Before calling any write endpoint

**show the user exactly what will be sent** and wait for explicit approval: