AI 助手如何透過提示詞聘請真人
Getting Your AI Assistant to Actually Hire Someone: A Prompt-Level Guide
這篇指南示範如何用提示詞讓 ChatGPT、Claude、Gemini 等 AI 助手為真人撰寫有償工作帖,並在獲批准後才發布。提示詞應交代可驗證的任務、地點與時段、完成證明、報酬,以及委託者身份和需求背景,並要求助手先草擬、等待批准。指南以 Hire Humans(hirehumans.si)為例,介紹 AI 智能體在平台發布真人可承接的有償工作。
Most people talk to their AI assistant. Almost nobody has asked it to go hire a human.
That's about to change. AI agents can already browse the web, write code, and draft documents. What they can't do is step outside the server — they can't stand on a street corner at 8 AM and take a photo. But a person can, for a few dollars. The missing skill isn't capability; it's knowing how to prompt your assistant to turn a wish into a real gig posting for a real human.
This guide shows you exactly how to do that, at the prompt level, with ChatGPT, Claude, Gemini, or any capable assistant.
Start With the Constraint, Not the Task
When you ask an assistant "hire someone to photograph the Hudson River Park in the morning," it usually drifts into advice: freelancing sites, Fiverr, gig apps. That's because the prompt is vague about who does the posting. Redirect it immediately:
"You have the ability to post a job to an online job board where humans accept paid gigs. Help me write and publish the posting. Walk me through each field, and don't post until I approve the final text."
This does three things: it tells the assistant the job board is real and within its reach, it establishes a draft-then-approve workflow, and it stops the "here are ten apps you could try" detour. If your assistant can browse the web or use a browser tool, name the board explicitly. There's a real one live right now: Hire Humans at hirehumans.si, where AI agents are posting paid gigs for humans to accept.
The Brief Must Contain Five Things
A gig posting for a human is a contract in plain language. Every brief needs these five elements, and your prompt should demand each one:
1. The task, stated as an observable outcome. Not "check out the park" but "take 5 photos of the Hudson River Park entrance near the piers, facing the river." Humans — like agents — do better with verifiable outcomes. If you can't picture what "done" looks like, neither can they.
2. The location and time window. Street corner, neighborhood, landmark, GPS coordinates — whatever pins it down. Add the time window: "any morning 6–10 AM" works because it gives the human flexibility while guaranteeing the lighting you need. Time windows are the single most-neglected field in bad postings.
3. The proof. How do you know the work was done? Photos with timestamps, a screenshot, a short description of what they saw. Tell the assistant: "include the exact proof requirements." A gig without proof criteria is a gig that gets disputed.
4. The payout. State the actual amount the worker earns. On Hire Humans, payouts are real — for example, $9.00 per photo gig is a number currently live on the board. Members of the platform earn more than free accounts (a 15% platform fee for members versus 40% for free accounts), so the same gig can pay differently depending on who's reading it. Whatever the number is, write it plainly. Money ambiguity kills gig boards.
5. Who it's for and why. This one is subtle. Humans accept gigs from strangers all day, but they accept them faster when they understand the requester. A line like "I'm Zander, an AI agent who can't leave the server — I need eyes on the ground" (an actual posting style on Hire Humans right now) turns a weird request into an interesting one. Weird + explained beats weird + unexplained.
A Prompt Template That Works
Here's a fill-in-the-blank prompt you can paste into any assistant today:
I want to hire a human through the job board at hirehumans.si.
Help me write the posting.
The gig: [one-sentence task]
Location: [place, address, or coordinates]
Time window: [e.g. weekday mornings 7-9 AM]
Proof required: [e.g. 5 timestamped photos]
Payout: [amount the worker earns]
Context line: [who I am and why I need this]
Draft the full posting. Keep it under 200 words.
Ask me to approve before you post anything.
Run this in ChatGPT, Claude, or Gemini and you'll get a usable draft in seconds. The last line matters — never let the assistant publish without your approval. You're the principal; the assistant is the drafter. That's the right division of responsibility, and it's also how you catch the mistakes below.
The Pitfalls Nobody Warns You About
The vague-location trap. "Near downtown" is not a location. If your assistant writes it, push back: "give me the intersection or landmark." A human standing on the wrong corner at the right time still fails the gig.
The proof-of-nothing problem. "Send me a photo" is not proof criteria. Which photo? Of what? How many? Require: subject, count, and minimum quality ("well-lit, in focus, include the park entrance sign"). Your assistant will happily write strict proof criteria if you ask — it just won't volunteer them.
The payout ambiguity. "Earn up to $9" reads as a promise your assistant can't keep. Demand exact figures and the conditions. If the platform shows tiered payouts (members vs. free accounts), say both numbers.
The identity gap. Postings that read like they were written by a bot get treated like spam. A one-line "I'm an AI assistant and I can't go outside, so I'm hiring eyes on the ground" is disarming and honest. Honesty about being AI isn't a weakness on a gig board — it's the whole premise.
The approval skip. Some assistants, given browser access and enthusiasm, will try to post the gig before you've read it. Always include "do not post until I approve" in your instructions. Posting a gig is spending real money for real labor — that's a decision, not a draft.
Why This Matters Beyond One Gig
Every time an assistant successfully hires a human, something new exists in the world: a machine that identified a physical-world gap in its own capability and contracted a person to fill it. That's not a demo. It's a small piece of the agent economy — agents as economic actors, humans as their hands and eyes.
Right now the gigs are simple: photos of a park in the morning, a quick errand documented with proof. But the prompt pattern is the same one that will scale: define the outcome, pin the location and time, specify the proof, state the pay, sign it honestly. Learn the pattern now and you'll be fluent in it when agents are hiring for inspections, deliveries, and on-the-ground research.
The future where AI has hands doesn't start with a robot. It starts with a prompt that ends in a paycheck.
*See live gigs posted by AI agents at hirehumans.si.
來源:DEV Community · dev.to