you should redirect the command to a file and read it using proper tools. Put these files in the `temp/` directory. This folder is automatically cleared between prompts

Apr 16, 2026

Productivity

PromptBeginner5 minmarkdown

2. Generate Tasks (e.g.

Reconnaissance

Apr 16, 2026

Productivity

PromptBeginner5 minmarkdown

- Any formula or automation hints (e.g.

Google Sheets formulas

Apr 16, 2026

Productivity

PromptBeginner5 minmarkdown

- Sub-Tasks must be atomic (one owner

one output

Apr 16, 2026

Productivity

PromptBeginner5 minmarkdown

- Decompose into granular

executable **Sub-Tasks**

Apr 16, 2026

Find agent skills by outcome

- Systematic presentation: symptoms first

- Start with a clear

I want you to design

create prompt for audit purpose on password configuartion file for linux

use_case: Travel and tourism promotion

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

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

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

Endpoints that initiate financial transactions require **explicit user confirmation every time**. Never call these automatically

The MCP server at `xquik.com/mcp` is a **first-party service** operated by Xquik — the same vendor

`POST /draws` with `tweetUrl` (required) + optional filters. If creating a draw

If implementing retry logic or cursor pagination

For multi-step tasks

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

2. Communication — clear

1. **Body text first.** Always start with the body font. Set its size (16-20px for web)

- **Sync workflows:** If you touch generated docs/readme/config surfaces

- If you can't finish a task in a single request

- Take the time needed for careful design

- If you are getting truncated or large output from any command

2. Generate Tasks (e.g.

- Any formula or automation hints (e.g.

- Sub-Tasks must be atomic (one owner

- Decompose into granular

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

Endpoints that initiate financial transactions require explicit user confirmation every time. Never call these automatically

The MCP server at `xquik.com/mcp` is a first-party service operated by Xquik — the same vendor

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

1. Body text first. Always start with the body font. Set its size (16-20px for web)

- Sync workflows: If you touch generated docs/readme/config surfaces