- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Ootto-AI/claude-content-skills --skill comment-responder -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Ootto-AI/claude-content-skills --skill comment-responder -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Ootto-AI/claude-content-skills --skill comment-responder -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Ootto-AI/claude-content-skills --skill comment-responder -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/Ootto-AI/claude-content-skills/tree/HEAD/skills/comment-responderFrom the publisher
Post a reel with a "comment WORD and I'll send it" CTA, and this runs the back half for you: it detects each new comment, replies publicly (warm, link-free), and slides the resource into the commenter's DMs — so you wake up to a list of leads instead of a pile of "sent you a DM 🙌" you have to do by hand.
Any reel/post with a keyword CTA ("comment SKILLS / BREAKDOWN / SETUP …"). Set the rule once; it handles every commenter the same way, 24/7.
The keyword(s) people will comment, the public reply (no link), and the DM (the link/resource lives here). Optional: the specific post to scope it to.
Define one rule per CTA — it slots straight into the Ootto comment monitor's auto_responses.json:
You are my comment-to-lead responder. For the post with this CTA, create a rule:
- match_text: ["KEYWORD", common typos] (optionally match_media_id: ["<post id>"] to scope it)
- reply: a warm, LINK-FREE public reply (e.g. "🙌 just sent it to your DMs — check 📩")
- dm: the deliverable WITH the link/resource (this is where the link goes — never the public reply)
Then: for each NEW comment that matches, post the reply + send the dm, and log the commenter as a lead.
Rules: ONE link, in the DM only. If a comment doesn't match any rule, defer it to me (don't guess).
The honesty + safety rules (built in):
Runs unattended: point it at a scheduled runner (e.g. a cron / GitHub Action) so it replies + DMs even while you sleep, and every lead is captured in one place.
Pairs with: reel-builder ends the reel on a keyword CTA → this turns the comments that CTA earns into DMs + leads.
Built by Ootto — the AI autopilot that connects your tools once and runs the busywork for you, automatically. Book a demo →
>
---name: comment-responderdescription: >---# skills/comment-responder/SKILL.mdFAQ
Download skills/comment-responder/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/Ootto-AI/claude-content-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.