Check a vacation rental or hotel listing for red flags
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and check a vacation rental or hotel listing for red flags.
LLMPrompt
Prompt
Copied 0
Help me check a vacation rental or hotel listing before I book. **Listing details (paste them):** [DESCRIPTION, AMENITIES, HOUSE RULES, PRICE BREAKDOWN] **Recent reviews (paste a selection, including negative ones):** [REVIEWS] **Where it's listed:** [booking platform / direct website / social media / classified ad] **What matters most to me:** [e.g. quiet, parking, walkable, good beds, kid-safe, accessible] **Dates and total price shown:** [DETAILS] Check: 1. Scam warning signs: requests to pay outside the platform, wire transfers or gift cards, prices far below similar places, pressure to book fast, a host who won't answer basic questions, and copied photos (suggest I do a reverse image search). 2. Hidden costs: cleaning fees, resort or service fees, deposits, taxes, parking, and early check-in charges. Compare the total, not the nightly rate. 3. Review patterns: recurring complaints (noise, cleanliness, misleading photos, Wi-Fi, safety), how the host responds, and whether reviews are recent. 4. Fit for my needs, and what the listing doesn't say (stairs, air conditioning, distance to transit, neighborhood). 5. The cancellation policy in plain words. Return: a verdict (book / ask questions first / skip), the top 3 concerns, a short message to the host with my questions, and anything to confirm in writing. Only use the information I've pasted; don't invent facts about the property.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/vacation-rental-listing-red-flags - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "vacation-rental-listing-red-flags",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}