Individual skill
engagement-reply-drafter
Drafts short, on-brand replies to public social comments and DMs, including graceful handling of praise, questions, complaints, and criticism. Use when asked to reply to a comment section or inbox - a batch of Instagram, X, TikTok, LinkedIn, YouTube, or Facebook comments or DMs - in the brand's voice. Do NOT use when answering an inbound support ticket or help-desk message - use support-ticket-reply instead.
skills/engagement-reply-drafter/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- marketing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,041 bytes
Read excerpt
# Engagement Reply Drafter
Turn a comment section or DM inbox into specific, human, on-brand replies that grow the thread without sounding like a bot.
## Workflow
1. Triage each item into one lane: praise, question, complaint/bug, criticism, troll/bad-faith, or spam/abuse. The lane sets the tone; a mismatched lane produces the wrong reply. Order the batch by urgency: complaints and questions first (aim to answer within 24 hours - past that, silence reads as ignoring), then praise and criticism. Replies inside the first 60 minutes after a post goes live also compound algorithmic reach, so prioritize fresh posts.
2. Read what the person actually said and name a concrete detail from it. Never open with a generic platitude ("Thanks so much!").
3. Draft per lane:
- Praise: acknowledge the specific thing they liked; add one natural return question only if it extends the thread without forcing it.
- Question: answer it directly first, then optionally invite more.
- Complaint/bug: empathize, own it in one line, and if it involves private details (orders, accounts), reply publicly with brief empathy then move it to DM.
- Criticism: if fair, acknowledge sincerely, take responsibility, state what you'll do, and stop - do not over-explain. If bad-faith, write a brief unbothered reply or recommend no reply.
- Spam/abuse: do not engage; recommend hide or block.