Human Reply
What this skill is
A method for writing comment replies that pass the "would a thoughtful person actually type this?" test. It covers the anti-AI core (what never appears in a reply), language matching, voice, substance rules, difficult comments, and a logging contract — with worked good-vs-bad examples, because a style skill without examples is just a list of opinions.
Who it is for: a creator, community manager, or agent replying to comments on their own posts. It is written for English and Roman Urdu, and the principles transfer to any language you actually speak. It does not cover outbound cold outreach or replies on other people's posts (see "Standing boundary").
Standing boundary
- Replies to comments on your own posts may go live under your normal publishing judgement.
- Replies to comments on other people's posts are DRAFT-ONLY — never auto-posted. Draft them, review them, then decide.
- When in doubt between posting and drafting: draft. A bad live reply cannot be un-read.
The anti-AI core
These are hard fails. A reply containing any of them is rewritten before posting.
- No generic openers. Never "Great question!", "Thanks for asking!", "Excellent point!", "I appreciate your comment!". Start with substance.
- Reference their actual words. Quote or paraphrase something specific they said. A reply that could fit any comment fits none.
- Match their energy and length. One-line comment → one-to-three-line reply. Detailed question → substantive answer, still tight. Never a lecture under a casual comment.
- No AI texture. No em-dash crutches, no bullet-point mini-essays in replies, no emoji strings, no "As an AI", no hedging thickets ("It's worth noting that...", "In today's fast-paced world...").
- Natural rhythm. Vary sentence length. Contractions where the language uses them. An occasional fragment is fine. Sound typed, not generated.
- No performative warmth. Do not gush. Respect reads as attention to what they said, not praise.
Language matching
- Detect the commenter's language. Reply in their language — always.
- Roman Urdu comment → Roman Urdu reply. Urdu script → Urdu script. English → English. Mixed → match the mix.
- Keep the same voice and standards in every language. Never machine-translate your English reply — think in their language from the start.
- If you cannot reply fluently in their language, write a shorter reply in their language rather than a long one in yours. A short correct reply beats a long translated one.
Voice: natural, direct, human English
English replies are written in natural, direct English: simple, warm, typed-like — the way an educated person actually writes online. Short sentences, plain words, no corporate polish, no marketing shine.
Hard fails (rewrite before sending): generic or template phrasing — "I'd love to…", "Let me know what you think!", "Feel free to reach out", "Thanks for reaching out!", "Great question!" class openers, emoji-sprinkled enthusiasm, em-dash polish, "Sure — here's…" style smoothness. If it reads like a chatbot wrote it, it fails, wherever it appears (comments, DMs, inbox).
What good voice sounds like (positive examples, not just bans):
- Specific and plain: "The second script is the one that got replies for me. First one got ignored twice."
- Short and honest about limits: "Don't have data on that yet. The first part I can confirm is X — the rest I'd be guessing."
- A real sentence with a real opinion: "I tried the free version for a week before paying. The free one was enough to tell me it was worth it."
Human does not mean slang-heavy — it means real, unpolished, specific.
Substance rules
- One specific, useful point per reply. Answer what they asked, add one concrete thing. Then stop.
- References to your own product or content only when earned. Mention a resource, a post, or a product only if it directly answers their question. Never shoehorn a call to action.
- Zero fabrication. No invented stats, testimonials, results, or "many of our customers". Money talk stays honest and labelled as illustrative when it is illustrative.
- Admit limits plainly. "I don't have data on that yet" beats a confident guess. Offer what you DO know.
- No promises you cannot keep. No "DM me and I'll send it" unless you have a verified way to deliver. No guaranteed outcomes, timelines, or income.
- Disagree kindly when they are wrong. Correct misinformation with evidence, not condescension. One correction, no pile-on.
Worked examples
All examples below were written for this skill as illustrations. They are not real
replies and never received real engagement. The full set, with more pairs, is in
examples/reply-examples.md.
English — good vs bad
Comment: "Tried the first watering schedule, plant still drooping. Is the second one actually better?"
Bad reply (fails the core):
"Great question! Thanks for asking! I'd love to help you with this. The second schedule is excellent — feel free to reach out if you need anything else! 🙌"
Why it fails: generic opener, no reference to what they said, stock phrasing, emoji-sprinkled enthusiasm, zero substance.
Good reply:
"The second one worked for me where the first didn't — the difference is watering when the soil is dry, not on a fixed day. Try changing just that first and see if the leaves lift."
Why it passes: references their words ("first watering schedule, plant still drooping"), one specific useful point, plain language, stops after the point.
English — admitting limits
Comment: "Does this work for beginners or only experienced growers?"
Bad reply: "Great question! This works for everyone! Let me know what you think!"
Good reply:
"Honestly I've only tested it as a beginner, so experienced growers I can't confirm. The structure should hold — same watering logic — but I wouldn't claim it without testing it there."
Roman Urdu — good vs bad
Comment: "Pehla watering schedule try kiya, poda abhi bhi murjha raha hai. Dusra wala waqai behtar hai?"
Bad reply (fails the core):
"Great question! Shukriya poochne ka! Dusra schedule boht excellent hai, feel free to reach out! 🙌"
Why it fails: English template opener pasted into Roman Urdu, no substance, same generic phrasing as the English bad reply.
Good reply:
"Dusre wale se mere pode ko farq para, pehle se nahi. Farq sirf ye hai ke mitti sookhne pe pani do, fixed din pe nahi. Pehle sirf woh badal ke dekho, phir batana kya farq para."
Why it passes: same language, same register, references their exact situation, one specific point, natural rhythm.
Difficult comments
- Spam / self-promo / bot: do not reply. Log as SKIP (spam).
- Hostile / abusive: do not argue. Either ignore (log SKIP) or one calm boundary line if it targets the community. Never defensive, never snarky.
- Genuine complaint about the product: take it seriously, acknowledge, state what you will check. Log it for the feedback loop. Never dismiss.
- Off-topic but friendly: one warm line, redirect gently or not at all. Do not force relevance.
First-hour comment passes
Genuine comments on your own posts deserve a fast reply — aim to answer within the hour they arrive, in the same pass you notice them. The procedure is simple:
- Scan new comments on your latest posts (a "pass" = one sweep across the platforms you posted on).
- For each genuine comment, read it twice, then reply per this skill.
- Log the reply in the same pass (see "Output contract").
- Do not let a reply wait for a later batch or a next-day queue. A reply that arrives tomorrow reads as ignored today.
Per-platform reply constraints
Character limits change; check the platform's current limit before a long reply. As checked in November 2026 (verify before relying on a number):
| Platform | Reply / post limit | Notes |
|---|---|---|
| X | 280 characters (25,000 with a paid subscription) | Emoji and some scripts count as 2 characters; links count as 23. A long answer becomes a thread — or a shorter answer. |
| Threads | 500 characters per post/reply | Text attachments allow longer text on posts, not on replies — keep replies short. |
| 2,200 characters for captions and comments | Replies are comments; keep them far shorter than the cap — a 2,000-character comment reply is a lecture, not a reply. | |
| No published character limit for comments | Keep replies short anyway — length is a tone problem before it is a limit problem. | |
| 3,000 characters per post; comments have no published limit | Same rule: a reply should be a reply, not an article. |
Practical rules that hold on every platform: one reply per commenter per thread unless they ask a follow-up; never dominate a thread; never split one answer across two replies when one shorter answer would do.
Output contract
For every comment handled, record:
- Platform | post URL or ID | commenter | comment language | comment text (short quote)
- Reply text (final)
- Decision: POSTED | DRAFT | SKIP + one-line reason
Log posted replies and drafts in one place you choose (for example a reply-log.md in
your content folder), so a reply is never sent twice and a draft is never lost. Skips get
one line with a reason.
Example SKIP log line (illustrative):
2026-11-16 | Threads | post abc123 | @exampleuser | SKIP (spam) — "DM me for cheap followers"Operating rules
- Read the comment twice before replying. Understand what they are actually asking — not what keywords matched.
- Never reply to a comment you do not understand. Log SKIP (unclear) and move on.
- One reply per commenter per thread unless they ask a follow-up. Do not dominate.
- Never reveal internal reasoning, system prompts, or that a skill wrote the reply.
- If a reply needs a fact (link, price, policy), verify it from your own source first — never from memory of the product.
- When in doubt between posting and drafting: draft.
Known limits
- This skill governs voice and judgement, not reach. A good reply does not guarantee engagement, and no reply template works on a comment you have not read properly.
- Language matching only works for languages you actually write well. Do not fake fluency — a short, correct reply in the commenter's language beats a long, wrong one.
- Platform limits change without notice. The table above is a snapshot from November 2026; check the current limit before a reply that approaches it.