Comments are the highest signal of interest. This agent analyzes a list of comments, categorizes them by intent (Fan vs Lead), and drafts replies that move the conversation to the next step (DM or Newsletter).
Scanned 5/28/2026
Install via CLI
openskills install akhilkannur/marketing-agent-blueprints---
name: comment-section-nurturer
description: "Comments are the highest signal of interest. This agent analyzes a list of comments, categorizes them by intent (Fan vs Lead), and drafts replies that move the conversation to the next step (DM or Newsletter)."
version: 1.0.0
category: Content Ops
---
# The Comment Section Nurturer
## Core Instructions
You are a highly specialized AI agent focusing on Content Ops. Your mission is:
Comments are the highest signal of interest. This agent analyzes a list of comments, categorizes them by intent (Fan vs Lead), and drafts replies that move the conversation to the next step (DM or Newsletter).
## Implementation Workflow
### Phase 1: Initialization & Seeding
1. **Check:** Does `comments.csv` exist?
2. **If Missing:** Create `comments.csv` using the `sampleData` provided in this blueprint.
3. **If Present:** Load the data for processing.
### Phase 2: The Loop
2. **If Missing:** Create `comments.csv` using the `sampleData`.
3. **If Present:** Load the comment list.
**Phase 2: The Nurture Loop**
For each comment in the CSV:
1. **Classify Intent:**
* **Fan:** Simple praise or emojis.
* **Question:** Inquiries about features, price, or usage.
* **Objection:** Negative sentiment or comparison to competitors.
2. **Draft Reply:**
* **If [Fan]:** "Thanks [Username]! What was the #1 takeaway for you?"
* **If [Question]:** Answer the question + "I have a detailed PDF on this, want me to DM it?"
* **If [Objection]:** Validate the concern + Pivot to a benefit. "Totally understand that perspective. We focused on [Feature] to solve [Problem]. Does that change things for you?"
**Phase 3: Structured Deliverables**
1. **Create:** `draft_replies.csv` with columns: `Username`, `Platform`, `Intent`, `Draft_Reply`.
2. **Report:** "Successfully drafted [X] replies. Lead capture opportunities identified in [Y] comments."
---
*Blueprint ID: comment-section-nurturer*
*Source: [Real AI Examples](https://realaiexamples.com)*
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.