From Airtasker
Post a task on Airtasker by guiding the user through a structured conversation to capture job details, location, timing, and budget, then submitting via the Airtasker MCP server. Use when asked to post a task, create a task, or hire someone on Airtasker. Prerequisites: Airtasker account, payment method configured, and MCP server authenticated at mcp.airtasker.com/mcp.
How this skill is triggered — by the user, by Claude, or both
Slash command
/airtasker:post-task [optional: brief task description][optional: brief task description]sonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide the user through a structured 4-step conversation to capture everything
Guide the user through a structured 4-step conversation to capture everything
needed for a well-described Airtasker task, then post it via post_task.
The more detail in the description, the better quality offers the user will receive. Help them be thorough.
Ask one question at a time throughout the entire flow. Wait for the user's answer before asking the next question. Never batch or combine questions.
If $ARGUMENTS was provided, present it back as a starting point and ask them
to confirm or expand on it. Otherwise, ask what they need done. Once you have
the description, ask when they need it (flexible / by a certain date / on a
specific date) as a separate follow-up.
Record the raw description — it will be shaped into a proper title and
description later. Record the timing preference for date_type and
timeless_date mapping:
| User says | date_type | timeless_date needed? |
|---|---|---|
| "Anytime / flexible" | flexible | No |
| "By [date]" | before_date | Yes |
| "On [date]" | on_date | Yes |
Ask where they need the job done. If their location is already known from context, present it and ask them to confirm or correct it.
location_type = remote and
skip lat/lng entirely.Once you have the suburb name, use your geographic knowledge to determine the
centroid latitude and longitude for that suburb. Do not ask the user for
coordinates — derive them yourself. Set display_name to the suburb name.
Detect whether this is a Moving, Cleaning, or Gardening task based on the description:
Follow the matching sub-flow below.
If none of the above match, think about what a professional doing this job would need to know before agreeing to a price. Ask 2–4 targeted questions — things like property size, materials needed, accessibility, specific requirements, or anything that would affect scope or effort. Use the answers to enrich the task description.
Ask one question at a time. Wait for the user's answer before asking the next question. Do not combine or batch questions.
Use the pick-up suburb centroid as the location_type (in_person) for the task.
Construct the description using this template:
{user's item description}
Pickup Location: {pickup suburb}
Drop-off Location: {drop-off suburb}
Removals size: {A few items / Apartment / House}
Stairs: {None / At pickup / At drop-off / At both locations}
Ask one question at a time. Wait for the user's answer before asking the next question. Do not combine or batch questions.
Construct the description using this template:
{user's additional details}
Type of clean: {Regular / End of lease}
Number of bedrooms: {count}
Number of bathrooms: {count}
Equipment and supplies: {Cleaner to bring / User will provide}
Ask one question at a time. Wait for the user's answer before asking the next question. Do not combine or batch questions.
Services needed (multiple can be selected):
Garden size — which best describes the area?
If the task location is in the US, use these options:
Otherwise:
Green waste bin — do they have one available?
Additional details — any specific areas or tasks to describe?
Construct the description using this template:
{user's additional details}
Type of gardening: {comma-separated list of selected services}
Size of garden: {Small / Medium / Large / Extra large}
Has green waste bin: {Yes / No}
Ask how much they want to offer as a budget. Clarify it must be a whole dollar amount (no cents). Record it as an integer.
Before calling any tools, present a summary of everything collected:
Ask the user to confirm or make any corrections.
Once confirmed, call post_task with:
| Field | Value |
|---|---|
title | Concise action phrase (e.g. "Help moving a 2-bedroom apartment from Surry Hills to Newtown") |
description | Full description with all collected details |
price | Whole dollar integer |
location_type | { type: "in_person", latitude, longitude, display_name } or { type: "remote" } |
date_type | "flexible" / "on_date" / "before_date" |
timeless_date | Required when date_type ≠ "flexible" |
specified_times | Include if the user mentioned a time of day preference |
After posting, share the returned task URL with the user and let them know offers typically arrive within minutes to hours — not immediately.
price must be a positive integer (whole dollars only).timeless_date is required whenever date_type is "on_date" or
"before_date". Do not call post_task without it in those cases.get_task_info eligibility check before posting.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub airtasker/airtasker-mcp-server --plugin airtasker