Dark Social Demand Generation Monitor
CreateRevOpsMarketing
A map of where your buyers talk off the record, on LinkedIn, Slack communities, and Reddit, with the conversations worth joining to create inbound demand.
This is the skill file version. It carries the prompt text unchanged and adds the inputs to collect, the process, decision rules, quality checks, and guardrails. The one-off prompt lives on its prompt page.
The file
---
name: dark-social-demand-generation-monitor
description: >-
A map of where your buyers talk off the record, on LinkedIn, Slack communities, and Reddit, with the conversations worth joining to create inbound demand.
Task type: Create. Built for RevOps, Marketing.
Use when the request sounds like "Dark Social Demand Generation Monitor".
Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
author: The Revenue AI Report
suite: Customer Retention and Growth
version: "1.0"
source: https://www.therevenueaireport.com/prompts/dark-social-demand-generation-monitor
---
# Dark Social Demand Generation Monitor
A map of where your buyers talk off the record, on LinkedIn, Slack communities, and Reddit, with the conversations worth joining to create inbound demand.
One job only: a map of where your buyers talk off the record, on LinkedIn, Slack communities, and Reddit, with the conversations worth joining to create inbound demand. Anything outside that job belongs in another file in the Customer Retention and Growth suite.
## When to use this skill
- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.
## When not to use it
- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.
## Inputs to collect first
- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on
Ask for anything missing before running. Do not fill a gap with a plausible guess.
## Process
1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.
## Instruction block
Run this text with the placeholders filled in.
```text
{
"intro": "You are an expert in dark social demand generation, specializing in identifying and engaging with **off-the-radar buying conversations**. Your mission is to track **real-time discussions** happening in key social and community spaces and surface high-value engagement opportunities.",
"task": "Monitor dark social channels for **keywords and buying intent signals** related to {product_category}.",
"input": {
"keywords": ["Competitor mentions", "Pain points", "Buying questions"],
"platforms": ["LinkedIn posts", "Slack communities", "Reddit threads", "Discord"],
"engagement_triggers": ["Questions about {product_category}", "Competitor frustration", "Peer recommendations"]
},
"output_format": {
"engagement_opportunities": [
{
"platform": "[Where conversation is happening]",
"post_link": "[URL]",
"post_summary": "[Brief post overview]",
"recommended_engagement": "[Comment, DM, or share relevant content]"
}
]
}
}
```
## Decision rules
- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.
## Quality checks
- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.
## Guardrails
- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.
## Source
- Prompt page: https://www.therevenueaireport.com/prompts/dark-social-demand-generation-monitor
- Suite: https://www.therevenueaireport.com/agent-skills/suites/customer-retention-and-growth
- Publication: The Revenue AI Report, https://www.therevenueaireport.com
Install this skill
- For Claude Code, copy the command below into your terminal. It creates the skill folder and saves the file as SKILL.md.
- For another assistant that supports skills, download the file above and place it in a folder named
dark-social-demand-generation-monitorinside that assistant's skills directory. - Start a new conversation and ask for the job named on this page. Review the result before using it.
For the supporting files, download the full Customer Retention and Growth package too. The single-file command only installs SKILL.md.
mkdir -p "$HOME/.claude/skills/dark-social-demand-generation-monitor" && curl -fL "https://www.therevenueaireport.com/agent-skills/prompt/dark-social-demand-generation-monitor/SKILL.md" -o "$HOME/.claude/skills/dark-social-demand-generation-monitor/SKILL.md"