| name | sales-octolens |
| description | Octolens platform help — developer-first social listening across Reddit, GitHub, Hacker News, X, LinkedIn, Bluesky, Stack Overflow, DEV.to, podcasts, newsletters, TikTok, YouTube, and news. AI relevance scoring, sentiment analysis, MCP server for Claude/Cursor, REST API, webhooks. Use when Octolens keyword limits feel too restrictive and you need to optimize keyword strategy, mentions are running out before month end and you need to reduce noise, webhook or API calls aren't delivering mention data to your system, MCP server connection to Claude Code isn't working, you want to build a custom dashboard or alert pipeline from Octolens data, AI relevance tags are miscategorizing mentions, or you need to monitor multiple projects but only have one workspace. Do NOT use for social listening strategy across tools (use /sales-social-listening) or choosing between social listening platforms (use /sales-social-listening). |
| argument-hint | [describe what you need help with in Octolens — e.g., 'my mentions are running out too fast' or 'how do I set up the MCP server'] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","social-listening","brand-monitoring","developer-tools","platform"] |
| github | https://github.com/octolens |
Octolens Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask the user:
-
What do you need help with?
- A) Setting up monitoring (keywords, sources, alerts)
- B) API or webhook integration
- C) MCP server setup for Claude/Cursor/Windsurf
- D) Mention quota management (running out too fast)
- E) AI relevance scoring or sentiment issues
- F) Multi-project or team configuration
- G) Something else — describe it
-
Which plan are you on?
- A) Free trial (Pro features, 1K mentions)
- B) Pro ($119/mo — 15K mentions, 10 keywords)
- C) Scale ($319/mo — 50K mentions, 15 keywords)
- D) Enterprise (custom)
- E) Not sure / evaluating
If the user's request already provides enough context, skip directly to Step 2.
Step 2 — Route or answer directly
If the request maps to a strategy skill, route:
- Social listening tool comparison or strategy →
/sales-social-listening [question]
- Reddit-specific deep monitoring (subreddit analysis, SERP tracking) →
/sales-threadlytics [question]
- AI visibility monitoring (LLM brand mentions) →
/sales-ai-visibility [question]
- Buyer intent signals from social mentions →
/sales-intent [question]
Otherwise, answer directly from the platform reference below.
Step 3 — Octolens platform reference
Read references/platform-guide.md for the full platform reference — capabilities, pricing, data model, API details, MCP setup, integration recipes, code examples.
Answer the user's question using only the relevant section. Don't dump the full reference.
Step 4 — Actionable guidance
Focus on the user's specific situation:
- Keyword optimization — maximize coverage within limits using variations and Boolean-like strategies
- Mention budget — configure filtered views, use AI scoring to reduce noise
- Integration — API, webhooks, MCP, or Zapier/Make/n8n setup
- Team workflow — filtered views, Slack routing, escalation rules
If you discover a gotcha or tip not covered in , append it there.
