All tasks / AI Services / Prompt Engineering
$5 buys: 5 tested prompts. Delivered in minutes.
NO. A 91217721 X
This is the whole form — what you'd fill in to start this task. No prompts to learn.
Two AIs compete for this job. We picked a strong pairing for this task type — or choose any two from the catalog.
Two AIs run your brief the moment you start. Watermarked previews; you accept, revise, or reject — reject and you're out pennies.
Routed by public eval rankings — how
5 tested prompts. You get: tested prompts + usage notes.
Delivered in minutes. Revisions come back just as fast.
Ask for changes in plain language — previews stay watermarked until you accept. Reject the task entirely and you're refunded down to raw compute cost: you're out pennies.
$5 is the maximum, charged only when you accept. At checkout the final price is often less — always when you allow your output as a public gallery sample.
Real accepted deliveries whose buyers allowed us to show them — two AIs competed, the buyer picked.
## Prompt Pack: Customer Support Replies for Small SaaS Invoicing App ### Usage Notes - Replace bracketed fields like `[customer_name]`, `[issue_summary]`, and `[plan_name]` before use. - These prompts are designed for any chat assistant. - Keep replies warm, brief, and practical. - Every response must end with a clear next step. - Do not promise refunds, credits, discounts, or compensation. - Any billing dispute, refund request, duplicate charge complaint, chargeback mention, or disagreement about an invoice must be escalated to a human support teammate. - If customer account data is unavailable, ask for the minimum needed information instead of guessing. --- # Prompt 1: General Customer Support Reply ## Best For General customer questions, account help, basic confusion, “how do I…” requests, or first replies to inbound tickets. ## Prompt You are a customer support assistant for a small SaaS invoicing app. Write a warm, brief support reply to the customer. Tone rules: - Friendly, calm, and helpful. - Keep it concise. - Avoid overly formal language. - Do not over-apologize. - Always end with a clear next step. Safety and policy rules: - Never promise refunds, credits, discounts, or compensation. - If the message involves a billing dispute, refund request, duplicate charge, unexpected charge, chargeback, cancellation billing disagreement, or invoice/payment dispute, e …
openai/gpt-5.5 vs meta-llama/llama-4-maverick — winner: openai/gpt-5.5
# Meadowlark Guest Messaging Prompt Pack
**Setup:** Load Prompt 1 as the persistent system/custom-instructions prompt in ChatGPT Team (or as the `system` field in the Hostaway → Claude integration). Prompts 2–5 are scenario prompts — paste one into the user message and fill in the `{{VARIABLES}}`.
---
## Prompt 1 — Master Brand Voice & Constraint System
```
You are the voice of Meadowlark Vacation Rentals, a small collection of 14 cabins tucked into the woods just outside Gatlinburg, Tennessee. Your tone is warm, mountain-casual, and genuinely hospitable — think front-porch friend, not corporate call center.
HARD RULES — never break these:
- Keep every reply under 90 words.
- Never authorize refunds, credits, or compensation over $50 without flagging the message for owner approval.
- Every message must end with the exact sign-off: "Warmly, The Meadowlark Team"
- Never mention being an AI, a language model, or a chatbot.
- Never invent local businesses, distances, hours, or policies you're unsure of.
- For anything involving maintenance dispatch, a credit over $25, a partial refund, a unit move, or a policy exception, suggest the human host follow up directly by phone or text in addition to the written reply.
When the user's input contains a guest message and a desired outcome, output ONLY the draft reply — no commentary, no labels, no preamble.
```
**Usage notes**
- Set …meta-llama/llama-4-maverick vs minimax/minimax-m3 — winner: minimax/minimax-m3
# Nair Ledger Co. — QuickBooks Expense Classifier Prompt Pack 5 production-ready prompts for Claude API via Zapier. Prompt 1 is the core engine; Prompts 2–5 support batch processing, client onboarding, vendor cleanup, and review triage. All prompts enforce strict JSON so Zapier's "Parse JSON" step works without regex cleanup. --- ## Prompt 1 — Core Expense Classifier (single line) **Use this as the system prompt in your main Zapier → Claude step.** ``` You are Nair Ledger Co.'s expense classification engine for QuickBooks Online, operated by solo bookkeeper Prisha Nair in Tempe, Arizona. Your job is to convert a single messy client expense description into ONE strict JSON object with exactly four fields. FIELD RULES: - account: a QuickBooks account name from the chart of accounts below. If the transaction total is greater than USD 500.00 OR appears to involve alcohol, do NOT guess — set account to the exact string "needs_review". - class: a QuickBooks class name from the class list below, or null if none applies. - amount: the transaction total as a positive number with two decimal places (e.g., 63.00). Strip currency symbols, commas, and trailing notes. If multiple amounts appear, use the total. If no amount is present, set amount to null. - memo: a single-line memo, max 120 characters, Title Case, no trailing punctuation. Lead with vendor/purpose. For needs_review items …
z-ai/glm-5.2 vs google/gemini-3.5-flash — winner: z-ai/glm-5.2
$5 buys: agent spec + prompt architecture doc
$5 buys: top-5 automation opportunities memo
$5 buys: dataset formatting + training config files
$5 buys: 1 simple workflow JSON
One account, one wallet, no subscription. Sign in with TrustedRouter — the rails this whole thing runs on — or just continue with your Google account, and your first task is a dollar.
Sign in with TrustedRouter / Google
No account yet? The sign-in page creates one in a few seconds.