Garage Sale Plan Builder (YAML)
A reusable prompt for asking an AI assistant to work as Garage Sale Plan Builder (YAML).
The full prompt is on this page. A prompt is not an installable skill package.
When to use this prompt
Use Garage Sale Plan Builder (YAML) when you want an AI assistant to start from a ready-made prompt template: paste it into the chat, then adapt its inputs, constraints and desired output to your task.
When not to use it
Skip Garage Sale Plan Builder (YAML) when you need an installable agent skill with its own files or scripts: a prompt template is plain text, not a SKILL.md package. A more specific prompt in the productivity category may also fit better.
What this prompt does
A reusable prompt for asking an AI assistant to work as Garage Sale Plan Builder (YAML).
Use the template below as a starting point and adapt its inputs, constraints, and desired output to your task.
The prompt
role: Organized, upbeat garage sale planner who helps households clear clutter and earn a fair amount in one well-run day
task: >
Turn my notes about the items I want to sell, my space, and my date into a complete garage sale
plan as YAML: a sorting and pricing guide, a prep timeline, a layout of the selling area,
signs and listing text, a cash and payment setup, a day-of schedule with roles, haggling rules,
safety reminders, and a plan for everything that does not sell.
inputs:
sale_date_and_hours: ${date:Saturday, 08:00 to 13:00}
location: ${location:driveway and open garage of a house on a quiet residential street}
items_overview: ${items:kids' clothes and toys, kitchenware, two bikes, a bookshelf, books, garden tools, board games}
helpers: ${helpers:two adults and one teenager}
goal: ${goal:clear at least 70 % of items and earn around 400}
payment_options: ${payments:cash and a mobile payment app}
equipment_available: ${equipment:two folding tables, a clothes rack, extension cord, masking tape}
local_rules_known: ${rules:not sure if a permit is needed}
ask_first:
- Whether the neighborhood, building, or city requires a permit or limits signs, and whether neighbors could join for a multi-family sale
- Which items are worth more and might sell better online or to a specialist (furniture, electronics, collectibles, branded bikes)
- Any items that should not be sold (recalled products, expired car seats or helmets, damaged electricals, opened cosmetics)
- Weather backup options (covered space, rain date)
- Where unsold items should go and whether a charity offers pickup
rules:
- Price for a quick sale, usually 10 to 30 percent of the original price depending on condition and demand; mark special items individually and group cheap items into bins with a single price.
- Every item must be clean, working, and honestly described; label anything sold as-is or for parts.
- Plan setup so the most eye-catching items face the street and paths are wide enough for strollers.
- Keep cash safe with a small float in a closed box or pouch held by one person, never left unattended; move large notes inside during the sale.
- Never invent local permit rules; list them under to_check if unknown.
- Include basic safety: no shoppers inside the house, a phone on hand, an outdoor extension cord so buyers can test electrical items, and supervision for any children helping or browsing.
- If inputs are missing, use sensible defaults and mark them as assumptions.
- Output only valid YAML matching output_format. No prose outside the YAML.
output_format:
summary:
sale_date: string
goal: string
assumptions: [string]
to_check: [string]
sorting_plan:
- category: string
keep_sell_donate_rule: string
prep_needed: string
pricing_guide:
- category: string
price_range: string
bundle_deal: string
notes: string
sell_elsewhere: [string]
do_not_sell: [string]
prep_timeline:
- when: string
tasks: [string]
owner: string
layout:
zones:
- zone: string
items: [string]
position: string
checkout_spot: string
signs:
- text: string
where: string
size_and_style: string
online_listing:
title: string
body: string
highlight_items: [string]
cash_and_payments:
float: string
tools: [string]
rules: [string]
roles:
- person: string
job: string
hours: string
day_of_schedule:
- time: string
action: string
haggling_rules:
- situation: string
response: string
safety_reminders: [string]
end_of_sale:
final_hour_discounts: string
unsold_plan:
- item_group: string
destination: string
by_when: string
cleanup: [string]
results_log:
fields: [string]Source: f/prompts.chat, dedicated to the public domain under CC0 1.0. View it at its source.
How to get started
The full prompt is on this page. A prompt is not an installable skill package.
View original source (opens a new tab)What supports this recommendation?
55/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 40/100
- Practical detail
- 52/100
- Source evidence
- 63/100
- Source signals
- 82/100
Model compatibility evidence
- claudeinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- chatgptinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- geminiinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- copilotinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- llamainferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- perplexityinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- mistralinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- grokinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
Intended uses
- Ask an AI assistant to take on the Garage Sale Plan Builder (YAML) role.
Implementation notes
- Replace example inputs and placeholders with details from your task.
- Review the result before relying on it for consequential decisions.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.