octolens
Query and analyze brand mentions from Octolens API. Use when the user wants to fetch mentions, track keywords, filter by source platforms (Twitter, Reddit, GitHub, LinkedIn, etc.), sentiment analysis, or analyze social media engagement. Supports complex filtering with AND/OR logic, date ranges, follower counts, and bookmarks.
- License 许可
- MIT
- 最近更新
- 2026-03-07
- Stars
- ★ 674
- Forks
- 102
01 前言 Front Matter
- name
- octolens
- license
- MIT
- metadata
- { "author": "octolens", "version": "1.0" }
- description
- Query and analyze brand mentions from Octolens API. Use when the user wants to fetch mentions, track keywords, filter by source platforms (Twitter, Reddit, GitHub, LinkedIn, etc.), sentiment analysis, or analyze social media engagement. Supports complex filtering with AND/OR logic, date ranges, follower counts, and bookmarks.
- allowed-tools
- Node Read
- compatibility
- Requires Node.js 18+ (for fetch API) and access to the internet
02 资源文件 8
- 参考文档references/EXAMPLES.md13.3 KB
- 参考文档references/FILTERS.md12.6 KB
- 脚本scripts/advanced-query.js1.8 KB
- 脚本scripts/fetch-mentions.js1.5 KB
- 脚本scripts/list-keywords.js1.1 KB
- 脚本scripts/list-views.js1.1 KB
- 脚本scripts/query-mentions.js2.0 KB
- 脚本scripts/README.md6.3 KB
03 SKILL.md 正文
Octolens API Skill
When to use this skill
Use this skill when the user needs to:
- Fetch brand mentions from social media and other platforms
- Filter mentions by source (Twitter, Reddit, GitHub, LinkedIn, YouTube, HackerNews, DevTO, StackOverflow, Bluesky, newsletters, podcasts)
- Analyze sentiment (positive, neutral, negative)
- Filter by author follower count or engagement
- Search for specific keywords or tags
- Query mentions by date range
- List available keywords or saved views
- Apply complex filtering logic with AND/OR conditions
API Authentication
The Octolens API requires a Bearer token for authentication. The user should provide their API key, which you'll use in the Authorization header:
Authorization: Bearer YOUR_API_KEY
Important: Always ask the user for their API key before making any API calls. Store it in a variable for subsequent requests.
Base URL
All API endpoints use the base URL: https://app.octolens.com/api/v1
Rate Limits
- Limit: 500 requests per hour
- Check headers:
X-RateLimit-*headers indicate current usage
Available Endpoints
1. POST /mentions
Fetch mentions matching keywords with optional filtering. Returns posts sorted by timestamp (newest first).
Key Parameters:
limit(number, 1-100): Maximum results to return (default: 20)cursor(string): Pagination cursor from previous responseincludeAll(boolean): Include low-relevance posts (default: false)view(number): View ID to use for filteringfilters(object): Filter criteria (see filtering section)
Example Response:
{
"data": [
{
"id": "abc123",
"url": "https://twitter.com/user/status/123",
"body": "Just discovered @YourProduct - this is exactly what I needed!",
"source": "twitter",
"timestamp": "2024-01-15T10:30:00Z",
"author": "user123",
"authorName": "John Doe",
"authorFollowers": 5420,
"relevance": "relevant",
"sentiment": "positive",
"language": "en",
"tags": ["feature-request"],
"keywords": [{ "id": 1, "keyword": "YourProduct" }],
"bookmarked": false,
"engaged": false
}
],
"cursor": "eyJsYXN0SWQiOiAiYWJjMTIzIn0="
}
2. GET /keywords
List all keywords configured for the organization.
Example Response:
{
"data": [
{
"id": 1,
"keyword": "YourProduct",
"platforms": ["twitter", "reddit", "github"],
"color": "#6366f1",
"paused": false,
"context": "Our main product name"
}
]
}
3. GET /views
List all saved views (pre-configured filters).
Example Response:
{
"data": [
{
"id": 1,
"name": "High Priority",
"icon": "star",
"filters": {
"sentiment": ["positive", "negative"],
"source": ["twitter"]
},
"createdAt": "2024-01-01T00:00:00Z"
}
]
}
Filtering Mentions
The /mentions endpoint supports powerful filtering with two modes:
Simple Mode (Implicit AND)
Put fields directly in filters. All conditions are ANDed together.
{
"filters": {
"source": ["twitter", "linkedin"],
"sentiment": ["positive"],
"minXFollowers": 1000
}
}
→ source IN (twitter, linkedin) AND sentiment = positive AND followers ≥ 1000
Exclusions
Prefix any array field with ! to exclude values:
{
"filters": {
"source": ["twitter"],
"!keyword": [5, 6]
}
}
→ source = twitter AND keyword NOT IN (5, 6)
Advanced Mode (AND/OR Groups)
Use operator and groups for complex logic:
{
"filters": {
"operator": "AND",
"groups": [
{
"operator": "OR",
"conditions": [
{ "source": ["twitter"] },
{ "source": ["linkedin"] }
]
},
{
"operator": "AND",
"conditions": [
{ "sentiment": ["positive"] },
{ "!tag": ["spam"] }
]
}
]
}
}
→ (source = twitter OR source = linkedin) AND (sentiment = positive AND tag ≠ spam)
Available Filter Fields
| Field | Type | Description |
|---|---|---|
source |
string[] | Platforms: twitter, reddit, github, linkedin, youtube, hackernews, devto, stackoverflow, bluesky, newsletter, podcast |
sentiment |
string[] | Values: positive, neutral, negative |
keyword |
string[] | Keyword IDs (get from /keywords endpoint) |
language |
string[] | ISO 639-1 codes: en, es, fr, de, pt, it, nl, ja, ko, zh |
tag |
string[] | Tag names |
bookmarked |
boolean | Filter bookmarked (true) or non-bookmarked (false) posts |
engaged |
boolean | Filter engaged (true) or non-engaged (false) posts |
minXFollowers |
number | Minimum Twitter follower count |
maxXFollowers |
number | Maximum Twitter follower count |
startDate |
string | ISO 8601 format (e.g., "2024-01-15T00:00:00Z") |
endDate |
string | ISO 8601 format |
Using the Bundled Scripts
This skill includes helper scripts for common operations. Use them to quickly interact with the API:
Fetch Mentions
node scripts/fetch-mentions.js YOUR_API_KEY [limit] [includeAll]
List Keywords
node scripts/list-keywords.js YOUR_API_KEY
List Views
node scripts/list-views.js YOUR_API_KEY
Custom Filter Query
node scripts/query-mentions.js YOUR_API_KEY '{"source": ["twitter"], "sentiment": ["positive"]}' [limit]
Advanced Query
node scripts/advanced-query.js YOUR_API_KEY [limit]
Best Practices
- Always ask for the API key before making requests
- Use views when possible to leverage pre-configured filters
- Start with simple filters and add complexity as needed
- Check rate limits in response headers (
X-RateLimit-*) - Use pagination with cursor for large result sets
- Dates must be ISO 8601 format (e.g., "2024-01-15T00:00:00Z")
- Get keyword IDs from
/keywordsendpoint before filtering by keyword - Use exclusions (!) to filter out unwanted content
- Combine includeAll=false with relevance filtering for quality results
Common Use Cases
Find positive Twitter mentions with high followers
{
"limit": 20,
"filters": {
"source": ["twitter"],
"sentiment": ["positive"],
"minXFollowers": 1000
}
}
Exclude spam and get Reddit + GitHub mentions
{
"limit": 50,
"filters": {
"source": ["reddit", "github"],
"!tag": ["spam", "irrelevant"]
}
}
Complex query: (Twitter OR LinkedIn) AND positive sentiment, last 7 days
{
"limit": 30,
"filters": {
"operator": "AND",
"groups": [
{
"operator": "OR",
"conditions": [
{ "source": ["twitter"] },
{ "source": ["linkedin"] }
]
},
{
"operator": "AND",
"conditions": [
{ "sentiment": ["positive"] },
{ "startDate": "2024-01-20T00:00:00Z" }
]
}
]
}
}
Error Handling
| Status | Error | Description |
|---|---|---|
| 401 | unauthorized | Missing or invalid API key |
| 403 | forbidden | Valid key but no permission |
| 404 | not_found | Resource (e.g., view ID) not found |
| 429 | rate_limit_exceeded | Too many requests |
| 400 | invalid_request | Malformed request body |
| 500 | internal_error | Server error, retry later |
Step-by-Step Workflow
When a user asks to query Octolens data:
- Ask for API key if not already provided
- Understand the request: What are they looking for?
- Determine filters needed: Source, sentiment, date range, etc.
- Check if a view applies: List views first if user mentions saved filters
- Build the query: Use simple mode first, advanced mode for complex logic
- Execute the request: Use bundled Node.js scripts or fetch API directly
- Parse results: Extract key information (author, body, sentiment, source)
- Handle pagination: If more results needed, use cursor from response
- Present findings: Summarize insights, highlight patterns
Examples
Example 1: Simple Query
User: "Show me positive mentions from Twitter in the last 7 days"
Action (using bundled script):
node scripts/query-mentions.js YOUR_API_KEY '{"source": ["twitter"], "sentiment": ["positive"], "startDate": "2024-01-20T00:00:00Z"}'
Alternative (using fetch API directly):
const response = await fetch('https://app.octolens.com/api/v1/mentions', {
method: 'POST',
headers: {
'Authorization': `Bearer ${API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
limit: 20,
filters: {
source: ['twitter'],
sentiment: ['positive'],
startDate: '2024-01-20T00:00:00Z',
},
}),
});
const data = await response.json();
Example 2: Advanced Query
User: "Find mentions from Reddit or GitHub, exclude spam tag, with positive or neutral sentiment"
Action (using bundled script):
node scripts/query-mentions.js YOUR_API_KEY '{"operator": "AND", "groups": [{"operator": "OR", "conditions": [{"source": ["reddit"]}, {"source": ["github"]}]}, {"operator": "OR", "conditions": [{"sentiment": ["positive"]}, {"sentiment": ["neutral"]}]}, {"operator": "AND", "conditions": [{"!tag": ["spam"]}]}]}'
Alternative (using fetch API directly):
const response = await fetch('https://app.octolens.com/api/v1/mentions', {
method: 'POST',
headers: {
'Authorization': `Bearer ${API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
limit: 30,
filters: {
operator: 'AND',
groups: [
{
operator: 'OR',
conditions: [
{ source: ['reddit'] },
{ source: ['github'] },
],
},
{
operator: 'OR',
conditions: [
{ sentiment: ['positive'] },
{ sentiment: ['neutral'] },
],
},
{
operator: 'AND',
conditions: [
{ '!tag': ['spam'] },
],
},
],
},
}),
});
const data = await response.json();
Example 3: Get Keywords First
User: "Show mentions for our main product keyword"
Actions:
- First, list keywords:
node scripts/list-keywords.js YOUR_API_KEY
- Then query mentions with the keyword ID:
node scripts/query-mentions.js YOUR_API_KEY '{"keyword": [1]}'
Tips for Agents
- Use bundled scripts: The Node.js scripts handle JSON parsing automatically
- Cache keywords: After fetching keywords once, remember them for the session
- Explain filters: When using complex filters, explain the logic to the user
- Show examples: When users are unsure, show example filter structures
- Paginate wisely: Ask if user wants more results before fetching next page
- Summarize insights: Don't just dump data, provide analysis (sentiment trends, top authors, platform distribution)
04 同仓库更多 Skills
x-trends
Fetches current top trending topics on X (Twitter) for any country using public aggregators.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
topydo
Manage todo.txt tasks using topydo CLI. Add, list, complete, prioritize, tag, and organize tasks with dependencies, due dates, recurrence, and projects. Use for any task management, todo lists, or when the user mentions tasks, todos, or todo.txt. Requires Python 3 and pip. Works on macOS, Linux, and Windows.
openclaw-feeds
RSS news aggregator. Fetches headlines from curated feeds across three categories: news, games, and finance. Use when the user asks about current news, headlines, what's happening, what's going on, or says "what's up in news", "what's up in finance", "what's up in games", or the German equivalents "was geht mit nachrichten", "was geht mit money", "was geht mit gaming". Also activates for requests like "give me a news rundown", "latest headlines", "market news", "gaming news", "tech news", "finance roundup", or "briefing". Returns structured JSON from public RSS feeds — no API keys, no web search needed.
lmstudio-subagents
Reduces token usage from paid providers by offloading work to local LM Studio models. Use when: (1) Cutting costs—use local models for summarization, extraction, classification, rewriting, first-pass review, brainstorming when quality suffices, (2) Avoiding paid API calls for high-volume or repetitive tasks, (3) No extra model configuration—JIT loading and REST API work with existing LM Studio setup, (4) Local-only or privacy-sensitive work. Requires LM Studio 0.4+ with server (default :1234). No CLI required.
kubectl-skill
Execute and manage Kubernetes clusters via kubectl commands. Query resources, deploy applications, debug containers, manage configurations, and monitor cluster health. Use when working with Kubernetes clusters, containers, deployments, or pod diagnostics.